charm should validate it can reach memcache
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
The 19.04 nova-cloud-
https:/
https:/
And even when you find them, I had to page down 11 times before I got to any mention of n-c-c and memcache.
Please make the charm check connectivity to memcache and do something useful (e.g. warn the user in juju status and/or set status to blocked).
Changed in charm-nova-cloud-controller: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: | added: canonical-bootstack |
tags: | added: sts |
This "known issue" degraded a charm-upgraded Cloud considerably. Because of haproxy-*-timeout, "openstack service list" (and the same via Horizon) aborted the connection before finishing. And there was a point where no logs identified this as an issue.
In retrospective, greping for "memcache" only shows the values after a nova-api-os-compute restart (in debug mode).
I may agree that the nova-cloud- controller message in "juju status" could highlight this connectivity issue, but I also think Nova logs should describe (at least in debug mode) that the connections to the configured memcached servers are getting refused (we may not know per the logs that it is caused by the juju bindings, but at least the problem won't be hidden).