heat tempest tests fail after delpoy cluster with mos7.0-mu1

Bug #1514463 reported by Oleksiy Butenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
Unassigned

Bug Description

Steps:
1. Delpoy env
Env: MOS 7.0 iso 301 with repo for update:
    1. deb http://mirror.fuel-infra.org/mos-repos/ubuntu/7.0/ mos7.0-proposed main restricted
    2. http://mirror.fuel-infra.org/mos-repos/ubuntu/7.0/ mos7.0-security main restricted

2. Run tempest tests for heat(tempest.api.orchestration)

Actual result:
test_created_network[id-c572b915-edb1-4e90-b196-c7199a6848c0,network] Failed
test_created_resources[id-f9e2664c-bc44-4eef-98b6-495e4f9d74b3] Failed
test_created_router[id-96af4c7f-5069-44bc-bdcf-c0390f8a67d1,network] Failed
test_created_server[compute,id-75d85316-4ac2-4c0e-a1a9-edd2148fc10e,network] Failed
test_created_router_interface[id-89f605bd-153e-43ee-a0ed-9919b63423c5,network] Failed
test_created_subnet[id-e8f84b96-f9d7-4684-ad5f-340203e9f2c2,network] Failed

Traceback (most recent call last):
testtools.testresult.real._StringException: Traceback (most recent call last):
File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 272, in setUpClass
six.reraise(etype, value, trace)
File "/home/developer/mos-tempest-runner/tempest/tempest/test.py", line 265, in setUpClass
cls.resource_setup()
File "/home/developer/mos-tempest-runner/tempest/tempest/api/orchestration/stacks/test_neutron_resources.py", line 87, in resource_setup
server_id = body['physical_resource_id']
KeyError: 'physical_resource_id'

nova-all.log:
http://paste.openstack.org/show/478323/

Changed in mos:
importance: Undecided → High
milestone: none → 7.0-updates
status: New → Confirmed
Revision history for this message
Oleksiy Butenko (obutenko) wrote :

https://goo.gl/LDzykT - Diagnostic Snapshot

Revision history for this message
Oleksiy Butenko (obutenko) wrote :

Creation of stack with WaitCondition didn't work in heat(kilo).
https://bugs.launchpad.net/mos/+bug/1497273

Changed in mos:
status: Confirmed → Invalid
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.