Bug 1205668

Summary: Errors in log when upgrading
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: UpgradesAssignee: Stephen Benjamin <stbenjam>
Status: CLOSED CURRENTRELEASE QA Contact: Sachin Ghai <sghai>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, bkearney, erezende, jhutar, jnikolak, jyejare, lhellebr, mmccune, omaciel, sghai, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/10282
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 13:56:19 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:
Bug Depends On:    
Bug Blocks: 1131575, 1180692, 1195618, 1196031    
Attachments:
Description Flags
Update log file none

Description Lukáš Hellebrandt 2015-03-25 12:46:07 UTC
Created attachment 1006308 [details]
Update log file

Description of problem:
Candlepin traceback occurs in /var/log/candlepin/candlepin.log ,
3 ISEs occur in /var/log/foreman/production.log ,
some pulp-related errors occur in /var/log/messages
log files during upgrade to 6.1.0

Version-Release number of selected component (if applicable):
Compose 20150320.1

How reproducible:
Always

Steps to Reproduce:
1. Have a sat 6.0.8 with some data
2. Add compose repository
3. "yum update" , while "tail -F /var/log/katello-installer/katello-installer.log /var/log/foreman/production.log /var/log/puppet/ /var/log/candlepin/candlepin.log /var/log/foreman-proxy/proxy.log /var/log/messages"

Actual results:
Errors in log

Expected results:
No errors

Comment 3 Lukáš Hellebrandt 2015-04-15 12:44:29 UTC
The errors actually appear in the step *before* katello-installer should be run

Comment 4 Stephen Benjamin 2015-04-15 14:07:19 UTC
`katello-installer --upgrade` should fix them

After yum update you're in kind of a weird state with newer packages and older database schemas running.  But the services need to stay running to do all the migration steps, I don't think there's a way to avoid these couple of errors you'll see during this process.

Comment 5 Stephen Benjamin 2015-04-27 19:20:04 UTC
Created redmine issue http://projects.theforeman.org/issues/10282 from this bug

Comment 6 Stephen Benjamin 2015-04-28 20:34:29 UTC
*** Bug 1215563 has been marked as a duplicate of this bug. ***

Comment 7 Stephen Benjamin 2015-04-28 20:35:48 UTC
Ah so the source of these errors is with candlepin, because gutterball isn't configured.  Will fix in the installer so gutterball gets configured in upgrades.

Comment 8 Bryan Kearney 2015-05-04 20:05:41 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/10282 has been closed
-------------
Anonymous
Applied in changeset commit:katello-installer|ac134f25fc8c2ecc9ccf8f16fb85cf5df8d9785a.

Comment 11 Stephen Benjamin 2015-05-07 08:36:00 UTC
*** Bug 1219206 has been marked as a duplicate of this bug. ***

Comment 12 Elyézer Rezende 2015-05-07 11:54:48 UTC
This is happening in new installations on RHEL 6.6:

# katello-installer -d -v --capsule-tftp="true" --foreman-admin-password="password" --capsule-dhcp-interface="virbr1" --katello-proxy-password="proxypass" --capsule-dns-interface="virbr1" --katello-proxy-port="3128" --capsule-dns="true" --capsule-register-in-foreman="true" --capsule-puppet="true" --capsule-puppetca="true" --capsule-dns-zone="example.com" --capsule-dhcp="true" --katello-proxy-url="http://proxy.example.com" --katello-proxy-username="proxyuser" --capsule-dns-forwarders="<ip_addr>" --capsule-dns-forwarders="<ip_addr>" --capsule-dns-forwarders="<ip_addr>"
ERROR: Unrecognised option '--profile'

See: 'katello-installer --help'

PS.: was edited options values.

Comment 13 Mike McCune 2015-05-07 22:14:48 UTC
Elyézer, 

that error is from https://bugzilla.redhat.com/show_bug.cgi?id=1219206

different from this bug.

Comment 14 Sachin Ghai 2015-05-08 08:49:57 UTC
This bz contains multiple issues related to upgrade..

I just tried upgrade from sat6.0.8 to sat6.1 GA snap3_compose2 and didn't see any of the reported issues as per the logs in attachments.

Just to make it clear for later review, writing all issues:

1. As per the attachement, I didn't see any exception in candlepin.log and production.log and no pulp related error in /var/log/messages..

2. katello-installer --upgrade also went smooth without throwing: ERROR: Unrecognised option '--profile'

Comment 15 Sachin Ghai 2015-05-08 08:50:57 UTC
(In reply to Sachin Ghai from comment #14)
> I just tried upgrade from sat6.0.8 to sat6.1 GA snap3_compose2 and didn't
> see any of the reported issues as per the logs in attachments.

I tried upgrade on rhel66 only

Comment 17 Sachin Ghai 2015-05-08 12:27:28 UTC
Error logs mentioned in comment 16 appears when we restart the katello-service. There is another bz related to katello-service errors. I updated these logs there too for reference.

Comment 18 Sachin Ghai 2015-05-08 12:28:11 UTC
(In reply to Sachin Ghai from comment #17)
> Error logs mentioned in comment 16 appears when we restart the
> katello-service. There is another bz related to katello-service errors. I
> updated these logs there too for reference.

https://bugzilla.redhat.com/show_bug.cgi?id=1205737

Comment 20 Sachin Ghai 2015-05-12 05:42:53 UTC
Tried upgrade from sat6.0.8 to sat6.1 GA snap3_compose2 and didn't
see any of the reported issues as per the logs in attachments.

Steps followed:
==============
1. Disable sat6.0 repo and enable sat6.1 compose repo
2. Stop services, except Mongo:

# katello-service stop
# service-wait mongod start

3. yum -y update
4. # katello-installer --upgrade


Upgrade was successful as per stdout, but I got two different issues.

- One related to qpid while katello-service restart. Reported issue here:
https://bugzilla.redhat.com/show_bug.cgi?id=1205737
- other issue was related to an error in installer.log and thats tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=1219792

Since we are tracking these issues separately and issues reported in original description are no longer reproducible so moving this to verified.

Comment 21 Bryan Kearney 2015-08-11 13:20:10 UTC
This bug is slated to be released with Satellite 6.1.

Comment 22 Bryan Kearney 2015-08-12 13:56:19 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.