Unnecessary Keystone dependency in resource agents
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-resource-agents |
In Progress
|
Low
|
Norbert Illes |
Bug Description
The monitoring function of some resource agents are depending on the availability of Keystone: they try to get a token from Keystone and they are using this token during monitoring.
If Keystone gets unavailable, these Keystone-dependent resource agents mark these -otherwise running- resources unavailable, simply because they can't get a token from Keystone, causing unnecessary resource restart/migration.
Although, we shouldn't consider the resources fully available if Keystone is not there (e.g. if neutron-server is running but Keystone isn't, the user can not use Neutron properly), this dependency should not be hard-coded in the resource agents.
The impacted resource agents:
* neutron-server
* glance-registry
* manila-api
* cinder-api
* nova-api
Norbert filed https:/ /review. openstack. org/#/c/ 275108/ to fix this but unfortunately IIUC it seems it referenced the wrong bug number. @Norbert, can we mark this as resolved now, or is there a reason your commit message said only "Partial-Bug" ?