charm-layer-ovn

  1. Bug #1896630
  2. Comment #14

Comment 14 for bug 1896630

Revision history for this message
Jeff Hillman (jhillman) wrote : Re: ovn-chassis subordinate to octavia registered with shortname shows down

I'm seeing something similar, but not identical. not sure if it is caused by the same issue or if a new bug needs to be created.

In my scenario, on a new deploy, when I run 'openstack network agent list | grep lxd', they all show the proper longs names.

Also, running 'juju run -a octavia 'ovs-vsctl get . external_ids:hostname'' also all show the proper short names.

However, running 'openstack port list | grep octavia', shows one as being DOWN.

Performing a port show on the health manager has it as binding_failed AND also shows the shortname.

Performing Frode's steps in comment #3 above, fixes the shortname, and the binding, however, the status is still DOWN, and I cannot ping any of the amphora images, or the other octavia ports from this bad octavia container.

Going into the container and running 'ip link show' has the link at UNKNOWN. Running 'ip link set down dev o-hm0; ip link set up dev o-hm0' puts the port back into an UNKNOWN state, but pings work. And Octavia can now create loadbalancer on demand.

I'm gathering a juju crash-dump at this moment.