charm-ovn-chassis

enable-auto-restarts shouldn't prevent install hooks from running during first deploy

Bug #1964994 reported by Garrett Neugent
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-ovn-chassis
New
Undecided
Unassigned

Bug Description

Hello,

After deploying nova-compute to a new machine (with ovn-chassis as a subordinate), i see the following status:

ovn-chassis/23 active executing <IP> Hooks skipped due to disabled auto restarts: install

I think a better user experience would be to configure enable-auto-restarts to permit the initial setup of a new machine. This was found on version cs:ovn-chassis-21, with focal/victoria.

Thanks!

Tags: bseng-121
Revision history for this message
Paul Goins (vultaire) wrote :

I just hit this while debugging some redeployed computes on a cloud being prepared for handover. I had to spend hours of time to dig in to figure out that the reason the neutron-sriov-agent package wasn't being installed (in response to a nova-compute-relation-joined hook triggering the enable_openstack handler) was because of enable-auto-restarts being set to false. And it does basically break automation of redeploys; to get redeploys to work cleanly without the charm going into an error state, we need to set enable-auto-restarts to true prior to doing so, and remember to set enable-auto-restarts back to false afterwards.

Alvaro Uria (aluria)
tags: added: bseng-121
Revision history for this message
Giuseppe Petralia (peppepetra) wrote :

This is a duplicate of LP#1943970

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.