Bug 1388146

Summary: Order of steps for upgrading OSP8 -> OSP9
Product: Red Hat OpenStack Reporter: kamil.rogon
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED NOTABUG QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: low    
Version: 9.0 (Mitaka)CC: dmacpher, jdonohue, mburns, sathlang, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-24 09:37:48 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:
Bug Depends On:    
Bug Blocks: 1373538, 1400606    

Description kamil.rogon 2016-10-24 15:08:18 UTC 
Description of problem:

The documentation for upgrade between OSP8 and OSP9 specifies the below steps in such order:
1. major-upgrade-aodh.yaml
2. major-upgrade-keystone-liberty-mitaka.yaml
3. major-upgrade-pacemaker-init.yaml
4. upgrade-non-controller.yaml (object storage nodes)
5. major-upgrade-pacemaker.yaml
6. upgrade-non-controller.yaml (computes nodes)
7. upgrade-non-controller.yaml (ceph storage nodes)
8. major-upgrade-pacemaker-converge.yaml

The 2nd step is calling below puppet file: /usr/share/openstack-tripleo-heat-templates/extraconfig/tasks/liberty_to_mitaka_keystone_upgrade.pp

However when reading the headers it indicate the order of steps should be different.

# This puppet manifest is to be used only during a Liberty->Mitaka upgrade
# It configures keystone to be run under httpd but it makes sure to not
# restart any services. This snippet needs to be called after the
# major-upgrade-pacemaker-init.yaml step because that pushes new hiera data
# on the nodes and before the major-upgrade-pacemaker.yaml


I had some problems after step 2 with api available (especially for keystone) and I want to confirm which order is the right one.


Version-Release number of selected component (if applicable):
[stack@osp8-director ~]$ rpm -qa | grep -ie triple -ie heat -ie puppet
openstack-heat-templates-0-0.3.96a0b0bgit.el7ost.noarch
openstack-tripleo-heat-templates-kilo-0.8.14-16.el7ost.noarch
openstack-heat-engine-6.0.0-11.el7ost.noarch
openstack-tripleo-heat-templates-liberty-2.0.0-34.el7ost.noarch
openstack-heat-api-cfn-6.0.0-11.el7ost.noarch
openstack-puppet-modules-8.1.8-2.el7ost.noarch
openstack-tripleo-common-2.0.0-8.el7ost.noarch
openstack-heat-api-cloudwatch-6.0.0-11.el7ost.noarch
openstack-heat-common-6.0.0-11.el7ost.noarch
openstack-tripleo-heat-templates-2.0.0-34.el7ost.noarch
python-tripleoclient-2.0.0-3.el7ost.noarch
puppet-3.6.2-2.el7.noarch
openstack-tripleo-0.0.8-0.2.d81bd6dgit.el7ost.noarch
openstack-tripleo-image-elements-0.9.9-6.el7ost.noarch
python-heatclient-1.2.0-1.el7ost.noarch
openstack-heat-api-6.0.0-11.el7ost.noarch
python-heat-tests-6.0.0-11.el7ost.noarch
openstack-tripleo-puppet-elements-2.0.0-4.el7ost.noarch
Comment 3 Sofer Athlan-Guyot 2017-01-24 09:27:16 UTC 
Hi,

I went through the OSP8 upgrade following the documentation and it went well.  

The comment in the puppet is indeed confusing.  For reference here is the upstream documentation (that matches the order of the director's one):


  - http://docs.openstack.org/developer/tripleo-docs/post_deployment/upgrade.html
  - https://github.com/openstack/tripleo-heat-templates/blob/stable/mitaka/extraconfig/tasks/liberty_to_mitaka_keystone_upgrade.pp#L16-L20

Going to check with the developer if that comment still makes sense.
Comment 4 Sofer Athlan-Guyot 2017-01-24 09:37:48 UTC 
After a quick chat with Baldessari, I confirm that the comment is wrong and should be ignored.  The order in the documentation is fine.

Feel free to re-open if you think you original error was indeed related to the order (unlikely).

Regards,