post upgrades validations fails if using a non default stack name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Carlos Camacho |
Bug Description
Description of problem:
-------
post-upgrade validation fails when overcloud is deployed with name different than 'overcloud'.
openstack stack list
+------
| ID | Stack Name | Project | Stack Status | Creation Time | Updated Time |
+------
| 96a4edee-
+------
From uc upgrade log:
-------
2018-05-16 02:09:37,460 INFO: Starting and waiting for validation groups ['post-upgrade']
2018-05-16 02:09:55,755 ERROR: ERROR error running the validation groups ['post-upgrade'] {"stderr": "[DEPRECATION WARNING]: DEFAULT_SUDO_FLAGS option, In favor of become which is a\n generic framework . This feature will be removed in version 2.8. Deprecation \nwarnings can be disabled by setting deprecation_
2018-05-16 02:09:55,758 INFO:
#######
Undercloud upgrade complete.
The file containing this installation's passwords is at
/home/stack/
There is also a stackrc file at /home/stack/
These files are needed to interact with the OpenStack services, and should be
secured.
#######
Version-Release number of selected component (if applicable):
-------
openstack-
Steps to Reproduce:
-------------------
1. Deploy tripleo with custom overcloud name
2. Setup tripleo repos on uc
3. Upgrade UC
Actual results:
---------------
Validation in post-upgrade group fails
Expected results:
-----------------
Validation in post-upgrade group succeeds
Additional info:
----------------
Virtual env: 3controller + 3messaging + 3database + 3ceph + 2compute + 2networker
Changed in tripleo: | |
status: | In Progress → Fix Released |
Fix proposed: https:/ /review. openstack. org/#/c/ 619112/