Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1205693

Summary: After upgrade, "katello-service restart" produces errors
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: UpgradesAssignee: Stephen Benjamin <stbenjam>
Status: CLOSED DUPLICATE QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, lhellebr, mmccune, omaciel
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-21 11:40:05 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:
Attachments:
Description Flags
Restart log
none
Logfiles
none
audit.log
none
Sealert none

Description Lukáš Hellebrandt 2015-03-25 13:15:59 UTC
Created attachment 1006327 [details]
Restart log

Description of problem:
"katello-service restart" produces errors as in attached log files

Restart log: output of "katello-service restart" -- Celery(Pulp)-related errors

Logfiles: output of "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" -- Celery, Pulp and Candlepin related errors

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

How reproducible:
Always

Steps to Reproduce:
1. Have a sat6.0.8 with some data
2. Add compose repo
3. yum update
4. "katello-service restart" 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 produced both in command output and log file

Expected results:
Restart should work without any errors.

Additional info:
- Restart works before upgrade, I didn't do anything permissions-related
- I will also attach selinux log

Comment 1 Lukáš Hellebrandt 2015-03-25 13:17:03 UTC
Created attachment 1006328 [details]
Logfiles

Comment 2 Lukáš Hellebrandt 2015-03-25 13:32:02 UTC
Created attachment 1006332 [details]
audit.log

Seems like selinux-related issue but I didn't change anything selinux-related during upgrade

Comment 4 Lukáš Hellebrandt 2015-03-25 13:35:08 UTC
Created attachment 1006333 [details]
Sealert

Comment 5 Stephen Benjamin 2015-04-15 11:48:54 UTC
As mentioned in BZ1205737, the upgrade is not being done correctly.  I imagine if you follow the procedure mentioned there the errors should go away.

Comment 7 Lukáš Hellebrandt 2015-04-16 08:46:42 UTC
The same as in BZ linked in comment 5, probably not a bug.

Comment 8 Stephen Benjamin 2015-04-21 11:40:05 UTC
Essentially the same problem as BZ1205737.

*** This bug has been marked as a duplicate of bug 1205737 ***