python-tripleoclient "overcloud_delete.py" doesn't link to the inventory

Bug #1950155 reported by Cédric Jeanneret
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Cédric Jeanneret

Bug Description

The inventory passed to utils.run_ansible_playbook in v2/overcloud_delete.py is wrong: it doesn't use the "parsed_args.stack" parameter and, therefore, only the string template is provided:

/home/stack/config-download/{}/tripleo-ansible-inventory.yaml

when it should pass:

/home/stack/config-download/overcloud/tripleo-ansible-inventory.yaml

It wasn't detected before because we don't have TLS-e with freeIPA deploy in CI, and the cli-overcloud-delete.yaml playbook doesn't use the OC inventory data at all - running only locally in the UC.

summary: - python-tripleoclient "overcloud_deploy" doesn't link to the inventory
+ python-tripleoclient "overcloud_delete.py" doesn't link to the inventory
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (master)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
Cédric Jeanneret (cjeanner) wrote (last edit ):
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (master)

Reviewed: https://review.opendev.org/c/openstack/python-tripleoclient/+/816998
Committed: https://opendev.org/openstack/python-tripleoclient/commit/9fd913f57cd5584c65c069af90037d72aa9db7cf
Submitter: "Zuul (22348)"
Branch: master

commit 9fd913f57cd5584c65c069af90037d72aa9db7cf
Author: Cédric Jeanneret <email address hidden>
Date: Mon Nov 8 12:32:09 2021 +0100

    Ensure we're using the stackname for the inventory

    Until now, the inventory path used by the overcloud_delete.py was wrong,
    since it wasn't using the "stackname", leading to a wrong
    /home/stack/config-download/{}/tripleo-ansible-inventory.yaml path.

    While it's not a big issue with non-TLS-e deploy, it becomes an actual
    problem when we involve FreeIPA and TLS-e, since the deletion won't
    remove the nodes nor services from FreeIPA.

    Closes-Bug: #1950155

    Change-Id: I5941bf9948c5f17e7406d34c21b8de9bd174c063

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/python-tripleoclient/+/817101

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/python-tripleoclient/+/817101
Committed: https://opendev.org/openstack/python-tripleoclient/commit/914709dd74d4a0ea09dedc3aacc06a0488ef89e4
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 914709dd74d4a0ea09dedc3aacc06a0488ef89e4
Author: Cédric Jeanneret <email address hidden>
Date: Mon Nov 8 12:32:09 2021 +0100

    Ensure we're using the stackname for the inventory

    Until now, the inventory path used by the overcloud_delete.py was wrong,
    since it wasn't using the "stackname", leading to a wrong
    /home/stack/config-download/{}/tripleo-ansible-inventory.yaml path.

    While it's not a big issue with non-TLS-e deploy, it becomes an actual
    problem when we involve FreeIPA and TLS-e, since the deletion won't
    remove the nodes nor services from FreeIPA.

    Closes-Bug: #1950155

    Change-Id: I5941bf9948c5f17e7406d34c21b8de9bd174c063
    (cherry picked from commit 9fd913f57cd5584c65c069af90037d72aa9db7cf)

tags: added: in-stable-wallaby
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 18.0.0

This issue was fixed in the openstack/python-tripleoclient 18.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 16.5.0

This issue was fixed in the openstack/python-tripleoclient 16.5.0 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.