Project

General

Profile

Actions

Bug #26664

closed

OpenStack 401 when project domain ID is missing

Added by Lukas Zapletal about 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources - OpenStack
Target version:
-
Difficulty:
Triaged:
Yes
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 4 (1 open3 closed)

Related to Foreman - Feature #12054: Openstack v3 supportClosed10/05/2015Actions
Related to Hammer CLI - Feature #26668: Add project_domain_name and project_domain_id fields to Foreman moduleClosedLukas ZapletalActions
Related to Foreman - Bug #27076: Compute Resource Openstack API v2/v3 mismatchNewActions
Related to Foreman - Bug #28307: Openstack V3 compute resource brokenRejectedActions
Actions #1

Updated by Lukas Zapletal about 5 years ago

Actions #2

Updated by Lukas Zapletal about 5 years ago

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

Updated by The Foreman Bot about 5 years ago

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

Updated by Marek Hulán almost 5 years ago

  • Fixed in Releases 1.23.0 added
Actions #5

Updated by Anonymous almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #6

Updated by Anthony Chevalet over 4 years ago

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

Updated by Anthony Chevalet over 4 years ago

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

Also available in: Atom PDF