* Command:
juju verify reboot neutron-gateway/0
juju verify shutdown neutron-gateway/0
Expected behavior:
- “juju-verify” checks if there are running network instances on agents (L3, DHCP, OVS, LB, Metadata)
* openstack network agent list --host <hostname> (list of agents in a host)
* openstack router list --agent <l3-agent-id-from-prev-hostname> (list of routers and status [active, backup, down...])
* openstack network list --agent <dhcp-agent-id-from-prev-hostname>
* neutron lbaas-loadbalancer-list-on-agent <lb-agent-id-from-prev-hostname>
Neutron-gateway actions required (a bug may be required per action, as separated tasks):
- neutron-gateway: get-agents-ids
Returns a map of agent IDs and agent names running on the unit, as listed in "openstack network agent list" output.
- neutron-gateway: get-status-routers
Returns the list of routers running on the unit, and their status
- neutron-gateway: get-status-dhcp: same as the previous action, but regarding tenant networks DHCP services (in case of HA, we need to know if they're active or in backup mode)
- neutron-gateway: get-status-lb: same as the previous but re: Neutron LBs, which are now discouraged but just in case
I don't think there are other services that having them stopped would cause an outage. Please evaluate if I missed anything, just in case.
As per the original bug report, I've filed additional bug reports:
- LP#1917399 (list network agents)
- LP#1917401 (list routers)
- LP#1917403 (list DHCP services)
- LP#1917405 (list Neutron LBs)