Comment 24 for bug 1896630

I'm adding a task for the nova-compute charm, because it gets affected by this same behavior, for example this is how the list of hypervisor looks when a machine changed the fqdn to include the domain.

| 12 | nova-compute | juju-6f998c-zaza-546dd56956f7-26 | nova | enabled | down | 2022-07-26T16:26:26.000000 |
| 13 | nova-compute | juju-6f998c-zaza-546dd56956f7-26.project.serverstack | nova | enabled | up | 2022-07-27T15:22:02.000000 |

This produced a mismatch between ovn and nova-compute, ovn due to the ovs-record-hostname.service sticked to the first hostname configured:

| juju-6f998c-zaza-546dd56956f7-26 | OVN Controller agent | juju-6f998c-zaza-546dd56956f7-26 | | :-) | UP | ovn-controller |
| 02d23ece-b1d2-57fd-a69c-198dacdc0561 | OVN Metadata agent | juju-6f998c-zaza-546dd56956f7-26 | | :-) | UP | neutron-ovn-metadata-agent |

With this no new instances could be launched on the hypervisor since the port binding was failing since there was no chassis for "juju-6f998c-zaza-546dd56956f7-26.project.serverstack"