Cleaning and recreating network resources leads to conflicting o-hm0 interface

After using configure-resources to create the lb-mgmt network resources with ipv6, I wanted to change the network to ipv4 so I deleted the security groups, the subnet, network, and router and ran a script to manually create the ipv4 resources. The script is irrelevant as I was able to recreate the scenario by re-running the configure-resources action.

I believe the relevant action is that in order to delete the lbm-mgmt-net, I had to delete the health manager ports (such as octavia-health-manager-octavia-0-listen-port). It seems this left the o-hm0 interfaces in ovs on the octavia units. I don't see a better way to delete these ports.

After re-creating the lb-mgmt network resources I saw that the o-hm0 interface had a different mac-address in the output of these two commands on the octavia units:

  sudo ovs-vsctl list interface o-hm0
  ip link show o-hm0

And I resolved this by running (on the octavia units):

  sudo ovs-vsctl del-port o-hm0

And then running a charm hook with juju:

  juju run -a octavia hooks/config-changed

It seems like the charm should query neutron to see if the port exists, and if not, delete the o-hm0 interface from ovs prior to creating the port in neutron.