Description of problem: While creating a RHEV + OSE deployment, I enter the following NFS share info on the RHEV > Storage tab: Storage Address: 192.168.100.1 Share Path: /var/lib/exports/vms The IP address is the IP address of the Satellite on the provisioning network, and the share was created with fusor-local-nfs-setup. After I click Next, the following warning message appears on the OpenShift > Master/Nodes tab: "Failed to mount NFS share, could not load available disk space" Version-Release number of selected component (if applicable): QCI-1.2-RHEL-7-20160513.t.0 How reproducible: 100% Steps to Reproduce: 1.) Create NFS share on Satellite with fusor-local-nfs-setup. 2.) Create RHEV+OSE deployment, and enter NFS share information. 3.) See "Failed to mount NFS share, could not load available disk space" message. Actual results: NFS mount and disk space check failed, error message displayed. Expected results: Successful NFS mount and disk space check, no error message. Additional info: /var/log/secure and /var/log/audit/audit.log show that safe-mount.sh failed due to an SELinux denial: ==> /var/log/secure <== May 16 14:07:27 localhost sudo: foreman : TTY=unknown ; PWD=/usr/share/foreman ; USER=root ; COMMAND=/bin/safe-mount.sh 3 192.168.100.1 /var/lib/exports/vms May 16 14:07:27 localhost sudo: PAM audit_log_acct_message() failed: Permission denied ==> /var/log/audit/audit.log <== type=AVC msg=audit(1463422047.385:909): avc: denied { getattr } for pid=29939 comm="diagnostic_con*" name="/" dev="0:40" ino=133 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:nfs_t:s0 tclass=filesystem type=SYSCALL msg=audit(1463422047.385:909): arch=c000003e syscall=137 success=no exit=-13 a0=7ff6b6d68fb8 a1=7ff6db26d020 a2=30 a3=7ff6db26d0b0 items=0 ppid=29894 pid=29939 auid=4294967295 uid=991 gid=988 euid=991 suid=991 fsuid=991 egid=988 sgid=988 fsgid=988 tty=(none) ses=4294967295 comm="diagnostic_con*" exe="/opt/rh/rh-ruby22/root/usr/bin/ruby" subj=system_u:system_r:passenger_t:s0 key=(null) These same errors also appear when creating a RHEV-only deployment, but there is no warning in the web UI. Temporarily disabling SELinux with 'setenforce 0' resolves the issue.
I saw this while doing testing and fixed it. The issue is as you stated an selinux error and should be fixed in the latest version of the package on the latest ISO.
Verified on QCI-1.2-RHEL-7-20160621.t.0.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1862