yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #28098
[Bug 1408326] Re: Server booted to a server group stucks in scheduling state if the policy filter is not configured
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => kilo-2
--
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/1408326
Title:
Server booted to a server group stucks in scheduling state if the
policy filter is not configured
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
To reproduce the problem:
Remove ServerGroupAntiAffinity from scheduler_default_filters in
nova.conf
$ nova server-group-create my-anti-affinity anti-affinity
$ nova boot --flavor 42 --image 1b0ef685-2a7a-4c11-8e2d-a549215c1b3a --hint group=<uuid of the group created above> vm23
The following exception is visible in the conductor log:
2015-01-07 15:33:44.988 ERROR nova.scheduler.utils [req-675e5f28-59c4-4406-952c-182202aae805 admin admin] ServerGroupAntiAffinityFilter not configured
2015-01-07 15:33:44.988 ERROR oslo.messaging.rpc.dispatcher [req-675e5f28-59c4-4406-952c-182202aae805 admin admin] Exception during message handling: No valid host was found. ServerGroupAntiAffinityFilter not configured
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 137, in _dispatch_and_reply
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher incoming.message))
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 180, in _dispatch
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args)
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 126, in _do_dispatch
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args)
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/conductor/manager.py", line 626, in build_instances
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher filter_properties)
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/scheduler/utils.py", line 311, in setup_instance_group
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher group_info = _get_group_details(context, instance_uuid, group_hosts)
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher File "/opt/stack/nova/nova/scheduler/utils.py", line 291, in _get_group_details
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher raise exception.NoValidHost(reason=msg)
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher NoValidHost: No valid host was found. ServerGroupAntiAffinityFilter not configured
2015-01-07 15:33:44.988 TRACE oslo.messaging.rpc.dispatcher
But the server stuck in scheduling state for ever.
$ nova list
+--------------------------------------+------+--------+------------+-------------+--------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+------+--------+------------+-------------+--------------------+
| 4b919b5c-1db4-4705-a608-8ce8db862b07 | vm23 | BUILD | scheduling | NOSTATE | |
+--------------------------------------+------+--------+------------+-------------+--------------------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1408326/+subscriptions
References