Hide Forgot
Description of problem: ==================================== Installed on a fresh rhel 6.2 install from brew-nightly (rpms version below). Configured for rhevm but when I went to add a realm mapping to the rhevm cluster, the rhevm cluster is not listed in conductor's realm drop down. No errors in the logs from what I can tell, rhevm is online and works when using rpms (deltacloud-core-rhevm-0.4.1-8.el6.noarch) from aeolus-testing repo, and the provider test connection succeeds in the ui so I am thinking there is some issue with deltacloud-rhevm v0.5 which is in brew-nightly. Version-Release number of selected component (if applicable): ======================================================================== [root@qeblade29 init.d]# rpm -qa | grep deltacloud deltacloud-core-rhevm-0.5.0-0.rc1.el6.noarch deltacloud-core-0.5.0-0.rc1.el6.noarch deltacloud-core-ec2-0.5.0-0.rc1.el6.noarch deltacloud-core-vsphere-0.5.0-0.rc1.el6.noarch rubygem-deltacloud-client-0.4.0-3.el6.noarch
Un-installing the v0.5 rpms that came from brew nightly and re-installing with v0.4.1-8 did resolve the issue.
changed config to rhevm_nfs_server: qeblade26.rhq.lab.eng.bos.redhat.com rhevm_nfs_export: /home/rhevm_export rhevm_nfs_mount_point: /mnt/rhevm-nfs rhevm_deltacloud_username: admin@iasdf rhevm_deltacloud_password: asdf rhevm_deltacloud_provider: https://qeblade26.rhq.lab.eng.bos.redhat.com:8443/api;4c96c74b-f8b6-4c8f-aa84-a55770839b85 rhevm_push_timeout: 1800 get the following error during configure: notice: /Stage[main]/Aeolus::Image-factory/Service[imagefactory]/ensure: ensure changed 'stopped' to 'running' err: /Stage[main]/Aeolus::Profiles::Rhevm/Web_request[rhevm-check-export-path-is-export-type]/get: change from to https://qeblade26.rhq.lab.eng.bos.redhat.com:8443/api;4c96c74b-f8b6-4c8f-aa84-a55770839b85/storagedomains?search=export failed: An exception was raised when invoking web request: Invalid HTTP Return Code: 404, was expecting one of 200 notice: /Stage[main]/Aeolus::Profiles::Rhevm/Mount[/mnt/rhevm-nfs]: Dependency Web_request[rhevm-check-export-path-is-export-type] has failures: true warning: /Stage[main]/Aeolus::Profiles::Rhevm/Mount[/mnt/rhevm-nfs]: Skipping because of failed dependencies notice: /Stage[main]/Aeolus::Iwhd/Service[mongod]/ensure: ensure changed 'stopped' to 'running' notice: /Stage[main]/Aeolus::Iwhd/Service[iwhd]/ensure: ensure changed 'stopped' to 'running' notice: /Stage[main]/Aeolus::Iwhd/Exec[iwhd_startup_pause]/returns: executed successfully notice: /Stage[main]/Aeolus::Profiles::Rhevm/Aeolus::Create_bucket[aeolus]/Exec[create-bucket-aeolus]/returns: % Total % Received % Xferd Average Speed Time Time Time Current notice: /Stage[main]/Aeolus::Profiles::Rhevm/Aeolus::Create_bucket[aeolus]/Exec[create-bucket-aeolus]/returns: Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0c[create-bucket-aeolus]/returns: notice: /Stage[main]/Aeolus::Profiles::Rhevm/Aeolus::Create_bucket[aeolus]/Exec[create-bucket-aeolus]/returns: executed successfully notice: Finished catalog run in 83.03 seconds
Details of the Deltacloud-core rhevm provider/datacenter change are in the links below: https://teambox.com/projects/deltacloud/tasks/586718 https://issues.apache.org/jira/browse/DTACLOUD-117
A fix as been committed to aeolus-configure as f3d033e0ebb2dca32fde0ba67277a3e3040e0eb1 To support data centers, the RHEVM provider URL is now in this form: https://rhevm-rest-api-server:port/api;datacenter-uuid Removed rhevm_deltacloud_provider configuration parameter and replaced it with rhevm_deltacloud_api which represents the url to the REST API and with rhevm_deltacloud_data_center which represents the data center uuid. In the example above, rhevm_deltacloud_api = https://rhevm-rest-api-server:port/api rhevm_deltacloud_data_center = datacenter-uuid
Available in aeolus-configure-2.5.0-3.el6.noarch.rpm.
good to go with aeolus-configure-2.5.0-3.el6.noarch
bugs in verified or on_qa moving off tracker
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. http://rhn.redhat.com/errata/RHEA-2012-0586.html