• Icon: Epic Epic
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • rhos-18.0.0
    • None
    • openstack-nova
    • None
    • Stable Compute UUIDs
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • Committed
    • To Do
    • openstack-nova-27.1.1-18.0.20230930093334.a869ab1.el9ost
    • Committed
    • Committed
    • 0% To Do, 25% In Progress, 75% Done
    • Hide
      .Compute service hostname change

      If you start the Compute service (nova) and your Compute host detects a name change, you must know the reason for the change of the host names. When you resolve the issue, you must restart the Compute service.
      Show
      .Compute service hostname change If you start the Compute service (nova) and your Compute host detects a name change, you must know the reason for the change of the host names. When you resolve the issue, you must restart the Compute service.
    • Enhancement
    • Done
    • Automated
    • OSPPlanningCycle3, 2023Q1
    • Approved

      https://specs.openstack.org/openstack/nova-specs/specs/2023.1/approved/stable-compute-uuid.html

      The nova-compute service does not strongly correlate with the unique identifier used to represent itself. In most cases, we use the system hostname as the identifier by which we locate our Service and ComputeNode records in the database. However, hostnames can change (both intentionally and unintentionally) which makes this problematic. The Nova project has long said “don’t do that” although, in reality, we must be less fragile and able to detect and protect against database corruption if it happens.

          There are no Sub-Tasks for this issue.

              dasmith@redhat.com Dan Smith
              smooney@redhat.com Sean Mooney
              rhos-dfg-compute
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: