nova-compute host is added to scheduling pool before Neutron can bind network ports on said host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned | ||
neutron |
Invalid
|
Undecided
|
Unassigned | ||
tripleo |
Fix Released
|
Critical
|
Clint Byrum |
Bug Description
This is a race condition.
Given a cloud with 0 compute nodes available, on a compute node:
* Start up neutron-
* Start up nova-compute
* nova boot an instance
Scenario 1:
* neutron-
* port is bound to agent
* instance boots with correct networking
Scenario 2:
* nova schedules instance to host before neutron-
* nova instance fails with vif_type=
* 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://
Changed in tripleo: | |
assignee: | nobody → Clint Byrum (clint-fewbar) |
status: | Triaged → In Progress |
Changed in neutron: | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
tags: | added: neutron-agent |
Changed in neutron: | |
status: | Incomplete → Invalid |
This breaks deployment of new clouds in TripleO sometimes, and will likely break scaling too. Hence the Critical status.