From d4f719e95a76760f9c6db0e085fc3bb2ca2ca2eb Mon Sep 17 00:00:00 2001
From: Mark Goddard <mark@stackhpc.com>
Date: Thu, 14 Nov 2019 11:34:09 +0000
Subject: [PATCH] Set previous release to Train
Now that the stable/train branch has been cut, we can set the previous
release to Train. This is done in kolla-ansible for rolling upgrades,
and in CI configuration for upgrade tests.
Change-Id: I9d903543936e59aeeee939b32afce3e63b8c4394
---
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 cf3e4ca52b..94f9a2ff2a 100644
--- a/ansible/group_vars/all.yml
+++ b/ansible/group_vars/all.yml
@@ -499,7 +499,7 @@ openstack_logging_debug: "False"
openstack_region_name: "RegionOne"
# Variable defined the pin_release_version, apply for rolling upgrade process
-openstack_previous_release_name: "stein"
+openstack_previous_release_name: "train"
# 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 932876233e..a056070948 100644
--- a/zuul.d/base.yaml
+++ b/zuul.d/base.yaml
@@ -31,7 +31,7 @@
name: kolla-ansible-upgrade-base
parent: kolla-ansible-base
vars:
- previous_release: stein
+ previous_release: train
scenario: upgrade
- job: