vCenter OSTF thinks there are no compute nodes and fails

Bug #1361845 reported by Andrew Woodward
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Tatyana Dubyk
5.0.x
Fix Committed
High
Tatyana Dubyk

Bug Description

in 5.0.1 setting up vCenter as the compute, OSTF fails tests that need compute nodes stating that there is no compute resource even though I can provision instances just fine. I assume OSTF is just following what Fuel is telling it in that there are no nodes with the compute role.

OSTF should probably inspect the service list instead of assuming what fuel tells it is what it expects.

Tags: vcenter
Revision history for this message
Dima Shulyak (dshulyak) wrote :

Andrew, can you attach snapshot or atleast specify version and names of tests that failed?

It looks like that we simply need to backport this patch https://review.openstack.org/#/c/117235/ for stable/5.0.

Revision history for this message
Dima Shulyak (dshulyak) wrote :

Sorry, i somehow missed version. So i think my assumption is correct and we need to backport mentioned patch.

Actually we need two:

- https://review.openstack.org/#/c/108651/
- https://review.openstack.org/#/c/117235/

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/5.1.x
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-ostf (stable/5.0)

Change abandoned by Tatyana Dubyk (<email address hidden>) on branch: stable/5.0
Review: https://review.openstack.org/117730

Revision history for this message
Tatyana Dubyk (tdubyk) wrote :

all my changes according this bug have already been merged in stable/5.0

Changed in fuel:
status: Invalid → Confirmed
status: Confirmed → Fix Committed
Revision history for this message
Tatyana Dubyk (tdubyk) wrote :
Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
Tatyana Dubyk (tdubyk) wrote :

checked on fuel-5.0-26-2014-05-27_05-51-41.iso

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.