[Train] HA: rabbitmq_init_bundle not restart on stack update as expected

Bug #1855732 reported by Damien Ciabrini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Damien Ciabrini

Bug Description

Starting in Train, a rabbitmq HA service refactoring [1] and a later unsuccessful fix [2] left the service unable to restart container "rabbitmq_init_bundle" on every stack update or minor update.

We used to originally create rabbitmq_init_bundle with an environment variable TRIPLEO_DEPLOY_IDENTIFIER whose value always changes during deploy/update, so paunch would always restart this container.

This variable is now gone, so we lost the expected behaviour.

[1] I894f339cdf03bc2a93c588f826f738b0b851a3ad
[2] I139c2c276c8f532d37fceafe06f9547048e76906

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.opendev.org/698041
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=82408e4b8add9da281e7cc51b3743ecd1d9efe43
Submitter: Zuul
Branch: master

commit 82408e4b8add9da281e7cc51b3743ecd1d9efe43
Author: Damien Ciabrini <email address hidden>
Date: Mon Dec 9 17:24:14 2019 +0100

    Ensure rabbitmq deployment container is restarted at every update

    In [1] we lost the ability to restart deployment containers such as
    rabbitmq_bootstrap and rabbitmq_init_bundle every time a stack update
    or minor update is run. A fix for it [2] was attempted but was only
    partial so not working.

    Make sure we reintroduce variable TRIPLEO_DEPLOY_IDENTIFIER in all
    the rabbitmq deployment containers (HA and non-HA) to make sure they
    get restarted as expected at every update.

    [1] I894f339cdf03bc2a93c588f826f738b0b851a3ad
    [2] I139c2c276c8f532d37fceafe06f9547048e76906

    Change-Id: I131a905b62cd990deee1ae6aa81ab2560c98a7c8
    Closes-Bug: #1855732

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

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

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

Reviewed: https://review.opendev.org/698451
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=3a02caa86b45c70f2c171683dd19358c59d09c4b
Submitter: Zuul
Branch: stable/train

commit 3a02caa86b45c70f2c171683dd19358c59d09c4b
Author: Damien Ciabrini <email address hidden>
Date: Mon Dec 9 17:24:14 2019 +0100

    Ensure rabbitmq deployment container is restarted at every update

    In [1] we lost the ability to restart deployment containers such as
    rabbitmq_bootstrap and rabbitmq_init_bundle every time a stack update
    or minor update is run. A fix for it [2] was attempted but was only
    partial so not working.

    Make sure we reintroduce variable TRIPLEO_DEPLOY_IDENTIFIER in all
    the rabbitmq deployment containers (HA and non-HA) to make sure they
    get restarted as expected at every update.

    [1] I894f339cdf03bc2a93c588f826f738b0b851a3ad
    [2] I139c2c276c8f532d37fceafe06f9547048e76906

    Change-Id: I131a905b62cd990deee1ae6aa81ab2560c98a7c8
    Closes-Bug: #1855732
    (cherry picked from commit 82408e4b8add9da281e7cc51b3743ecd1d9efe43)

tags: added: in-stable-train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 11.3.1

This issue was fixed in the openstack/tripleo-heat-templates 11.3.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 12.1.0

This issue was fixed in the openstack/tripleo-heat-templates 12.1.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.