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.
Created attachment 929366[details]
foreman-debug
Description of problem:
The foreman-tasks service is failing to start on RHEL 7 after generating a new compose with updated foreman-selinux rules for RHEL 7. Perhaps interestingly, running the installer again or trying to restart http and foreman-tasks in permissive mode is still resulting in foreman-tasks failing to start:
Could not start Service[foreman-tasks]: Execution of '/usr/bin/systemctl start foreman-tasks' returned 1: Job for foreman-tasks.service failed. See 'systemctl status foreman-tasks.service' and 'journalctl -xn' for details.
/Stage[main]/Foreman::Plugin::Tasks/Service[foreman-tasks]/ensure: change from stopped to running failed: Could not start Service[foreman-tasks]: Execution of '/usr/bin/systemctl start foreman-tasks' returned 1: Job for foreman-tasks.service failed. See 'systemctl status foreman-tasks.service' and 'journalctl -xn' for details.
I'm unsure as to whether this is a selinux problem or not at this point.
Version-Release number of selected component (if applicable):
Satellite-6.0.4-RHEL-7-20140821.0
How reproducible:
Seems always, QE reported the same problem
Comment 1RHEL Program Management
2014-08-21 22:33:08 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
This was due to ruby193-rubygem-foreman-tasks tagging issue in brew resulting from work for getting things set up for errata tool. This and one other package were downgraded inadvertantly, but this should be fixed now.
Created attachment 929366 [details] foreman-debug Description of problem: The foreman-tasks service is failing to start on RHEL 7 after generating a new compose with updated foreman-selinux rules for RHEL 7. Perhaps interestingly, running the installer again or trying to restart http and foreman-tasks in permissive mode is still resulting in foreman-tasks failing to start: Could not start Service[foreman-tasks]: Execution of '/usr/bin/systemctl start foreman-tasks' returned 1: Job for foreman-tasks.service failed. See 'systemctl status foreman-tasks.service' and 'journalctl -xn' for details. /Stage[main]/Foreman::Plugin::Tasks/Service[foreman-tasks]/ensure: change from stopped to running failed: Could not start Service[foreman-tasks]: Execution of '/usr/bin/systemctl start foreman-tasks' returned 1: Job for foreman-tasks.service failed. See 'systemctl status foreman-tasks.service' and 'journalctl -xn' for details. I'm unsure as to whether this is a selinux problem or not at this point. Version-Release number of selected component (if applicable): Satellite-6.0.4-RHEL-7-20140821.0 How reproducible: Seems always, QE reported the same problem