Project

General

Profile

Bug #28307

Openstack V3 compute resource broken

Added by Anthony Chevalet over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Compute resources - OpenStack
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hi, I've just updated to 1.23.2 and I'm still not able to create new (or manage existing) openstack compute resources. It was working fine on 1.21 and started to fail on 1.22 with corrupted keystone url. It now uses the correct v3 url according to the log but I still get 401 permission issue.

URL: https://openstack.com:5000/v3/auth/tokens
Project: myproject
User Domain: mydomain
Project domain name/id: tried 'mydomain' and/or 'default' or nothing (doc would be very welcome))

payload in log:

2019-11-19T18:03:29 [I|app|1bea54f5]   Parameters: {"utf8"=>"✓", "authenticity_token"=>"xxx==", "compute_resource"=>{"name"=>"mycptres", "description"=>"", "url"=>"https://openstack.com:5000/v3/auth/tokens", "user"=>"xxx", "password"=>"[FILTERED]", "tenant"=>"myproject", "domain"=>"mydomain", "project_domain_name"=>"mydomain", "project_domain_id"=>"default", "allow_external_network"=>"0", "location_ids"=>["5", ""], "organization_ids"=>["3", ""]}, "fakepassword"=>"[FILTERED]", "cr_id"=>"5"}

error in ui:

Expected([200, 201]) <=> Actual(401 Unauthorized) excon.error.response :body => "{\"error\": {\"message\": \"The request you have made requires authentication.\", \"code\": 401, \"title\": \"Unauthorized\"}}" :cookies => [ ] :headers => { "Connection" => "close" "Content-Length" => "114" "Content-Type" => "application/json" "Date" => "Tue, 19 Nov 2019 18:03:29 GMT" "Server" => "Apache" "Vary" => "X-Auth-Token" "WWW-Authenticate" => "Keystone uri=\"https://openstack.com:5000\"" "x-openstack-request-id" => "req-xxx" } :host => "openstack.com" :local_address => "172.1.1.4" :local_port => 33704 :path => "/v3/auth/tokens" :port => 5000 :reason_phrase => "Unauthorized" :remote_ip => "xxx" :status => 401 :status_line => "HTTP/1.1 401 Unauthorized\r\n" 

I'm not sure about the new params project_domain_name and project_domain_id.
Previously we just gave the user domain and we had a drop down list with user's tenants. Adding 2 parameters and a user input box is kind of regression.


Related issues

Related to Hammer CLI - Feature #26668: Add project_domain_name and project_domain_id fields to Foreman moduleClosed
Related to Foreman - Bug #26664: OpenStack 401 when project domain ID is missingClosed
Related to Foreman - Feature #12054: Openstack v3 supportClosed2015-10-05

History

#1 Updated by Anthony Chevalet over 2 years ago

  • Related to Feature #26668: Add project_domain_name and project_domain_id fields to Foreman module added

#2 Updated by Anthony Chevalet over 2 years ago

  • Related to Bug #26664: OpenStack 401 when project domain ID is missing added

#3 Updated by Anthony Chevalet over 2 years ago

#4 Updated by Tomer Brisker over 2 years ago

  • Category set to Compute resources - OpenStack

#6 Updated by Anthony Chevalet about 2 years ago

  • Status changed from New to Rejected

I'm going to close this as there is no issue on Foreman side, it works perfectly well after applying this patch on fog-openstack: https://github.com/fog/fog-openstack/pull/513

Also available in: Atom PDF