| Summary: | AMQP port is ignored for OpenStack AMQP endpoint | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Pete Savage <psavage> |
| Component: | Providers | Assignee: | Ladislav Smola <lsmola> |
| Status: | CLOSED ERRATA | QA Contact: | Ola Pavlenko <opavlenk> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.6.0 | CC: | dclarizi, jfrey, jhardy, obarenbo, psavage, simaishi |
| Target Milestone: | GA | ||
| Target Release: | 5.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.6.0.6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-29 15:54:50 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: | |
|
Description
Pete Savage
2016-04-26 13:28:21 UTC
Dan, can someone in UI look at this and make sure that the port is not getting lost in the Angular form? Pete,
I have a couple questions.
1. Did you say you set the AMQP port to 5000 and the DB also shows that?
If yes, then this is not a UI issue
2. How did you infer that your AMQP port is not being used?
In the production.log I see this when I hit validate
[----] I, [2016-04-26T16:24:32.399868 #3179:15b871c] INFO -- : Parameters: {"utf8"=>"✓", "authenticity_token"=>"i4E8U0htqaRCHxfjGchLNcsKvT07BWsLWAO00IfVxeZOm6tbynOlXGsCc4XXFCyjNaBaOkrWrwd9aAVVQ/eqeg==", "button"=>"validate", "cred_type"=>"amqp", "name"=>"test", "emstype"=>"openstack_infra", "api_version"=>"v2", "zone"=>"default", "default_userid"=>"", "default_password"=>"[FILTERED]", "default_verify"=>"[FILTERED]", "default_hostname"=>"aaa", "default_api_port"=>"5000", "default_security_protocol"=>"ssl-with-validation", "amqp_hostname"=>"bbb", "amqp_api_port"=>"1111", "amqp_security_protocol"=>"ssl", "amqp_userid"=>"a", "amqp_password"=>"[FILTERED]", "amqp_verify"=>"[FILTERED]", "ssh_keypair_userid"=>"", "ssh_keypair_password"=>"[FILTERED]", "ssh_keypair_verify"=>"[FILTERED]"}
Notice that amqp_api_port (AMQP Port) is passed correctly to the backend (I set it to 1111 in my test)
Yes, in my additional info, I have seen that the database is storing the right port number in the endpoints table. The issue seems to be the provider subsystem using that value. If I do a netstat on the appliance I see a constant connection to 5672, which is obviously the "right" port, but not the one I requested. So I do not believe this is a UI issue. Ladas, can you take a look at this? I believe you're actually already looking at it. New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/8c84e6af4b2a999b3cdfe197e95c7fa9b3b81264 commit 8c84e6af4b2a999b3cdfe197e95c7fa9b3b81264 Author: Ladislav Smola <lsmola> AuthorDate: Wed Apr 27 19:58:39 2016 +0200 Commit: Ladislav Smola <lsmola> CommitDate: Thu May 5 11:43:12 2016 +0200 OpenStack AMQP doesn't use endpoint data OpenStack AMQP doesn't use endpoint data, whcih is being fixed. Fixes BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1330568 Fixes Issue: https://github.com/ManageIQ/manageiq/issues/8158 .../manageiq/providers/openstack/manager_mixin.rb | 20 ++++++++++++-------- gems/pending/openstack/openstack_event_monitor.rb | 2 +- 2 files changed, 13 insertions(+), 9 deletions(-) In case the port is correct the validation passed, changing the port throws: Credential validation was not successful: Socket error: Could not establish TCP connection to any of the configured hosts 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 |