UUID mismatch on newer cloud-init

Bug #1770696 reported by Matthew Edmonds on 2018-05-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Matthew Edmonds

Bug Description

The version of cloud-init in Ubuntu 18.04 is much newer than that in other distros. When the newer version processes an instance to determine if it is first boot or not, it compares the config drive UUID with the VM UUID. We need to make those values the same for a given VM / config drive pair.

This was already addressed in the master branch with https://github.com/openstack/nova-powervm/commit/5d438733eb310b278d44aada7340a56ee9325063 but we also need to address on any stable branch that may be used with newer cloud-init versions.

Changed in nova-powervm:
assignee: nobody → Matthew Edmonds (edmondsw)
status: New → In Progress

Reviewed: https://review.openstack.org/567894
Committed: https://git.openstack.org/cgit/openstack/nova-powervm/commit/?id=220a7cdc684043139de43ef5e8d4602ad4d9faf0
Submitter: Zuul
Branch: stable/queens

commit 220a7cdc684043139de43ef5e8d4602ad4d9faf0
Author: Eric Fried <email address hidden>
Date: Thu Feb 2 15:22:34 2017 -0600

    Sanitize the config drive UUID

    When cloud-init processes an instance to determine
    if it is first boot or not, it compares the config
    drive UUID with the VM UUID. This change makes those
    values the same now for a given VM / config drive pair.

    Closes-Bug: #1770696
    Change-Id: I128a0bc886b020d67241c67a874cf8d06e791b57
    (cherry picked from commit 5d438733eb310b278d44aada7340a56ee9325063)

tags: added: in-stable-queens
Changed in nova-powervm:
status: In Progress → Fix Committed

This issue was fixed in the openstack/nova-powervm 6.0.2 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers