Closed sudeephb closed 7 months ago
(by afreiberger) The real issue here is that nova-cert doesn't exist in Pike and later and the charms didn't cleanup. related bug: lp#1810449
I think this can be safely set to "Won't Fix" or "invalid" as the newer charms do properly remove the nova-cert service records upon Pike upgrade.
The errors about ServiceTooOld came from having old nova packages on the neutron-gateway nodes and were resolved with a full upgrade of the neutron-gateway service to Pike.
After an upgrade to Pike, nova-cert didn't upgrade and left nova-cert dead in the water with the nova-api-metadata service spewing errors like:
2019-01-03 22:37:21.803 1666745 ERROR oslo_service.service ServiceTooOld_Remote: This service is older (v15) than the minimum (v22) version of the rest of the deployment. Unable to continue.
Found by querying the nova database that nova-cert was version 15 on all units, but the rest of the services were version 22.
This resulted in nova-cert State "down" for all nova-cert services. This should be alerted on by nagios check for nova_services, but is not.
Imported from Launchpad using lp2gh.
date created: 2019-01-03T22:47:46Z
owner: afreiberger
assignee: None
the launchpad url