yahoo-eng-team team mailing list archive

[Chris Behrens <1157330@xxxxxxxxxxxxxxxxxx>]

Not sure if this is truly a bug or not.   I can't seem to reproduce it
on a fresh compute_nodes table.  However, if I have a compute_nodes
entry leftover... from switching from XenAPI -> fake... I see this
problem just trying to build *1* instance.  The problem is that the
'nodename' changes.  The fake driver advertises a 'fake-mini' nodename.

This may help if you switch from kvm -> fake:

http://paste.openstack.org/show/34095/

That should make the fake driver use the same nodename as was probably
used for kvm.   But ultimately, I'm not sure just switching the driver
on a host should "just work".  XenAPI's nodename is the host in dom0.
kvm's nodename is the same as the nova-compute hostname.  There's all
sorts of things that may need to be cleaned when swapping the driver.

I would try repeating this when an empty compute nodes table and see if
this is still a bug.

** Changed in: nova
       Status: Confirmed => Won't Fix

** Changed in: nova
       Status: Won't Fix => Triaged

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

Title:
  error: 'is not a valid node managed by this compute host.' under load

Status in OpenStack Compute (Nova):
  Triaged

Bug description:
  Using Devstack (Grizzly-3) and nova  SHA1
  5aec4001eb30197f88467e0519203a52c3acd431.

  And setting 'compute_driver = nova.virt.fake.FakeDriver' in nova.conf

  
  vagrant@precise64:~$ nova image-list
  +--------------------------------------+---------------------------------+--------+--------+
  | ID                                   | Name                            | Status | Server |
  +--------------------------------------+---------------------------------+--------+--------+
  | 90e59cc9-503f-46e8-873e-13cde01b1252 | cirros-0.3.1-x86_64-uec         | ACTIVE |        |
  | 8097952f-6ef8-440b-bdf4-dfac34746396 | cirros-0.3.1-x86_64-uec-kernel  | ACTIVE |        |
  | 23828452-dc20-4e4e-a505-86abc77a4cc3 | cirros-0.3.1-x86_64-uec-ramdisk | ACTIVE |        |
  +--------------------------------------+---------------------------------+--------+--------+

  When trying to run 100 vms  as admin user using

  $ nova boot --image 90e59cc9-503f-46e8-873e-13cde01b1252 --flavor
  m1.nano --num-instances 100 test

  over %10 fail with the following error:

  {u'message': u'NovaException', u'code': 500, u'details': u'precise64
  is not a valid node managed by this compute host.

  
  http://paste.openstack.org/show/34069/

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