yahoo-eng-team team mailing list archive

[György Szombathelyi <gyurco@xxxxxxxxxxx>]

Public bug reported:

When instances are booted automatically after a compute reboot, the
libvirt.xml-s are recreated withot the nova:owner data. And ceilometer
likes use it.

The relevant part of the xml after the reboot:
.
.
      </nova:flavor>
      <nova:owner/>
      <nova:root type="image" uuid="98199656-154f-4481-8ee9-b5480c9f9b8b"/>
    </nova:instance>
  </metadata>
.
.
At the first sight, the owner metadata is created in _get_guest_config_meta in virt/libvirt/driver.py, but only when context is not None. But when nova starts the guests on its own, probably it is None?

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1736457

Title:
  resume_guests_state_on_host_boot = True creates libvirt.xml with empty
  nova:owner

Status in OpenStack Compute (nova):
  New

Bug description:
  When instances are booted automatically after a compute reboot, the
  libvirt.xml-s are recreated withot the nova:owner data. And ceilometer
  likes use it.

  The relevant part of the xml after the reboot:
  .
  .
        </nova:flavor>
        <nova:owner/>
        <nova:root type="image" uuid="98199656-154f-4481-8ee9-b5480c9f9b8b"/>
      </nova:instance>
    </metadata>
  .
  .
  At the first sight, the owner metadata is created in _get_guest_config_meta in virt/libvirt/driver.py, but only when context is not None. But when nova starts the guests on its own, probably it is None?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1736457/+subscriptions