Change in globals.yml is not passed to environment

Bug #1853776 reported by Viktor Michalek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Medium
Radosław Piliszek

Bug Description

The change of variable value neutron_legacy_iptables in globals.yml is not passed to corresponding environment variable KOLLA_LEGACY_IPTABLES during reconfigure run, i.e.

When deployed with globals.yml setting:
neutron_legacy_iptables: "no"
There remains value FALSE in variable KOLLA_LEGACY_IPTABLES despite the change of neutron_legacy_iptables to "yes" and then then finished `kolla-ansible reconfigure`.

Revision history for this message
Mark Goddard (mgoddard) wrote :
Changed in kolla-ansible:
importance: Undecided → Medium
Revision history for this message
Radosław Piliszek (yoctozepto) wrote :
Changed in kolla-ansible:
status: New → Triaged
Changed in kolla-ansible:
status: Triaged → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.opendev.org/746965

Changed in kolla-ansible:
assignee: nobody → Michal Arbet (michalarbet)
status: Confirmed → In Progress
Changed in kolla-ansible:
assignee: Michal Arbet (michalarbet) → Radosław Piliszek (yoctozepto)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

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

commit ed2a2704d13fa70a8dc783960d05f5469639425c
Author: Michal Arbet <email address hidden>
Date: Wed Aug 19 17:23:18 2020 +0200

    Fix kolla-ansible not reflect environment changed

    Neutron's containers should use ENV from kolla_docker module's
    environment parameter (defined in roles/neutron/defaults/main.yml)
    after reconfigure, not only when deploying.

    Currently this is working only for deploy, not for reconfigure.

    How to test it ?
    - Deploy neutron with "neutron_legacy_iptables" set to yes/no.
    - Change value of "neutron_legacy_iptables" to opposite value as before.
    - Reconfigure neutron.

    Current result :
     - "KOLLA_LEGACY_IPTABLES" in container's ENV is not changed

    Expected result :
     - "KOLLA_LEGACY_IPTABLES:" in container's ENV should be changed

    This patch is fixing this behaviour by adding missing
    environment parameter to neutron's "Check neutron containers" task.

    Change-Id: Ibfbe2d4f49261fa766acbb6ff45da9994118bda8
    Closes-Bug: #1853776

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/ussuri)

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/747461

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/747462

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

Reviewed: https://review.opendev.org/747461
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=75f8ce358c648248941c1fbabc155e887f637e1a
Submitter: Zuul
Branch: stable/ussuri

commit 75f8ce358c648248941c1fbabc155e887f637e1a
Author: Michal Arbet <email address hidden>
Date: Wed Aug 19 17:23:18 2020 +0200

    Fix kolla-ansible not reflect environment changed

    Neutron's containers should use ENV from kolla_docker module's
    environment parameter (defined in roles/neutron/defaults/main.yml)
    after reconfigure, not only when deploying.

    Currently this is working only for deploy, not for reconfigure.

    How to test it ?
    - Deploy neutron with "neutron_legacy_iptables" set to yes/no.
    - Change value of "neutron_legacy_iptables" to opposite value as before.
    - Reconfigure neutron.

    Current result :
     - "KOLLA_LEGACY_IPTABLES" in container's ENV is not changed

    Expected result :
     - "KOLLA_LEGACY_IPTABLES:" in container's ENV should be changed

    This patch is fixing this behaviour by adding missing
    environment parameter to neutron's "Check neutron containers" task.

    Change-Id: Ibfbe2d4f49261fa766acbb6ff45da9994118bda8
    Closes-Bug: #1853776
    (cherry picked from commit ed2a2704d13fa70a8dc783960d05f5469639425c)

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

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

commit 06c6e14e5e66f09615631ddf56e47101a6819ca8
Author: Michal Arbet <email address hidden>
Date: Wed Aug 19 17:23:18 2020 +0200

    Fix kolla-ansible not reflect environment changed

    Neutron's containers should use ENV from kolla_docker module's
    environment parameter (defined in roles/neutron/defaults/main.yml)
    after reconfigure, not only when deploying.

    Currently this is working only for deploy, not for reconfigure.

    How to test it ?
    - Deploy neutron with "neutron_legacy_iptables" set to yes/no.
    - Change value of "neutron_legacy_iptables" to opposite value as before.
    - Reconfigure neutron.

    Current result :
     - "KOLLA_LEGACY_IPTABLES" in container's ENV is not changed

    Expected result :
     - "KOLLA_LEGACY_IPTABLES:" in container's ENV should be changed

    This patch is fixing this behaviour by adding missing
    environment parameter to neutron's "Check neutron containers" task.

    Change-Id: Ibfbe2d4f49261fa766acbb6ff45da9994118bda8
    Closes-Bug: #1853776
    (cherry picked from commit ed2a2704d13fa70a8dc783960d05f5469639425c)

tags: added: in-stable-train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 10.2.0

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

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

This issue was fixed in the openstack/kolla-ansible 9.3.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.