Public bug reported: Failed to create a instance into a server group with affinity policy and the retry filter is enabled. The scheduler selected a host, say it's 'host2', but the host2's hypervisor has some problems and failed to boot the instance. Then scheduler retry to boot the instance. Scheduler failed to select host for the instance. As the group with affinity request boot instance to host2 but host2 is not OK.
For this case, it's not make sense that the group affinity policy take effect when the first instance in the group is retrying to create. ** 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/1369385 Title: Fail to create instance to a server group with affinity policy. Status in OpenStack Compute (Nova): New Bug description: Failed to create a instance into a server group with affinity policy and the retry filter is enabled. The scheduler selected a host, say it's 'host2', but the host2's hypervisor has some problems and failed to boot the instance. Then scheduler retry to boot the instance. Scheduler failed to select host for the instance. As the group with affinity request boot instance to host2 but host2 is not OK. For this case, it's not make sense that the group affinity policy take effect when the first instance in the group is retrying to create. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1369385/+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