workaround #1402427 in support_server

support_server was failing because of #1402427. I re-generated
the disk image with latest F25 so the fixed selinux-policy is
used, but even then, it seems we have to run 'restorecon' on
rpcbind manually before starting nfs.
This commit is contained in:
Adam Williamson 2016-12-13 16:38:22 -08:00
parent 44cf1cd89c
commit d8ba53aefc

View File

@ -54,6 +54,9 @@ sub run {
assert_script_run "printf '/export 10.0.2.0/24(ro)\n/repo 10.0.2.0/24(ro)' > /etc/exports"; assert_script_run "printf '/export 10.0.2.0/24(ro)\n/repo 10.0.2.0/24(ro)' > /etc/exports";
# open firewall port # open firewall port
assert_script_run "firewall-cmd --add-service=nfs"; assert_script_run "firewall-cmd --add-service=nfs";
# workaround RHBZ #1402427: somehow the file is incorrectly labelled
# even after a clean install with fixed selinux-policy
assert_script_run "restorecon /usr/bin/rpcbind";
# start the server # start the server
assert_script_run "systemctl restart nfs-server.service"; assert_script_run "systemctl restart nfs-server.service";
assert_script_run "systemctl is-active nfs-server.service"; assert_script_run "systemctl is-active nfs-server.service";