Ocata -> Pike overcloud upgrade: openstack-cinder-volume is still running under systemd after upgrade:
[root@overcloud-controller-0 heat-admin]# systemctl list-units | grep openstack | grep active
openstack-cinder-volume.service loaded active running OpenStack Cinder Volume Server
openstack-heat-api-cfn.service loaded active running Openstack Heat CFN-compatible API Service
openstack-heat-api.service loaded active running OpenStack Heat API Service
openstack-swift-object-expirer.service loaded active running OpenStack Object Storage (swift) - Object Expirer
openstack-cinder-volume doesn't have a corresponding container:
[root@overcloud-controller-0 heat-admin]# docker ps | grep cinder
265fbfbcc3d1 192.168.0.1:8787/tripleoupstream/centos-binary-cinder-scheduler:latest "kolla_start" 12 hours ago Up 12 hours cinder_scheduler
1161915e4287 192.168.0.1:8787/tripleoupstream/centos-binary-cinder-api:latest "kolla_start" 12 hours ago Up 12 hours cinder_api
I expected to see openstack-cinder-volume running inside a docker container
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE