Bug 1411020
| Summary: | OpenStack + CloudForms deployment validation failing due to RHEV export domain missing information | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Quickstart Cloud Installer | Reporter: | Landon LaSmith <llasmith> | ||||
| Component: | WebUI | Assignee: | cchase | ||||
| Status: | CLOSED ERRATA | QA Contact: | Tasos Papaioannou <tpapaioa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 1.1 | CC: | cchase, joden, juwu, qci-bugzillas, tpapaioa | ||||
| Target Milestone: | --- | Keywords: | Automation, AutomationBlocker, 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:43:21 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: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Landon LaSmith
2017-01-07 14:31:20 UTC
Created attachment 1238248 [details]
Screenshot of deployment validation
Definitely saw this last Friday when trying to do an OSP+CFME deployment using Ceph. Work around is to add a valid RHV export domain path using the fusor api. No info is needed for the data domain.
curl -k -X PUT -u admin:changeme https://<fusor api>/fusor/api/v21/deployments/<deployment id> -H "Content-Type: application/json" -d '{deployment: { "rhev_export_domain_name": "my_export", "rhev_export_domain_path": "/var/lib/exports/exports", "rhev_export_domain_address": "192.169.0.1"}}'
https://github.com/fusor/fusor/pull/1325 Those validations should only be checked on RHV/CFME, now. *** Bug 1410677 has been marked as a duplicate of this bug. *** Verified on QCI-1.1-RHEL-7-20170111.t.8. 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 |