Cinder-volume service isn't started after reboot on Ubuntu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Aleksandr Didenko | ||
5.1.x |
Fix Committed
|
High
|
Aleksandr Didenko | ||
6.0.x |
Fix Committed
|
High
|
Aleksandr Didenko | ||
6.1.x |
Fix Released
|
High
|
Aleksandr Didenko |
Bug Description
After restart of all nodes in cluster cinder-volume services on compute/storage nodes do not start automatically, because of special override file:
root@node-1:~# cat /etc/init/
manual
Steps to reproduce:
1. Create new cluster: Ubuntu, HA, NeutronGre
2. Add 1 controller and 2 compute+cinder nodes
3. Deploy changes. Everything works fine after deployment, cluster passes health checks.
4. Shutdown all nodes in cluster (/sbin/shutdown -Ph now)
5. Start all nodes simultaneously.
Expected result:
- all nodes are booted correctly, cluster passes health checks
Actual:
- cinder-volume services are down
Here is an output of cinder service-list command on controller:
+------
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------
| cinder-scheduler | node-2 | nova | enabled | up | 2015-02-
| cinder-volume | node-1 | nova | enabled | down | 2015-02-
| cinder-volume | node-3 | nova | enabled | down | 2015-02-
+------
On compute/cinder cinder-volume services nodes are down after restart:
root@node-1:~# /etc/init.
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service cinder-volume status
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status cinder-volume
cinder-volume stop/waiting
After 'cinder-volume' services restart they begin to work fine. If remove '/etc/init/
http://
I guess cinder-
Diagnostic snapshot is attached. Fuel version info: http://
summary: |
- Cinder-volume service goes down if it couldn't connect to MySQL server + Cinder-volume service isn't started after reboot on Ubuntu |
description: | updated |
The solution is to add post-deployment task to purge all override files Fuel created during the deployment