Red Hat Bugzilla – Bug 1248485
[New] - Add a point in the install guide to move host to maintenance before enabling selinux on the RHGS nodes managed via console.
Last modified: 2017-11-17 00:29:36 EST
Description of problem:
vdsm fails to start when user tries to change selinux from disabled to permissive mode and following is seen in the /var/log/boot.log
libvirt is already configured for vdsm
Modules sebool are not configured
One of the modules is not configured to work with VDSM.
To configure the module use the following:
'vdsm-tool configure [--module module-name]'.
If all modules are not configured try to use:
'vdsm-tool configure --force'
(The force flag will stop the module's service and start it
afterwards automatically to load the new configuration.)
vdsm: stopped during execute check_is_configured task (task returned with error code 1).
This issue occurs only for the first time when user upgrades 3.0.4 to 3.1 and changes selinux from disabled to permissive. Once user runs vdsm-tool configure --force and starts vdsm / reinstall the node from UI this issue will not be seen when user switches between disabled to permissive and permissive to disabled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add 3.0.4 nodes to console
2. Upgrade RHGS nodes from 3.0.4 to 3.1
3. Now change the selinux from disabled to permissive and reboot the system
4. Nodes in console goes to non responsive mode.
vdsm does not restart sucessfully, but running 'vdsm-tool configure --force' on rhgs brings vdsm up or reinstalling the nodes brings up the nodes.
vdsm should be restarted sucessfully.
In 18.104.22.168. Enabling SELinux section add a step which says put the RHGS nodes added to console into maintenance and reinstall the nodes once selinux configuration has been done.
Made the changes as suggested. Could you please verify.
Looks good to me
Based on Comment 4, moving the bug ON_QA
Documentation is clear and closing it as verified