Red Hat Bugzilla – Bug 1469519
OpenStack Manilla Services not set to enabled in systemd for reboot
Last modified: 2017-07-26 11:09:05 EDT
Description of problem:
After clean OSP11 install with tripleo and manilla backend enabled, some manila services are not enabled in systemd for reboot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# systemctl list-unit-files '*openstack*' | grep manila
openstack-manila-data.service and openstack-manila-share.service not enabled
openstack-manila-data.service and openstack-manila-share.service enabled by default by heat template
I wouldn't necessarily expect the data service to be enabled as it is an experimental and unsupported service.
share service is a different matter but it runs under pacemaker control rather than under control of systemd so I don't think we want systemctl to report that it's enabled.
If you run 'pcs status' to see which controller the share service runs on, login to that controller, and run 'sudo systemctl status openstack-manila-share' you'll see that the service is loaded and active but "disabled", like so:
$ sudo systemctl status openstack-manila-share
● openstack-manila-share.service - Cluster Controlled openstack-manila-share
Loaded: loaded (/usr/lib/systemd/system/openstack-manila-share.service; disabled; vendor preset: disabled)
Active: active (running) since Sat 2017-07-01 09:17:55 UTC; 3 weeks 4 days ago
Same deal for cinder volume (note that it may be running on a different controller):
$ systemctl status openstack-cinder-volume
● openstack-cinder-volume.service - Cluster Controlled openstack-cinder-volume
Loaded: loaded (/usr/lib/systemd/system/openstack-cinder-volume.service; disabled; vendor preset: disabled)
Active: active (running) since Sat 2017-07-01 09:17:15 UTC; 3 weeks 4 days ago
Closing this one as NOTABUG. Please re-open if I'm missing someting.