[Yahoo-eng-team] [Bug 1524114] Re: nova-scheduler also loads deleted instances at startup

[Tardis Xu]

*** This bug is a duplicate of bug 1524421 ***
https://bugs.launchpad.net/bugs/1524421

** This bug has been marked a duplicate of bug 1524421
   Host Manager reads deleted instance info on startup

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

Title:
  nova-scheduler also loads deleted instances at startup

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  nova-scheduler is loading all instances (including deleted) at
  startup.

  Experienced problems when each node has >6000 deleted instances, even when 
using batches of 10 nodes.
  Each query can take several minutes and transfer several GB of data.
  This prevented nova-scheduler connect to rabbitmq.

  
  ###
  When nova-scheduler starts it calls "_async_init_instance_info()" and it does 
an "InstanceList.get_by_filters" that uses batches of 10 nodes. This uses 
"instance_get_all_by_filters_sort", however "Deleted instances will be returned 
by default, unless there's a filter that says otherwise".
  Adding the filter: {"deleted": False} fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1524114/+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 1524627] Re: nova libvirt xml generate wrong metadata

[Tardis Xu]

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 , view metadata:
  
  demo
  demo
  
  4. login as admin/admin
  5. hard boot the instance
  6. virsh dumpxml , view metadata:
  
  admin
  admin
  

  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

-- 
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 1524363] Re: Owner metadata is missing when regenerating libvirt XML after host reboot

[Tardis Xu]

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
booted when host up, the context is admin. 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/1524363

Title:
  Owner metadata is missing when regenerating libvirt XML after host
  reboot

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Environment:

  devstack running OpenStack from master.

  Steps to reproduce:

  1. Make sure that resume_guests_state_on_host_boot=True in nova.conf.
  2. Boot an instance.
  3. Check that the libvirt XML contains a nova:owner element with the project 
and user ids [1].
  4. Stop the nova-compute service.
  5. Destroy the instance using virsh. This is to simulate the reboot of the 
host.
  6. Restart the nova-compute service.
  7. Check that the instance is respawned.

  Expected result:

  The project id and user id are still present in the libvirt XML.

  Actual result:

  The project id and user id are missing [2].

  [1] http://paste.openstack.org/show/481314/
  [2] http://paste.openstack.org/show/481315/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1524363/+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 1524627] [NEW] nova libvirt xml generate wrong metadata

[Tardis Xu]

Public bug reported:

Environment:

devstack running OpenStack from master.

Steps to reproduce:

1. login as demo/demo
2. boot a instance
3. virsh dumpxml , view metadata:

demo
demo

4. login as admin/admin
5. hard boot the instance
6. virsh dumpxml , view metadata:

admin
admin


Expected result:

The project and user metadata cannot get from current context.

Actual result:

The project and user metadata all get from current context.

** Affects: nova
 Importance: Medium
 Assignee: Tardis Xu (xiaoxubeii)
 Status: In Progress


** Tags: compute libvirt xml

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

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

** Changed in: nova
 Assignee: (unassigned) => Tardis Xu (xiaoxubeii)

** Tags added: compute

** Tags added: libvirt xml

-- 
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):
  In Progress

Bug description:
  Environment:

  devstack running OpenStack from master.

  Steps to reproduce:

  1. login as demo/demo
  2. boot a instance
  3. virsh dumpxml , view metadata:
  
  demo
  demo
  
  4. login as admin/admin
  5. hard boot the instance
  6. virsh dumpxml , view metadata:
  
  admin
  admin
  

  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

-- 
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 1510395] Re: resize vm across azs

[Tardis Xu]

** Changed in: nova
   Status: New => Invalid

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

Title:
  resize vm across azs

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Problem:

  i create instance1 in az A, one day the instance was resized and in az
  B.this confused me.

  my nova filter config is :
  
scheduler_default_filters=RetryFilter,AvailabilityZoneFilter,RamFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter

  1. Exact version of Nova/OpenStack you are running:

  openstack juno

  2. Relevant log files:

  none

  3. Reproduce steps:

  random

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1510395/+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 1512267] Re: HTTP Unexpected API Error during network-create

[Tardis Xu]

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

** Changed in: nova
   Status: New => Invalid

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

Title:
  HTTP Unexpected API Error during network-create

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1. reedip@reedip-VirtualBox:/opt/stack/nova$ git log -1
  commit 542552754d8da0a97cde32f07a777179c4be608f
  Merge: 1dfc36d b08b20b
  Author: Jenkins 
  Date:   Tue Oct 20 15:21:38 2015 +

  Merge "Make secgroup rules refresh with
  refresh_instance_security_rules()"

  2. Please see: http://paste.openstack.org/show/477745/   for debug
  logs and devstack log snippet

  3. Execute Network create as :
  nova network-create --mtu 1500 --mtu 9000  --fixed-range-v4 1.1.1.1/24 M

  4. Expected Result  :Network with Label M and MTU 9000 should be created.
  5. Actual result in the PASTE-IT link given above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1512267/+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