Bug 872096 – Configuration files after upgrade are not deployed

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 872096 - Configuration files after upgrade are not deployed

Summary:	Configuration files after upgrade are not deployed

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	6.0.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Katello Bug Bin
QA Contact:	Og Maciel
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-11-01 04:25 EDT by Lukas Zapletal
Modified:	2014-01-27 09:08 EST (History)
CC List:	5 users (show)

See Also:
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 14:57:39 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2012:1543	normal	SHIPPED_LIVE	Important: CloudForms System Engine 1.1 update	2012-12-04 19:39:57 EST

Groups: None (edit)

Description Lukas Zapletal 2012-11-01 04:25:15 EDT

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 04:25:38 EDT

https://github.com/Katello/katello/pull/971

Comment 4 Lukas Zapletal 2012-11-01 04:41:55 EDT

For to doco effor, there is another BZ: https://bugzilla.redhat.com/show_bug.cgi?id=871488

Comment 7 Lukas Zapletal 2012-11-05 07:13:50 EST

Testing done

Comment 16 Lukas Zapletal 2012-11-07 04:50:31 EST

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 05:42:25 EST

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 10:40:46 EST

Confirmed that this does fix the issue I was seeing! Leaving postgresql alone did the trick!

Comment 22 errata-xmlrpc 2012-12-04 14:57:39 EST

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.