Bug 1596320
| Summary: | 404 error accessing OpenStack console | |||
|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | jritenou | |
| Component: | Providers | Assignee: | Gilles Dubreuil <gdubreui> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ido Ovadia <iovadia> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 5.9.0 | CC: | cpelland, gblomqui, gdubreui, ikaur, jfrey, jhardy, jprause, maufart, obarenbo, peli, simaishi | |
| Target Milestone: | GA | Keywords: | TestOnly, ZStream | |
| Target Release: | 5.10.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 5.10.0.11 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1603022 (view as bug list) | Environment: | ||
| Last Closed: | 2019-02-11 14:06:40 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: | ||||
| Bug Depends On: | 1615796, 1622471 | |||
| Bug Blocks: | 1603022 | |||
The same error message is reproduced using ManageIQ with current master branch. Upstream to be patched and back ported accordingly. This is happening because the 'get_vnc_console' method from fog-openstack is called by default. Unfortunately this method is deprecated for Nova (Compute) microversion 2.5 and not supported after 2.6. The following patch [1] adds the 'remote_consoles' request method which should be used from now on. The patch also forces the 'get_vnc_console' to use microversion 2.5 when the microversion is greater. Once that patch has been merged and a newer version of fog-openstack has been released, then fog-openstack gem used by ManageIQ will need to be bumped up. We'll have to confirm that the latest can be applied safely to 5.9.x. [1] https://github.com/fog/fog-openstack/pull/407 Fog-openstack patch has been merged. Now bumping fog-openstack version up within manageiq-providers-openstack repo. https://github.com/ManageIQ/manageiq-providers-openstack/pull/317 I tested fog-openstack version 0.1.27 can be used against 5.9.x (latest Gaprindashvili branch). Patch https://github.com/ManageIQ/manageiq-providers-openstack/pull/317 has been flagged for back port. Failed QA ========= CFME 5.10.0.8 Access to VM Console is missing on UI https://bugzilla.redhat.com/show_bug.cgi?id=1615796 This is now working fine with latest Gaprindashvili. Putting back to ON_QA, as BZ mentioned in Comment 12 is ON_QA. Verified ======== 5.10.0.23 |
Description of problem: On latest CF 4.6 release, trying to access VM console against OpenStack (RH OSP 10 provider), I get a 404 error. I cannot say for sure if this affects other version of OSP, as 10 is the only one I have easy access to ATM. Version-Release number of selected component (if applicable): cfme-5.9.2.4 How reproducible: Always Steps to Reproduce: 1. Add OSP 10 provider (keystone v2/v3 doesn't seem to matter) 2. Attempt to open console on instance running on OSP 3. Actual results: Console access failed: Expected([200, 202]) <=> Actual(404 Not Found) excon.error.response :body => "{\"itemNotFound\": {\"message\": \"The resource could not be found.\", \"code\": 404}}" :cookies => [ ] :headers => { "Content-Length" => "78" "Content-Type" => "application/json; charset=UTF-8" "Date" => "Wed, 27 Jun 2018 19:42:53 GMT" "Openstack-Api-Version" => "compute 2.15" "Vary" => "OpenStack-API-Version, X-OpenStack-Nova-API-Version" "X-Compute-Request-Id" => "req-f49b317d-43cd-4090-8704-56bf7f844a63" "X-Openstack-Nova-Api-Version" => "2.15" } :host => "192.168.1.40" :local_address => "172.16.0.17" :local_port => 58706 :path => "/v2.1/servers/a28883a6-ef07-43bd-b3a5-c9d7c971fa8d/action" :port => 8774 :reason_phrase => "Not Found" :remote_ip => "192.168.1.40" :status => 404 :status_line => "HTTP/1.1 404 Not Found\r\n" Expected results: Console access. Additional info: See ManageIQ git issue - https://github.com/ManageIQ/manageiq/issues/17619. The proposed fix does appear to work.