From 58bcdf1a4ae9836b354ee1c0be6e5f27bc8e1b4f Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Thu, 7 Aug 2025 08:26:24 -0700 Subject: [PATCH] ci: grenade: restart neutron services Recently networking-baremetal got a patch to leverage a relatively new rpc call against neutron called report_state. However... in late 2024 neutron's RPC executions were split from the API, and grenade never learned to restart the new service.. and that may also be intentional. Until there is clarity on that front, the path is clear... to restart the service. This should clear up the overall grenade job execution failure. Closes-Bug: 2118780 Related-Bug: 2117227 Change-Id: I9f942df892783a85387e6feb3a8bdb5396103e15 Signed-off-by: Julia Kreger --- devstack/upgrade/upgrade.sh | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/devstack/upgrade/upgrade.sh b/devstack/upgrade/upgrade.sh index 9cf7e402d1..b543da5c7b 100755 --- a/devstack/upgrade/upgrade.sh +++ b/devstack/upgrade/upgrade.sh @@ -66,6 +66,19 @@ if [[ -d $IRONIC_CONF_DIR ]] && [[ ! -d $SAVE_DIR/etc.ironic ]] ; then cp -pr $IRONIC_CONF_DIR $SAVE_DIR/etc.ironic fi +# Ironic has an early consumer of a new neutron API, and grenade nor devstack +# has any concept of restarting neutron-rpc-server as it was added in late +# 2024. Ultimately networking-baremetal adding an rpc call which needs the +# updated service running means we need to restart it, for now. +sudo systemctl stop devstack@neutron-rpc-server.service || true +sudo systemctl stop devstack@q-l3.service || true +sudo systemctl stop devstack@q-agt.service || true +sleep 1 +sudo systemctl start devstack@neutron-rpc-server.service || true +sudo systemctl start devstack@q-l3.service || true +sudo systemctl start devstack@q-agt.service || true +sleep 1 + stack_install_service ironic # calls upgrade-ironic for specific release