Project

General

Profile

Bug #26664

OpenStack 401 when project domain ID is missing

Added by Lukas Zapletal 8 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources - OpenStack
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

When creating new OpenStack CR against OSP v13 a permission denied (401) error is returned. I have narrowed this down to the fact to missing flag openstack_domain_id.
When it's provided, the CR authenticates fine, since it is mentioned as mandatory for V3 in https://github.com/fog/fog-openstack this patch is going to add it.


Related issues

Related to Foreman - Feature #12054: Openstack v3 supportClosed2015-10-05
Related to Hammer CLI - Feature #26668: Add project_domain_name and project_domain_id fields to Foreman moduleClosed
Related to Foreman - Bug #27076: Compute Resource Openstack API v2/v3 mismatchNew
Related to Foreman - Bug #28307: Openstack V3 compute resource brokenNew

Associated revisions

Revision 047aca17 (diff)
Added by Lukáš Zapletal 5 months ago

Fixes #26664 - adds OpenStack project domain (#6706)

History

#1 Updated by Lukas Zapletal 8 months ago

#2 Updated by Lukas Zapletal 8 months ago

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

#3 Updated by The Foreman Bot 8 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6706 added

#4 Updated by Marek Hulán 5 months ago

  • Fixed in Releases 1.23.0 added

#5 Updated by Anonymous 5 months ago

  • Status changed from Ready For Testing to Closed

#6 Updated by Anthony Chevalet 18 days ago

  • Related to Bug #27076: Compute Resource Openstack API v2/v3 mismatch added

#7 Updated by Anthony Chevalet 18 days ago

  • Related to Bug #28307: Openstack V3 compute resource broken added

Also available in: Atom PDF