vmwareapi drivers - most summary fields need not be set

Bug #1217541 reported by Shawn Hartsock
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Committed
High
Gary Kotton
VMwareAPI-Team
Fix Committed
Critical
Unassigned

Bug Description

In host.py method update_status,

Several status fields may not be set by the vSphere endpoint.

    summary.hardware <- all children will be None
    summary.config
    summary.quickStats.overallMemoryUsage

Write code to handle these missing attributes gracefully.

References:
* http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.wssdk.apiref.doc/vim.host.Summary.html#field_detail
* http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.wssdk.apiref.doc/vim.host.Summary.QuickStats.html

Tags: vmware
Revision history for this message
Shawn Hartsock (hartsock) wrote :

I'm calling this critical, because when it does happen (doesn't always) there will be no work around.

Changed in nova:
status: New → Triaged
importance: Undecided → Medium
importance: Medium → High
importance: High → Critical
description: updated
summary: - vmwareapi drivers - summary.quickStats.overallMemoryUsage need not be
- set
+ vmwareapi drivers - most summary fields need not be set
Revision history for this message
Russell Bryant (russellb) wrote :

I think it's better as High, since it doesn't affect *all* users.

"High if the bug prevents a key feature from working properly for some users (or with a workaround)"

Changed in nova:
importance: Critical → High
tags: added: grizzly-backport-potential
Changed in openstack-vmwareapi-team:
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/44006

Changed in nova:
assignee: nobody → Gary Kotton (garyk)
status: Triaged → In Progress
Gary Kotton (garyk)
Changed in nova:
milestone: none → havana-3
Revision history for this message
Gary Kotton (garyk) wrote :
Download full text (5.6 KiB)

The problem happens if the nova compute service is restarted. This at times has a situation where is is impossible to restart the nova compute service. We should consider changing this to critical. Please see the trace below when I restarted the compute service:

2013-09-02 00:59:40.979 INFO nova.compute.manager [req-10927006-b0e9-4159-9032-6337bbad97e5 None None] Updating host status
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line 97, in wait
    readers.get(fileno, noop).cb(fileno)
  File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 194, in main
    result = function(*args, **kwargs)
  File "/opt/stack/nova/nova/openstack/common/service.py", line 65, in run_service
    service.start()
  File "/opt/stack/nova/nova/service.py", line 154, in start
    self.manager.init_host()
  File "/opt/stack/nova/nova/compute/manager.py", line 757, in init_host
    self._report_driver_status(context)
  File "/opt/stack/nova/nova/compute/manager.py", line 4409, in _report_driver_status
    capabilities = self.driver.get_host_stats(refresh=True)
  File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 363, in get_host_stats
    return self.host_state.get_host_stats(refresh=refresh)
  File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 434, in host_state
    self._cluster)
  File "/opt/stack/nova/nova/virt/vmwareapi/host.py", line 155, in __init__
    self.update_status()
  File "/opt/stack/nova/nova/virt/vmwareapi/host.py", line 201, in update_status
    summary.quickStats.overallMemoryUsage
AttributeError: 'Text' object has no attribute 'overallMemoryUsage'
Removing descriptor: 7
2013-09-02 00:59:41.382 ERROR nova.openstack.common.threadgroup [-] 'Text' object has no attribute 'overallMemoryUsage'
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup Traceback (most recent call last):
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 117, in wait
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup x.wait()
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 49, in wait
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup return self.thread.wait()
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 168, in wait
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup return self._exit_event.wait()
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup return hubs.get_hub().switch()
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 187, in switch
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup return self.greenlet.switch()
2013-09-02 00:59:41.382 TRACE nova.openstack.common.threadgroup File "/usr...

Read more...

Revision history for this message
dan wendlandt (danwent) wrote :

Gary, it sounds like russell's argument is that 'critical' should be reserved for bugs that apply to all users, regardless of what virt driver is used. This is not the case for this bug.

If that is the metric, it seems reasonable for this to be high.

Thierry Carrez (ttx)
Changed in nova:
milestone: havana-3 → havana-rc1
Changed in nova:
importance: High → Medium
Changed in nova:
importance: Medium → High
Revision history for this message
Russell Bryant (russellb) wrote :
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :
Tracy Jones (tjones-i)
Changed in openstack-vmwareapi-team:
status: Triaged → In Progress
Revision history for this message
Gary Kotton (garyk) wrote :
Changed in nova:
status: In Progress → Fix Committed
Changed in openstack-vmwareapi-team:
status: In Progress → Fix Committed
Gary Kotton (garyk)
tags: removed: grizzly-backport-potential
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.