VMware: nova nodes crash on 503 errors, control of vSphere infrastructure completely lost
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Shawn Hartsock | ||
VMwareAPI-Team |
In Progress
|
Critical
|
Shawn Hartsock |
Bug Description
Related to https:/
The result is administrative control over the entire vSphere, vCenter, and ESX infrastructure is temporarily lost.
Python CLI users experience:
pyVmomi.
dynamicType = <unset>,
dynamicProperty = (vmodl.
msg = '503 Service Unavailable',
faultCause = <unset>,
faultMessage = (vmodl.
}
VpXClient users experience:
Call "ServiceInstanc
OpenStack users experience:
2014-03-14 08:55:06.579 ERROR suds.client [-] <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns0=
<ns1:Body>
<
<ns0:_this type="ServiceIn
<
</ns1:Body>
</SOAP-
2014-03-14 08:55:06.581 CRITICAL nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
2014-03-14 08:55:06.581 TRACE nova.virt.
All administrative control of the cloud is temporarily lost for a timespan of up to 30 minutes.
Changed in nova: | |
status: | New → In Progress |
importance: | Undecided → High |
milestone: | none → icehouse-rc1 |
Changed in openstack-vmwareapi-team: | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Shawn Hartsock (hartsock) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-rc1 → 2014.1 |
See: https:/ /review. openstack. org/#/c/ 75262/