[Yahoo-eng-team] [Bug 1607313] Re: Inconsistency in data stored in libvirt.xml file

2018-10-02 Thread Corey Bryant 
Marking as Fix Released for Ubuntu Ocata as it has nova 15.1.3.

** Changed in: cloud-archive/ocata
   Status: Fix Committed => Fix Released

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

Title:
  Inconsistency in data stored in libvirt.xml file

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Incomplete
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Incomplete

Bug description:
  Operations involved : 
  nova migrate
  nova evacuate
  nova live-migration

  The above mentioned operations on instances lead to creation of a new
  instance on a new compute host. It has been observed that the 'owner'
  information in the libvirt.xml file is populated with the
  username/projectname(tenantname) of the user performing any of the
  above operations.

  For instance,

  There's an instance 'ins-1' in project/tenant 'pro-1' owned by user 'user01' 
launched on compute host 'compute-101'.
  Now, an admin user named 'osadmin' from project 'admin', performs operation 
  `nova live-migration asdfghi123xyz compute-102`  
  * AD-123 (ID if ins-1)

  This leads to a live migration of ins-1 from compute-101 to compute-102.
  Now, the file /var/lib/nova/instances/asdfghi123xyz/libvirt.xml in 
compute-102 will have 

  
  osadmin
  admin
  

  which ideally should be,

  
  user01
  pro-1
  
   

  This inconsistency is seen in all the operations mentioned, i.e. evacuate, 
migrate, live-
  migration.

  
  Related commands : 
  nova live-migration SERVER HOST_NAME
  nova evacuate EVACUATED_SERVER_NAME HOST_B
  nova migrate VM_ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1607313/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1607313] Re: Inconsistency in data stored in libvirt.xml file

2018-10-02 Thread Matt Riedemann 
** Changed in: nova/ocata
   Status: In Progress => Fix Released

** Changed in: nova/ocata
 Assignee: (unassigned) => György Szombathelyi (gyurco)

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

Title:
  Inconsistency in data stored in libvirt.xml file

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Incomplete
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Incomplete

Bug description:
  Operations involved : 
  nova migrate
  nova evacuate
  nova live-migration

  The above mentioned operations on instances lead to creation of a new
  instance on a new compute host. It has been observed that the 'owner'
  information in the libvirt.xml file is populated with the
  username/projectname(tenantname) of the user performing any of the
  above operations.

  For instance,

  There's an instance 'ins-1' in project/tenant 'pro-1' owned by user 'user01' 
launched on compute host 'compute-101'.
  Now, an admin user named 'osadmin' from project 'admin', performs operation 
  `nova live-migration asdfghi123xyz compute-102`  
  * AD-123 (ID if ins-1)

  This leads to a live migration of ins-1 from compute-101 to compute-102.
  Now, the file /var/lib/nova/instances/asdfghi123xyz/libvirt.xml in 
compute-102 will have 

  
  osadmin
  admin
  

  which ideally should be,

  
  user01
  pro-1
  
   

  This inconsistency is seen in all the operations mentioned, i.e. evacuate, 
migrate, live-
  migration.

  
  Related commands : 
  nova live-migration SERVER HOST_NAME
  nova evacuate EVACUATED_SERVER_NAME HOST_B
  nova migrate VM_ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1607313/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1607313] Re: Inconsistency in data stored in libvirt.xml file

2018-02-15 Thread James Page 
** Also affects: nova (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: nova (Ubuntu)
   Status: New => Fix Released

** Changed in: nova (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: nova (Ubuntu)
   Importance: Undecided => Low

** Changed in: nova (Ubuntu Xenial)
   Status: New => Incomplete

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Changed in: cloud-archive
   Status: New => Fix Released

** Changed in: cloud-archive/ocata
   Status: New => Confirmed

** Changed in: cloud-archive/ocata
   Importance: Undecided => Medium

** Changed in: cloud-archive/mitaka
   Status: New => Incomplete

** Changed in: cloud-archive
   Importance: Undecided => Low

** Changed in: cloud-archive/mitaka
   Importance: Undecided => 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/1607313

Title:
  Inconsistency in data stored in libvirt.xml file

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Incomplete
Status in Ubuntu Cloud Archive ocata series:
  Confirmed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Incomplete

Bug description:
  Operations involved : 
  nova migrate
  nova evacuate
  nova live-migration

  The above mentioned operations on instances lead to creation of a new
  instance on a new compute host. It has been observed that the 'owner'
  information in the libvirt.xml file is populated with the
  username/projectname(tenantname) of the user performing any of the
  above operations.

  For instance,

  There's an instance 'ins-1' in project/tenant 'pro-1' owned by user 'user01' 
launched on compute host 'compute-101'.
  Now, an admin user named 'osadmin' from project 'admin', performs operation 
  `nova live-migration asdfghi123xyz compute-102`  
  * AD-123 (ID if ins-1)

  This leads to a live migration of ins-1 from compute-101 to compute-102.
  Now, the file /var/lib/nova/instances/asdfghi123xyz/libvirt.xml in 
compute-102 will have 

  
  osadmin
  admin
  

  which ideally should be,

  
  user01
  pro-1
  
   

  This inconsistency is seen in all the operations mentioned, i.e. evacuate, 
migrate, live-
  migration.

  
  Related commands : 
  nova live-migration SERVER HOST_NAME
  nova evacuate EVACUATED_SERVER_NAME HOST_B
  nova migrate VM_ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1607313/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1607313] Re: Inconsistency in data stored in libvirt.xml file

2018-01-30 Thread Matt Riedemann 
** Also affects: nova/ocata
   Importance: Undecided
   Status: New

** Changed in: nova/ocata
   Status: New => In Progress

** Changed in: nova/ocata
 Assignee: (unassigned) => Danil Akhmetov (dinobot)

** Changed in: nova/ocata
 Assignee: Danil Akhmetov (dinobot) => György Szombathelyi (gyurco)

** Changed in: nova/ocata
   Importance: Undecided => 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/1607313

Title:
  Inconsistency in data stored in libvirt.xml file

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress

Bug description:
  Operations involved : 
  nova migrate
  nova evacuate
  nova live-migration

  The above mentioned operations on instances lead to creation of a new
  instance on a new compute host. It has been observed that the 'owner'
  information in the libvirt.xml file is populated with the
  username/projectname(tenantname) of the user performing any of the
  above operations.

  For instance,

  There's an instance 'ins-1' in project/tenant 'pro-1' owned by user 'user01' 
launched on compute host 'compute-101'.
  Now, an admin user named 'osadmin' from project 'admin', performs operation 
  `nova live-migration asdfghi123xyz compute-102`  
  * AD-123 (ID if ins-1)

  This leads to a live migration of ins-1 from compute-101 to compute-102.
  Now, the file /var/lib/nova/instances/asdfghi123xyz/libvirt.xml in 
compute-102 will have 

  
  osadmin
  admin
  

  which ideally should be,

  
  user01
  pro-1
  
   

  This inconsistency is seen in all the operations mentioned, i.e. evacuate, 
migrate, live-
  migration.

  
  Related commands : 
  nova live-migration SERVER HOST_NAME
  nova evacuate EVACUATED_SERVER_NAME HOST_B
  nova migrate VM_ID

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1607313] Re: Inconsistency in data stored in libvirt.xml file

2017-03-15 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/399679
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=3f2935872da311f79b5fd4d51fb50b4fcf8d2bcd
Submitter: Jenkins
Branch:master

commit 3f2935872da311f79b5fd4d51fb50b4fcf8d2bcd
Author: Danil Akhmetov 
Date:   Fri Nov 18 19:27:37 2016 +0300

Use proper user and tenant in the owner section of libvirt.xml.

Nova takes instance ownership info from request context when it updates
libvirt.xml, which is not always correct. A real instance owner should
be used to avoid inconsistency in the data stored in the XML file.

Change-Id: Ib1e4803ba4ff17894a0905bcf116225defa5b58a
Closes-Bug: #1607313


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  Inconsistency in data stored in libvirt.xml file

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Operations involved : 
  nova migrate
  nova evacuate
  nova live-migration

  The above mentioned operations on instances lead to creation of a new
  instance on a new compute host. It has been observed that the 'owner'
  information in the libvirt.xml file is populated with the
  username/projectname(tenantname) of the user performing any of the
  above operations.

  For instance,

  There's an instance 'ins-1' in project/tenant 'pro-1' owned by user 'user01' 
launched on compute host 'compute-101'.
  Now, an admin user named 'osadmin' from project 'admin', performs operation 
  `nova live-migration asdfghi123xyz compute-102`  
  * AD-123 (ID if ins-1)

  This leads to a live migration of ins-1 from compute-101 to compute-102.
  Now, the file /var/lib/nova/instances/asdfghi123xyz/libvirt.xml in 
compute-102 will have 

  
  osadmin
  admin
  

  which ideally should be,

  
  user01
  pro-1
  
   

  This inconsistency is seen in all the operations mentioned, i.e. evacuate, 
migrate, live-
  migration.

  
  Related commands : 
  nova live-migration SERVER HOST_NAME
  nova evacuate EVACUATED_SERVER_NAME HOST_B
  nova migrate VM_ID

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp