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
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.
I believe this went out in Satellite 6.0. If not, please re-open.