Description of problem: If I enter an incorrect IP address under 2E. Storage for a RHEV deployment's NFS mountpoint, then I get a warning message on 4A. Installation Review like the following: "Could not connect to address '192.168.0.1'. Make sure the NFS server exists and is up." Nothing prevents me from clicking the Deploy button, and then getting all the way through to 87.5% of the RHEV progress bar, at which point the hosts can't mount NFS and the task eventually times out after 24 hours. Is there a reason why the Deploy button isn't disabled? It seems unlikely to me that the Satellite would fail the NFS validation test while the hosts would succeed. Either the test should succeed, or we should maybe confirm (with a "yes, I really want to continue" checkbox or something) that the user REALLY wants to ignore the warning and understands that the deployment may fail. Version-Release number of selected component (if applicable): RHCI-6.0-RHEL-7-20160208.1-RHCI-x86_64 How reproducible: 100% Steps to Reproduce: 1.) See above. Actual results: Can ignore NFS validation failure, resulting in failed deployment. Expected results: Can't ignore NFS validation failure. Additional info:
Hi Tasos, Yes, there are cases where the Satellite is unable to mount the NFS share but a provisioned host (engine/hypervisor) would be able to. For this reason we ensure that a user has the means to continue and by-pass our warnings.