Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 872096 - Configuration files after upgrade are not deployed
Summary: Configuration files after upgrade are not deployed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-01 08:25 UTC by Lukas Zapletal
Modified: 2019-09-26 15:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In an upgrade, the command katello-upgrade does not include katello-configure. katello-configure needed to be run after running upgrade. katello-configure has been added into the katello-upgrade script, elimintating an extra step to upgrading System Engine.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:57:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Lukas Zapletal 2012-11-01 08:25:15 UTC 
We now run katello-configure at the end of the katello-upgrade, because configuration files were unchanged:

https://bugzilla.redhat.com/attachment.cgi?id=635574&action=diff

QE: To verify this, please install 1.0 and upgrade to 1.1 with the following instructions:

https://fedorahosted.org/katello/wiki/Upgrade
Comment 1 Lukas Zapletal 2012-11-01 08:25:38 UTC 
https://github.com/Katello/katello/pull/971
Comment 4 Lukas Zapletal 2012-11-01 08:41:55 UTC 
For to doco effor, there is another BZ: https://bugzilla.redhat.com/show_bug.cgi?id=871488
Comment 7 Lukas Zapletal 2012-11-05 12:13:50 UTC 
Testing done
Comment 16 Lukas Zapletal 2012-11-07 09:50:31 UTC 
Og, thanks for your comments.

You should not start katello upgrade process if the instance is not started and working properly. You obviously had postgresql service down, Katello does not work without SQL database.

Therefore I think we should add a note telling user to check if the instance is on-line and working - for example using katello ping command.

Comments?
Comment 17 Lukas Zapletal 2012-11-07 10:42:25 UTC 
Ah I see the point, in the doco there is requirement to stop the postgres. This is not correct, good catch! Removing and also adding additional note to check if katello is running (wont hurt). Please comment:

https://fedorahosted.org/katello/wiki/Upgrade?action=diff&version=17&old_version=16
Comment 20 Og Maciel 2012-11-07 15:40:46 UTC 
Confirmed that this does fix the issue I was seeing! Leaving postgresql alone did the trick!
Comment 22 errata-xmlrpc 2012-12-04 19:57:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Note You need to log in before you can comment on or make changes to this bug.