updating overcloud after undercloud upgrade: Unable to create plan. A container with the name overcloud already exists.

[Jiří Stránský]

The containers upgrade job started hitting this issue which fails the upgrade:

2017-04-20 18:34:51 | Unable to create plan. A container with the name overcloud already exists.

The last point when the overcloud was able to start upgrading was April 19th, on April 20th all job runs fail with the above error. Given this info a related commit seems to be this one https://review.openstack.org/#/c/456889

[OpenStack Infra (hudson-openstack)]

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

[Jiří Stránský (jistr)]

Here's a CI job from 19th April that started executing the overcloud upgrade:

http://logs.openstack.org/84/450784/15/experimental/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/823dfd7/logs/undercloud/home/jenkins/overcloud_upgrade_console.log.txt.gz#_2017-04-19_10_25_48

Here's a CI job from 20th April that's failing:

http://logs.openstack.org/84/450784/17/experimental/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/4c05d45/logs/undercloud/home/jenkins/overcloud_upgrade_console.log.txt.gz#_2017-04-20_18_34_51

[Jiří Stránský (jistr)]

Disabling undercloud upgrade in the containers job did help the job get further, so the bug is indeed somewhere in the undercloud upgrade procedure:

http://logs.openstack.org/84/450784/18/experimental/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/ea4b0ed/logs/undercloud/home/jenkins/overcloud_upgrade_console.log.txt.gz#_2017-04-21_11_04_33

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Jiri Stransky (<email address hidden>) on branch: master
Review: https://review.openstack.org/458792
Reason: Fix at Icac6efe17fffc78bf74a34206cced82e2b968fcf

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/458859
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=f530e1450536ea61aeb47daa53f8528d948f6752
Submitter: Jenkins
Branch: master

commit f530e1450536ea61aeb47daa53f8528d948f6752
Author: Julie Pichon <email address hidden>
Date: Fri Apr 21 15:22:27 2017 +0100

    Plan format migration: keep the Mistral env around

    Until the tripleo-common change at [1] is merged, operations related to
    Plans still expect a Mistral environment to exist. Deleting it now is
    causing updates and re-deployments to fail after upgrading the
    undercloud (which also migrates the Plan to use the new format).

    Let's keep the Mistral environment around until the tripleo-common
    changes are in and fix the TODO then.

    [1] https://review.openstack.org/#/c/452291/6

    Related blueprint: stop-using-mistral-env
    Closes-Bug: #1685171

    Change-Id: Icac6efe17fffc78bf74a34206cced82e2b968fcf

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/instack-undercloud 7.1.0 release.