yahoo-eng-team team mailing list archive

[baiyuan <bybai@xxxxxxxxxx>]

Public bug reported:

1,
nova version:root@byrh09:/opt/stack/nova# git log -1
commit 9c45ff348d7eb75ae8098b6c950db549aaff282a
Merge: 480c419 07b5373
Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
Date:   Tue Mar 31 08:14:43 2015 +0000

    Merge "Fix API links and labels"
2, reproduce steps:
in my environment, there are 2 ironic baremetal hosts; I want to use nova boot to deploy these 2 nodes; each nova flavor can select one baremetal host;
When I nova boot one instance, it start to deploy a baremetal host, the task state is apawning,power state is NOSTATE, status is build, it work well and it start to deploy the right host based on nova flavor; then I execute another different nova boot for another instance, the second nova boot fails and it cannot find the right servers, the second baremetal host;
If the first nova boot finished, and its status is ACTIVE, power state is running, at this time, I execute the same second nova boot command, it can select the second right baremetal host;
I think if different nova boot command use different  flavor and different instance name, there are enough baremetal nodes, these nova boot  should work well;
My commands are as following:
a, nova boot --flavor 21_baremetal --image $XCAT_IMAGE test_xcat  --nic net-id=$net_id --key-name xcat_key
b, nova boot --flavor 23_baremetal --image $XCAT_IMAGE test_pcm  --nic net-id=$net_id --key-name xcat_key

** 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/1442127

Title:
  nova boot fails when there is another nova instance deploying

Status in OpenStack Compute (Nova):
  New

Bug description:
  1,
  nova version:root@byrh09:/opt/stack/nova# git log -1
  commit 9c45ff348d7eb75ae8098b6c950db549aaff282a
  Merge: 480c419 07b5373
  Author: Jenkins <jenkins@xxxxxxxxxxxxxxxxxxxx>
  Date:   Tue Mar 31 08:14:43 2015 +0000

      Merge "Fix API links and labels"
  2, reproduce steps:
  in my environment, there are 2 ironic baremetal hosts; I want to use nova boot to deploy these 2 nodes; each nova flavor can select one baremetal host;
  When I nova boot one instance, it start to deploy a baremetal host, the task state is apawning,power state is NOSTATE, status is build, it work well and it start to deploy the right host based on nova flavor; then I execute another different nova boot for another instance, the second nova boot fails and it cannot find the right servers, the second baremetal host;
  If the first nova boot finished, and its status is ACTIVE, power state is running, at this time, I execute the same second nova boot command, it can select the second right baremetal host;
  I think if different nova boot command use different  flavor and different instance name, there are enough baremetal nodes, these nova boot  should work well;
  My commands are as following:
  a, nova boot --flavor 21_baremetal --image $XCAT_IMAGE test_xcat  --nic net-id=$net_id --key-name xcat_key
  b, nova boot --flavor 23_baremetal --image $XCAT_IMAGE test_pcm  --nic net-id=$net_id --key-name xcat_key

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