Bug 1303959
Summary: | When the Openstack cloud provider AMQP server isn't reachable an Unknown reason is shown for credentials validation | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Marius Cornea <mcornea> |
Component: | Providers | Assignee: | Ladislav Smola <lsmola> |
Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.5.0 | CC: | gblomqui, jfrey, jhardy, mfeifer, obarenbo, simaishi |
Target Milestone: | GA | ||
Target Release: | 5.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | openstack | ||
Fixed In Version: | 5.6.0.8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-29 15:35:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | Openstack | Target Upstream Version: | |
Embargoed: |
Description
Marius Cornea
2016-02-02 14:25:49 UTC
Assigning to add test case New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/5ad1662e596e7a598acfd93f7b0ae4734fe1f2cc commit 5ad1662e596e7a598acfd93f7b0ae4734fe1f2cc Author: Ladislav Smola <lsmola> AuthorDate: Thu May 12 15:51:17 2016 +0200 Commit: Ladislav Smola <lsmola> CommitDate: Mon May 16 17:26:14 2016 +0200 Do not hide AMQP exception for validation Do not hide AMQP exception for validation Fixes BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1303959 .../manageiq/providers/openstack/manager_mixin.rb | 7 +++++-- .../events/openstack_ceilometer_event_monitor.rb | 2 +- .../events/openstack_rabbit_event_monitor.rb | 2 +- gems/pending/openstack/openstack_event_monitor.rb | 24 +++++++++++++--------- 4 files changed, 21 insertions(+), 14 deletions(-) Validated on cfme 5.6.0.9 rc2 credentials for rabbitmq validation successful 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/RHBA-2016:1348 |