Bug 872096
Summary: | Configuration files after upgrade are not deployed | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
Component: | Installation | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Og Maciel <omaciel> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | achan, cpelland, gkhachik, mmccune, omaciel |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-04 19:57:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lukas Zapletal
2012-11-01 08:25:15 UTC
For to doco effor, there is another BZ: https://bugzilla.redhat.com/show_bug.cgi?id=871488 Testing done 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? 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 Confirmed that this does fix the issue I was seeing! Leaving postgresql alone did the trick! 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 |