The template previously could use v2.0 depending on the value of
api_version. This was causing issues in newer releases of OpenStack
where the value of api_version was reporting as something other than
"3", and the generated Ironic config tried to use the v2.0 Keystone API.
This patch removes the optional logic in the template for v2.0 and rely
on the global default just like templates/parts/section-placement does.
Closes-Bug: #1995778
Change-Id: I8e0270b933f9c8fb5d6a65f9ebb930a0b21fead8
(cherry picked from commit 8d560b3ff55257370be0b9bc9b5dea73ee82d0ca)
Reviewed: https:/ /review. opendev. org/c/openstack /charm- nova-compute/ +/895792 /opendev. org/openstack/ charm-nova- compute/ commit/ 81ee072e71de61e b17329856d72628 11ec60fd66
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit 81ee072e71de61e b17329856d72628 11ec60fd66
Author: Jadon Naas <email address hidden>
Date: Thu Jun 22 12:40:04 2023 -0400
Drop the path from the auth_url.
The template previously could use v2.0 depending on the value of
api_version. This was causing issues in newer releases of OpenStack
where the value of api_version was reporting as something other than
"3", and the generated Ironic config tried to use the v2.0 Keystone API.
This patch removes the optional logic in the template for v2.0 and rely parts/section- placement does.
on the global default just like templates/
Closes-Bug: #1995778 fb5d6a65f9ebb93 0a0b21fead8 70be0b9bc9b5dea 73ee82d0ca)
Change-Id: I8e0270b933f9c8
(cherry picked from commit 8d560b3ff552573