From ac9c74bda942128ae5c307b78dfee6d01ce20432 Mon Sep 17 00:00:00 2001 From: Mark Goddard Date: Fri, 29 May 2020 17:28:57 +0100 Subject: [PATCH] Set previous release to Ussuri Now that the stable/ussuri branch has been cut, we can set the previous release to Ussuri. This is done in kolla-ansible for rolling upgrades, and in CI configuration for upgrade tests. Change-Id: I36f252c77339a6b810413810efd6bb32e0b69e29 --- ansible/group_vars/all.yml | 2 +- zuul.d/base.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ansible/group_vars/all.yml b/ansible/group_vars/all.yml index 8ec048c2df..d8717b52dd 100644 --- a/ansible/group_vars/all.yml +++ b/ansible/group_vars/all.yml @@ -502,7 +502,7 @@ openstack_logging_debug: "False" openstack_region_name: "RegionOne" # Variable defined the pin_release_version, apply for rolling upgrade process -openstack_previous_release_name: "train" +openstack_previous_release_name: "ussuri" # A list of policy file formats that are supported by Oslo.policy supported_policy_format_list: diff --git a/zuul.d/base.yaml b/zuul.d/base.yaml index f27ed9d636..6ac0cc215d 100644 --- a/zuul.d/base.yaml +++ b/zuul.d/base.yaml @@ -26,7 +26,7 @@ - ^kolla_ansible/tests/ - ^zuul\.d/ vars: - previous_release: train + previous_release: ussuri scenario: core is_upgrade: no api_network_prefix: "192.0.2."