Description of problem: New installation of spacewalk on CENTOS 7: error on package spacewalk-selinux-2.3.2-1.el7 : Version-Release number of selected component (if applicable): spacewalk-selinux-2.3.2-1.el7.noarch.rpm How reproducible: Steps to Reproduce: 1.rpm -ivh --replacepkgs /tmp/spacewalk-selinux-2.3.2-1.el7.noarch.rpm 2. 3. Actual results: Failed to resolve roletype statement at /etc/selinux/mls/tmp/modules/400/spacewalk/cil:2 /usr/sbin/semodule: Failed! Failed to resolve roletype statement at /etc/selinux/strict/tmp/modules/400/spacewalk/cil:2 /usr/sbin/semodule: Failed! Expected results: Additional info:
The command `/usr/sbin/semodule -s ${selinuxvariant} -l` used to return a failure exit code, but that has now changed on RHEL and CentOS 7. thanks to mmraka for pointing out an alternate command `/usr/sbin/semanage module -l -S ${selinuxvariant}` that continues to return a failure status code. Should the `semanage module ...` command be changed to always return success status code, mmraka also suggested an alternative check with `if [ $(/usr/sbin/semodule -s ${selinuxvariant} -l | wc -l) -gt 1 ]; then` ...
In addition to updating the spacewalk-selinux-enable script, the osa-dispatcher-selinux-enable script also needed the same fix.
spacewalk.github: b495b84d322ee1942096d6e0fd7771637a3033b9
(In reply to Eric Herget from comment #3) > spacewalk.github: > b495b84d322ee1942096d6e0fd7771637a3033b9 Hi Eric. I am deploying Spacewalk for my company to manage a pile of CentOS 7 VMs, and I just ran into this SELinux error when installing the Spacewalk 2.6 packages. I tracked down your fix on Github, and ran the two fixed loops of semanage that had otherwise bombed during the installation. I was wondering whether that was a correct approach, and also whether updated packages for Spacewalk 2.6 might be released?
(In reply to Troels Just from comment #4) > (In reply to Eric Herget from comment #3) > > spacewalk.github: > > b495b84d322ee1942096d6e0fd7771637a3033b9 > > Hi Eric. > I am deploying Spacewalk for my company to manage a pile of CentOS 7 VMs, > and I just ran into this SELinux error when installing the Spacewalk 2.6 > packages. > > I tracked down your fix on Github, and ran the two fixed loops of semanage > that had otherwise bombed during the installation. I was wondering whether > that was a correct approach, and also whether updated packages for Spacewalk > 2.6 might be released? Hi Troels, Yes, running the two loops of semanage should apply the necessary config. This fix is found in the nightly builds and will be included in the upcoming Spacewalk 2.7 release in the next few weeks.
Spacewalk 2.7 has been released. https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes27