charm-layer-ovn

  1. Bug #1896630
  2. Comment #27

Comment 27 for bug 1896630

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-nova-compute (master)

Reviewed: https://review.opendev.org/c/openstack/charm-nova-compute/+/873944
Committed: https://opendev.org/openstack/charm-nova-compute/commit/2bad8a0522622e9da621a28912faa42efa27d033
Submitter: "Zuul (22348)"
Branch: master

commit 2bad8a0522622e9da621a28912faa42efa27d033
Author: Felipe Reyes <email address hidden>
Date: Wed Feb 15 11:43:40 2023 -0300

    Use a stable hostname to render nova.conf

    OVS introduced a new service called ovs-record-hostname.service which
    records the hostname on the first start in the ovs database to identify
    the ovn chassis, this is how it achieved a stable hostname and be
    resilient to the changes in the FQDN when the DNS gets available.

    This change introduces the same approach for nova-compute charm. In the
    first run of the NovaComputeHostInfoContext the value passed in the
    context as host_fqdn is stored in the unit's kv db, and re-used on every
    subsequent call.

    This change affects only new installs since the hint to store (or not)
    the host fqdn is set in the install hook.

    Change-Id: I2aa74442ec25b21201a47070077df27899465814
    Closes-Bug: #1896630