yahoo-eng-team team mailing list archive

[Tardis Xu <xiaoxubeii@xxxxxxxxx>]

The problem is in virt/libvirt/driver.py, _get_guest_config_meta, it
gets the nova owner meta from current context. But if the instance is
rebooted as other context, it will go wrong. I think we can add the
identity cache to instance like network info. If this, we must change
the db table. So I think we should implement it as a bp not a bug.

** Changed in: nova
       Status: In Progress => Opinion

** Changed in: nova
   Importance: Medium => Low

-- 
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/1524627

Title:
  nova libvirt xml generate wrong metadata

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Environment:

  devstack running OpenStack from master.

  Steps to reproduce:

  1. login as demo/demo
  2. boot a instance
  3. virsh dumpxml <instance>, view metadata:
  <nova:owner>
          <nova:user uuid="<demo-uuid>">demo</nova:user>
          <nova:project uuid="demo-project-uuid">demo</nova:project>
  </nova:owner>
  4. login as admin/admin
  5. hard boot the instance
  6. virsh dumpxml <instance>, view metadata:
  <nova:owner>
          <nova:user uuid="<admin-uuid>">admin</nova:user>
          <nova:project uuid="<admin-project-uuid>">admin</nova:project>
  </nova:owner>

  Expected result:

  The project and user metadata cannot get from current context.

  Actual result:

  The project and user metadata all get from current context.

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