[katello-devel] Running katello-configure after katello-upgrade

[Og Maciel]

----- Original Message -----
> From: "Lukas Zapletal" <lzap at redhat.com>
> To: katello-devel at redhat.com
> Sent: Tuesday, October 30, 2012 9:02:03 AM
> Subject: [katello-devel] Running katello-configure after katello-upgrade
> 
> In short:
> 
> 1) yum upgrade
> 2) review rpmnew files (but do not rewrite current configuration) **
> 3) katello-upgrade
> 4) optional step: do katello-configure --anser-file=...
> 
> The topic I want to bring in are steps 2 and 4. We distribute new
> default versions of configuration files which are stored as rpmnew by
> yum. Traditional approach is to review the changes and incorporate
> them.
> But in our case, some files are substantially different and changes
> made
> by katello-configure are hard to incorporate.
> 
> I recommend to make the step 4 required, so after successful upgrade,
> user is asked to run katello-configure to redeploy all the config
> files.
> Thank to this, step 2 can be safely skipped for katello configuration
> files deleting all the rpmnew files - this step will be only
> necessary
> for system files.

If I understood this correctly we would be asking the user to perform all those 4 steps (or 3: 1, 3 and 4?) for an upgrade AND the last one to run katello-configure again with the answer-file option?  If this is the case, all I have to say is that this feels extremely flaky and not "enterpris-y" at all imnsho. I should have to yum update katello-* && katello-upgrade and walk away. When I come back, it should all be working (or point me to a log if something failed).
-- 
Og Maciel

Senior QA Engineer
Red Hat, Inc.
+1.646.707.7723
irc: omaciel