Bug 1535475

Summary: OSP10 -> OSP13 FFU upgrade: upgrade_steps_playbook.yaml: pre upgrade validations are placed at the end of the controller upgrade playbook
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: openstack-tripleo-commonAssignee: Ryan Brady <rbrady>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: urgent Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: dbecker, jschluet, mandreou, mbracho, mbultel, mburns, morazi, rhel-osp-director-maint, sclewis, slinaber
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-8.4.1-0.20180224032817.d51ed49.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:42:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marius Cornea 2018-01-17 13:23:20 UTC 
Description of problem:
OSP10 -> OSP13 FFU upgrade: upgrade_steps_playbook.yaml: pre upgrade validations are placed at the end of the controller upgrade playbook.

I am not sure that in case of FFU we need those validations as the services shouldn't be running at this point. Attaching the controller upgrade playbook where you can see the validations are placed at the end of the playbook: http://paste.openstack.org/show/646509/
Comment 2 Marios Andreou 2018-01-24 13:19:06 UTC 
This has same root cause as BZ 1535442 and should also be fixed by https://review.openstack.org/#/c/529369/ which addresses the task ordering - marking triaged
Comment 12 errata-xmlrpc 2018-06-27 13:42:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2086