yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #53192
[Bug 1260440] Re: nova-compute host is added to scheduling pool before Neutron can bind network ports on said host
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY
** Changed in: nova
Importance: High => Undecided
** Changed in: nova
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1260440
Title:
nova-compute host is added to scheduling pool before Neutron can bind
network ports on said host
Status in neutron:
Incomplete
Status in OpenStack Compute (nova):
Expired
Status in tripleo:
Fix Released
Bug description:
This is a race condition.
Given a cloud with 0 compute nodes available, on a compute node:
* Start up neutron-openvswitch-agent
* Start up nova-compute
* nova boot an instance
Scenario 1:
* neutron-openvswitch-agent registers with Neutron before nova tries to boot instance
* port is bound to agent
* instance boots with correct networking
Scenario 2:
* nova schedules instance to host before neutron-openvswitch-agent is registered with Neutron
* nova instance fails with vif_type=binding_failed
* instance is in ERROR state
I would expect that Nova would not try to schedule instances on
compute hosts that are not ready.
Please also see this mailing list thread for more info:
http://lists.openstack.org/pipermail/openstack-
dev/2013-December/022084.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1260440/+subscriptions
References