cinder.conf changes doesn't clean up service list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
In a muti-backend cinder configuration , volume backend section name changes to cinder.conf file is not hanndled properly and causes volume creation errors.
For e.g: If the section name changes and c-vol service is restarted, the 'State' of the service is down , but the 'Status' is enabled. You have to manually disable the service using service-disable command for it to be invalid(or delete from database using brute force).
Before:
enabled_
[eqlx1]
volume_
...
volume_
After:
enabled_
[eqlx2]
volume_
...
volume_
stack@au-
+------
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------
| cinder-scheduler | au-ubuntu-
| cinder-volume | au-ubuntu-
| cinder-volume | au-ubuntu-
| cinder-volume | au-ubuntu-
+------
description: | updated |
description: | updated |
description: | updated |
Changed in cinder: | |
importance: | Undecided → Wishlist |
assignee: | nobody → harsh mishra (harsh-mishra) |
status: | New → In Progress |
The name you're setting in the config file is used to identify the service host (or our version of a fake-service host at any rate). This is expected behavior that you can't go in and *change* the host name on existing volumes.
In order to do this sort of thing you need to use the cinder-manage update_host command 7512b88ecb0cbaf 6aedc06ea7)
(Change: 2f7c40421627b26