kolla-ansible

deploy/reconfigure blazar failed due to the authentication error

Bug #1853462 reported by Zhuo Zhen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Medium
Zhuo Zhen
kolla-ansible 10.0.0 "ussuri"
Rocky
Fix Released
Medium
Mark Goddard
Stein
Fix Released
Medium
Mark Goddard
Train
Fix Released
Medium
Mark Goddard
Ussuri
Fix Released
Medium
Zhuo Zhen
kolla-ansible 10.0.0 "ussuri"

Bug Description

**Bug Report**

When deploy or reconfigure blazar using kolla-ansible, the process fails at "Creating blazar host aggregate" due to the authentication error. In "bootstrap.yml", the admin project name and username are hard-coded as "admin". OpenStack users can define their admin project name and username differently and the hard-coded names cause authentication errors.

To reproduce, simply run "kolla-ansible reconfigure --tags blazar" and make sure your admin project name and/or username is not "admin".

**Environment**

OS: centos7
Kernel: 3.10.0-862.11.6.el7.x86_64
Docker version: 18.09.2
Kolla-Ansible version: rocky

Tags: blazar
OpenStack Infra (hudson-openstack)
Changed in kolla-ansible:
assignee: nobody → Zhuo Zhen (zhenz)
status: New → In Progress
Mark Goddard (mgoddard)
Changed in kolla-ansible:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.opendev.org/695214
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=f2d32d2e0134030a3a9f40fb8ec769b1ae71e199
Submitter: Zuul
Branch: master

commit f2d32d2e0134030a3a9f40fb8ec769b1ae71e199
Author: Zhuo Zhen <email address hidden>
Date: Wed Nov 20 08:55:27 2019 -0600

    Fix hard-coded admin project name and username in blazar task

    In one of the blazar ansible tasks in "bootstrap.yml", the admin
    project name and username are hard-coded as "admin". OpenStack
    users can define their admin project name and username differently
    and the hard-coded names would cause authentication errors.

    In addition, keystone identity api version 3 uses "os-project-name"
    instead of "os-tenant-name". Although "os-tenant-name" might be
    still accepatable, it's better to keep the latest.

    Change-Id: Ie5c1016f9ce6f402ef208f3c295e6883a9edd8ab
    Closes-bug: #1853462

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/696344

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/696345

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/696346

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/stein)

Reviewed: https://review.opendev.org/696345
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=bcea46f13d24855e482f5b32ce7797033d67fa05
Submitter: Zuul
Branch: stable/stein

commit bcea46f13d24855e482f5b32ce7797033d67fa05
Author: Zhuo Zhen <email address hidden>
Date: Wed Nov 20 08:55:27 2019 -0600

    Fix hard-coded admin project name and username in blazar task

    In one of the blazar ansible tasks in "bootstrap.yml", the admin
    project name and username are hard-coded as "admin". OpenStack
    users can define their admin project name and username differently
    and the hard-coded names would cause authentication errors.

    In addition, keystone identity api version 3 uses "os-project-name"
    instead of "os-tenant-name". Although "os-tenant-name" might be
    still accepatable, it's better to keep the latest.

    Change-Id: Ie5c1016f9ce6f402ef208f3c295e6883a9edd8ab
    Closes-bug: #1853462
    (cherry picked from commit f2d32d2e0134030a3a9f40fb8ec769b1ae71e199)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/rocky)

Reviewed: https://review.opendev.org/696346
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ad0e7700f14af4d50a79d37bc815663ab36a4843
Submitter: Zuul
Branch: stable/rocky

commit ad0e7700f14af4d50a79d37bc815663ab36a4843
Author: Zhuo Zhen <email address hidden>
Date: Wed Nov 20 08:55:27 2019 -0600

    Fix hard-coded admin project name and username in blazar task

    In one of the blazar ansible tasks in "bootstrap.yml", the admin
    project name and username are hard-coded as "admin". OpenStack
    users can define their admin project name and username differently
    and the hard-coded names would cause authentication errors.

    In addition, keystone identity api version 3 uses "os-project-name"
    instead of "os-tenant-name". Although "os-tenant-name" might be
    still accepatable, it's better to keep the latest.

    Change-Id: Ie5c1016f9ce6f402ef208f3c295e6883a9edd8ab
    Closes-bug: #1853462
    (cherry picked from commit f2d32d2e0134030a3a9f40fb8ec769b1ae71e199)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/train)

Reviewed: https://review.opendev.org/696344
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=e6e3ffd555fd737477725efd985227bfcf5af332
Submitter: Zuul
Branch: stable/train

commit e6e3ffd555fd737477725efd985227bfcf5af332
Author: Zhuo Zhen <email address hidden>
Date: Wed Nov 20 08:55:27 2019 -0600

    Fix hard-coded admin project name and username in blazar task

    In one of the blazar ansible tasks in "bootstrap.yml", the admin
    project name and username are hard-coded as "admin". OpenStack
    users can define their admin project name and username differently
    and the hard-coded names would cause authentication errors.

    In addition, keystone identity api version 3 uses "os-project-name"
    instead of "os-tenant-name". Although "os-tenant-name" might be
    still accepatable, it's better to keep the latest.

    Change-Id: Ie5c1016f9ce6f402ef208f3c295e6883a9edd8ab
    Closes-bug: #1853462
    (cherry picked from commit f2d32d2e0134030a3a9f40fb8ec769b1ae71e199)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 9.0.0.0rc2

This issue was fixed in the openstack/kolla-ansible 9.0.0.0rc2 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 7.2.0

This issue was fixed in the openstack/kolla-ansible 7.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 8.1.0

This issue was fixed in the openstack/kolla-ansible 8.1.0 release.

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

Other bug subscribers

Remote bug watches

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