Bug 1572603 - cinder-volume trouble after upgrade from ocata to pike
Summary: cinder-volume trouble after upgrade from ocata to pike
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-tripleo-heat-templates
Version: Pike
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: trunk
Assignee: Tomas Sedovic
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-27 11:57 UTC by girardin
Modified: 2020-05-08 17:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-08 17:53:24 UTC


Attachments (Terms of Use)

Description girardin 2018-04-27 11:57:10 UTC
Description of problem:
After upgrade from ocata to pike (dockerized) with HA controllers, we noticed cinder was no longer functional. Operations like creating new volumes from old volumes, or deleting old volumes was stuck in Deleting and creating status. 

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-7.0.12-0.20180402201322.e8b34d6.el7.centos.noarch

How reproducible:
Replace puppet-pacemaker.yaml env file by docker-ha.yaml envfile for upgrading you overcloud with HA controllers from Ocata to Pike. 


Steps to Reproduce:
Using an overcloud deploy command with the following environment files:
overcloud deploy --templates --libvirt-type kvm  --timeout 90 \
-e /home/stack/templates/node-info.yaml \
-e /home/stack/templates/network-environment-bonding.yaml \
-e /home/stack/templates/storage-environnement.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/docker.yaml \
-e /home/stack/templates/docker_registry.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-composable-steps-docker.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/ironic.yaml \
-e /home/stack/templates/ironic_env.yaml

Actual results:
Only cinder services are not containerized after the upgrade and cinder operations are stuck while deleting or cloning old volumes (existing volumes before the upgrade)


Expected results:
cinder was containerized and work as expected


Additional info:
After analyze, we found 2 things:
 - the 'host' parameter in cinder.conf is unconfigured 
 - the cinder-volume is still managed by pacemaker but active on all controllers  instead of active on one of them and passive on the others.

this trouble seems to be related with the difference between docker-ha.yaml and puppet-pacemaker.yaml. 

$ grep cinder-volume /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
  OS::TripleO::Services::CinderVolume: ../puppet/services/pacemaker/cinder-volume.yaml
$ grep cinder-volume /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml
  # OS::TripleO::Services::CinderVolume: ../docker/services/pacemaker/cinder-volume.yaml

the cinder-volume services configuration is commented in docker-ha.yaml.
With Ocata we used puppet-pacemaker.yaml env file but with Pike upgrade the tripleO documentation says:
"If the Overcloud has been deployed with Pacemaker, then add the docker-ha.yaml environment file to the upgrade command".

Comment 1 Luke Short 2020-05-08 17:53:24 UTC
Ocata and Pike are end-of-life releases now. Please re-open this BZ if it is affecting new upgrades.


Note You need to log in before you can comment on or make changes to this bug.