Description of problem: Lock root account Locking password for user root. passwd: Success ERROR: policydb magic number 0x000008 does not match expected magic number 0xf97cff8c or 0xf97cff8d ERROR: Unable to open policy /sys/fs/selinux/policy. Traceback (most recent call last): File "/sbin/semanage", line 25, in <module> import seobject File "/usr/lib64/python2.7/site-packages/seobject.py", line 27, in <module> import sepolicy File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 61, in <module> policy(policy_file) File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 54, in policy raise ValueError(_("Failed to read % policy file") % policy_file) ValueError: unsupported format character 'p' (0x70) at index 17 Version-Release number of selected component (if applicable): http://jenkins.ovirt.org/job/ovirt-node-iso-devel/1422/console
Installing: vdsm ##################### [556/582]ERROR: policydb magic number 0x000008 does not match expected magic number 0xf97cff8c or 0xf97cff8d ERROR: Unable to open policy /sys/fs/selinux/policy. Traceback (most recent call last): File "/usr/bin/vdsm-tool", line 143, in <module> sys.exit(main()) File "/usr/bin/vdsm-tool", line 125, in main load_modules() File "/usr/bin/vdsm-tool", line 74, in load_modules module = imp.load_module(mod_name, mod_fobj, mod_absp, mod_desc) File "/usr/lib64/python2.7/site-packages/vdsm/tool/seboolsetup.py", line 21, in <module> import seobject File "/usr/lib64/python2.7/site-packages/seobject.py", line 27, in <module> import sepolicy File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 61, in <module> policy(policy_file) File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 54, in policy raise ValueError(_("Failed to read % policy file") % policy_file) ValueError: unsupported format character 'p' (0x70) at index 17 ERROR: policydb magic number 0x000008 does not match expected magic number 0xf97cff8c or 0xf97cff8d ERROR: Unable to open policy /sys/fs/selinux/policy. Traceback (most recent call last): File "/usr/bin/vdsm-tool", line 143, in <module> sys.exit(main()) File "/usr/bin/vdsm-tool", line 125, in main load_modules() File "/usr/bin/vdsm-tool", line 74, in load_modules module = imp.load_module(mod_name, mod_fobj, mod_absp, mod_desc) File "/usr/lib64/python2.7/site-packages/vdsm/tool/seboolsetup.py", line 21, in <module> import seobject File "/usr/lib64/python2.7/site-packages/seobject.py", line 27, in <module> import sepolicy File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 61, in <module> policy(policy_file) File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 54, in policy raise ValueError(_("Failed to read % policy file") % policy_file) ValueError: unsupported format character 'p' (0x70) at index 17
Dan, can you say what problems we are seeing here? First to me it seems as if there is an incorrect py format string: raise ValueError(_("Failed to read % policy file") % policy_file) ValueError: unsupported format character 'p' (0x70) at index 17 But I can't say anything about: ERROR: policydb magic number 0x000008 does not match expected magic number 0xf97cff8c or 0xf97cff8d ERROR: Unable to open policy /sys/fs/selinux/policy.
Snippet from comment #1 was take from http://jenkins.ovirt.org/view/ovirt_node/job/ovirt-node-iso-devel/1506/console
What OS is this happening on? rpm -q selinux-policy policycoreutils
Fedora 18 based ovirt-node upstream of RHEV-H policycoreutils-2.1.13-49.fc18.x86_64 selinux-policy-3.11.1-67.fc18.noarch entire rpm manifest if needed: http://jenkins.ovirt.org/view/ovirt_node/job/ovirt-node-iso-devel/1506/artifact/manifest-rpm.txt
Mike, I still see this errors in recent builds, e.g. http://jenkins.ovirt.org/view/ovirt_node/job/ovirt-node-iso-devel/1574/consoleFull , is there a way how Dan can gain access? Maybe we can sort this out w/ someone from the infra team ...
Defer this for now. My fully updated F18 host will build with no issues. I will work with the infra team to update the jenkins hosts there and see if we can solve this with a simple yum update. Not something to block releasing an F18 node on though.
Still seeing this after yum update. Trying to get access to the machine for Dan.
This should be fixed - as much as it can - with teh new policy and the new selinux policy subpackage.
http://gerrit.ovirt.org/#/c/14052/