| Summary: | Occasional error when configuring storage for self-hosted deployment | ||
|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | Tasos Papaioannou <tpapaioa> |
| Component: | WebUI | Assignee: | Derek Whatley <dwhatley> |
| Status: | CLOSED ERRATA | QA Contact: | Landon LaSmith <llasmith> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.1 | CC: | dwhatley, jmatthew, llasmith, qci-bugzillas |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | 1.1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-28 01:41:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This BZ is addressed in fusor PR 1302 and fusor-utils PR 7 (both merged). Based on the log messages given, believe the problem manifests when multiple mount validations attempt to use the same mount point at the same time. Each type of storage (rhv, self-hosted, export, ocp) now gets a dedicated test mount point. https://github.com/fusor/fusor/pull/1302 https://github.com/fusor/fusor-utils/pull/7 Built in fusor-server 1.1.16-1 Built in fusor-utils 1.1.0-2 VERIFIED. Automated runs have seen a sharp reduction (if not elimination) in the number of storage mount errors since this update QCI Media Version: QCI-1.1-RHEL-7-20161212.t.2 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-2017:0335 |
Description of problem: When creating a self-hosted RHV deployment, occasionally I get the error message "Error mounting self-hosted domain my_hosted_storage, please make sure it is a valid mount point" after entering valid IP addresses and paths for my_storage and my_hosted_storage domains on NFS. Other times I can enter the exact same information and there will be no error. /var/log/foreman/production.log shows: **** 2016-11-17 13:09:24 [app] [I] Processing by Fusor::Api::V21::DeploymentsController#check_mount_point as JSON 2016-11-17 13:09:24 [app] [I] Parameters: {"path"=>"/home/export/data_domain", "address"=>"192.168.100.254", "type"=>"NFS", "api_version"=>"v21", "i d"=>"28", "deployment"=>{}} 2016-11-17 13:09:24 [app] [I] Processing by Fusor::Api::V21::DeploymentsController#check_mount_point as JSON 2016-11-17 13:09:24 [app] [I] Parameters: {"path"=>"/home/export/self_hosted_domain", "address"=>"192.168.100.254", "type"=>"NFS", "api_version"=>"v 21", "id"=>"28", "deployment"=>{}} 2016-11-17 13:09:24 [app] [E] Error running command: sudo safe-mount.sh '28' '192.168.100.254' '/home/export/self_hosted_domain' 'nfs' 2016-11-17 13:09:24 [app] [E] Status code: 1 2016-11-17 13:09:24 [app] [E] Command output: sudo: unable to send audit message: Permission denied | mount.nfs: /tmp/fusor-test-mount-28 is busy or already mounted | Failed to mount nfs share | **** In this example, the Satellite is on the same subnet, w/ IP address 192.168.100.1. Version-Release number of selected component (if applicable): QCI-1.1-RHEL-7-20161111.n.0 How reproducible: Occasional Steps to Reproduce: 1.) Create a new deployment for RHV self-hosted. 2.) Enter valid IP address and paths for NFS shares. 3.) See error message at the top of the page when clicking Next. Actual results: Error message when testing NFS mount. Expected results: No error for valid NFS share. Additional info: