os_magnum role doesn't specify region_name for keystone

Bug #1819380 reported by Magnus Bergman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Magnus Bergman

Bug Description

It's not possible to set keystone region_name in appropriate section of magnum.conf.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/642300

Changed in openstack-ansible:
assignee: nobody → Magnus Bergman (magnusbe)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_magnum (master)

Reviewed: https://review.openstack.org/642300
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_magnum/commit/?id=3c4952376d923c15082c4bccd94bf5654a4e8a80
Submitter: Zuul
Branch: master

commit 3c4952376d923c15082c4bccd94bf5654a4e8a80
Author: mb <email address hidden>
Date: Sun Mar 10 23:36:10 2019 +0100

    Add ability to set keystone region_name in magnum.conf

    Adding the ability to set region_name in keystone_authtoken section of
    magnum.conf in the same wqy as for other services. Defaulting to
    magnum_service_region.

    Change-Id: I7f7e184c5eec6489505a6492ed2786a27bae29ab
    Closes-Bug: #1819380

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum stein-eol

This issue was fixed in the openstack/openstack-ansible-os_magnum stein-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum train-eol

This issue was fixed in the openstack/openstack-ansible-os_magnum train-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum ussuri-eol

This issue was fixed in the openstack/openstack-ansible-os_magnum ussuri-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum yoga-eom

This issue was fixed in the openstack/openstack-ansible-os_magnum yoga-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum victoria-eom

This issue was fixed in the openstack/openstack-ansible-os_magnum victoria-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum wallaby-eom

This issue was fixed in the openstack/openstack-ansible-os_magnum wallaby-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum xena-eom

This issue was fixed in the openstack/openstack-ansible-os_magnum xena-eom release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_magnum zed-eom

This issue was fixed in the openstack/openstack-ansible-os_magnum zed-eom release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.