yahoo-eng-team team mailing list archive

[David Patterson <David.Patterson@xxxxxxxxxxx>]

Public bug reported:

If anti-affinity policy is set for two different servers, and only one
host is available, a stack trace is shown instead of a error message.
Failure is expected, but a message about why it failed would be helpful.

On a single node devstack setup:

nova server-group-create --policy anti-affinity aagroup

nova boot --flavor m1.nano --image cirros-0.3.1-x86_64-uec --nic net-
id=ea784f2b-b262-451a-821a-5ee7f69b3d63 --hint group=0f2b71ea-3dc3-423d-
a9f4-41ac5d0fff07 server1

nova boot --flavor m1.nano --image cirros-0.3.1-x86_64-uec --nic net-
id=ea784f2b-b262-451a-821a-5ee7f69b3d63 --hint group=0f2b71ea-3dc3-423d-
a9f4-41ac5d0fff07 server2

server1 boots fine
server2 has Status Error and Power State No State

Horizon shows:

Fault
Message
unsupported operand type(s) for |: 'list' and 'set'
Code
500
Details
File "/opt/stack/nova/nova/scheduler/manager.py", line 140, in run_instance legacy_bdm_in_spec) File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 86, in schedule_run_instance filter_properties, instance_uuids) File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 289, in _schedule filter_properties) File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 275, in _setup_instance_group filter_properties['group_hosts'] = user_hosts | group_hosts
Created
April 3, 2014, 1:58 p.m.

** Affects: nova
     Importance: Undecided
         Status: New

** Attachment added: "Sorry for the large logs.  Look at end of screen-n-sch*"
   https://bugs.launchpad.net/bugs/1301982/+attachment/4063305/+files/logs.tar.gz

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

Title:
  anti-affinity server boot failure shows stack trace

Status in OpenStack Compute (Nova):
  New

Bug description:
  If anti-affinity policy is set for two different servers, and only one
  host is available, a stack trace is shown instead of a error message.
  Failure is expected, but a message about why it failed would be
  helpful.

  On a single node devstack setup:

  nova server-group-create --policy anti-affinity aagroup

  nova boot --flavor m1.nano --image cirros-0.3.1-x86_64-uec --nic net-
  id=ea784f2b-b262-451a-821a-5ee7f69b3d63 --hint group=0f2b71ea-3dc3
  -423d-a9f4-41ac5d0fff07 server1

  nova boot --flavor m1.nano --image cirros-0.3.1-x86_64-uec --nic net-
  id=ea784f2b-b262-451a-821a-5ee7f69b3d63 --hint group=0f2b71ea-3dc3
  -423d-a9f4-41ac5d0fff07 server2

  server1 boots fine
  server2 has Status Error and Power State No State

  Horizon shows:

  Fault
  Message
  unsupported operand type(s) for |: 'list' and 'set'
  Code
  500
  Details
  File "/opt/stack/nova/nova/scheduler/manager.py", line 140, in run_instance legacy_bdm_in_spec) File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 86, in schedule_run_instance filter_properties, instance_uuids) File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 289, in _schedule filter_properties) File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 275, in _setup_instance_group filter_properties['group_hosts'] = user_hosts | group_hosts
  Created
  April 3, 2014, 1:58 p.m.

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