Mirantis OpenStack

After HA cluster 5.0 is updated to 5.0.2, platform test "Typical stack actions" fails

Bug #1364026 reported by Dennis Dmitriev on 2014-09-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Mirantis OpenStack	Invalid	High	Igor Yozhikov	Mirantis OpenStack 5.1
	5.0.x	Fix Committed	High	Igor Yozhikov	Mirantis OpenStack 5.0.2

Bug Description

Steps to reproduce:
1. Deploy cluster 1 with release 2014.1 (5.0): Ubuntu/HA, nova/vlan, 3 controllers, 1 compute, 1 cinder
2. Run OSTF
3. Upload and unpack tarball with fuel-5.1 release (build #491) to /var
4. run upgrade.sh with openstack
5. Navigate to UI and update cluster 1 to release 2014.1.1-5.0.2
6. Run OSTF

Expexted result: OSTF passes all tests

Actual result: Platform test "Typical stack actions..." is failed on the first step "1. Create a stack." with the following error:

====================
heatclient.common.http: DEBUG: curl -i -X GET -H 'X-Auth-Token: f0e5fc6b2a41478797ef8d99252a50f3' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'User-Agent: python-heatclient' http://172.16.21.2:8004/v1/b899bf2206c242868d54c22795d62d70/stacks?
urllib3.connectionpool: INFO: Starting new HTTP connection (1): 10.20.21.4
urllib3.connectionpool: DEBUG: "GET http://172.16.21.2:8004/v1/b899bf2206c242868d54c22795d62d70/stacks HTTP/1.1" 200 14
heatclient.common.http: DEBUG:
HTTP/1.1 200 OK
date: Mon, 01 Sep 2014 12:40:09 GMT
content-length: 14
via: 1.1 192.168.0.4:8004
content-type: application/json; charset=UTF-8
{"stacks": []}
fuel_health.common.test_mixins: DEBUG: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/fuel_health/common/test_mixins.py", line 186, in verify
    result = func(*args, **kwargs)
  File "/usr/lib/python2.6/site-packages/fuel_health/heatmanager.py", line 84, in _create_stack
    self.set_resource(stack.id, stack)
AttributeError: 'NoneType' object has no attribute 'id'
===================

Tags:

Revision history for this message

Dennis Dmitriev (ddmitriev) wrote on 2014-09-01:

fuel-snapshot-2014-09-01_15-06-09.tgz Edit (9.1 MiB, application/x-tar)

Mike Scherbakov (mihgen) on 2014-09-01

Changed in fuel:
assignee:	Fuel for Openstack (fuel) → Fuel Python Team (fuel-python)

Aleksey Kasatkin (alekseyk-ru) on 2014-09-01

tags:

added: ostf

Nastya Urlapova (aurlapova) on 2014-09-01

Changed in fuel:
importance:	Undecided → High

Ihor Kalnytskyi (ikalnytskyi) on 2014-09-01

tags:

added: update

Ihor Kalnytskyi (ikalnytskyi) on 2014-09-01

Changed in fuel:
assignee:	Fuel Python Team (fuel-python) → Igor Kalnitsky (ikalnitsky)

Ihor Kalnytskyi (ikalnytskyi) on 2014-09-01

Changed in fuel:
status:	New → Confirmed

Revision history for this message

Vladimir Kuklin (vkuklin) wrote on 2014-09-02:

this either OSTF or Heat problem itself. Assigning to MOS-Heat team

Changed in fuel:
assignee:	Igor Kalnitsky (ikalnitsky) → MOS Heat (mos-heat)

Sergey Kraynev (skraynev) on 2014-09-02

Changed in fuel:
assignee:	MOS Heat (mos-heat) → Anastasia Kuznetsova (akuznetsova)

Revision history for this message

Artem Roma (aroma-x) wrote on 2014-09-02:

Ok, I've inspected logs from the snapshot and there is an error of stack creation operation in heat.engine.resource.log on one of controllers (node-3) hence described error is caused by heat code. The only mishit from ostf side is that in logs addition traceback is present but on UI all error messages are correct and logically appropriate.

Also I couldn't reproduce this bug on my machine so maybe it is some temporary floating issue with heat itself and I highly doubt that it is caused by upgrade process. But to be 100% percent sure could you please reproduce this bug and provide access to environment in order to investigate the issue on the spot?

OpenStack Infra (hudson-openstack) on 2014-09-02

Changed in fuel:
assignee:	Anastasia Kuznetsova (akuznetsova) → Artem Roma (aroma-x)
status:	Confirmed → In Progress

Revision history for this message

Anastasia Kuznetsova (akuznetsova) wrote on 2014-09-02:

Artem Roma, can you explain how your fix help here ? Because I've inspected logs too and as for me problem not in ostf test, but judging by the heat-engine logs the problem is that engine haven't start.

Revision history for this message

Artem Roma (aroma-x) wrote on 2014-09-02:

Anastasia, sry, my mistake, I meant another bug in Closes-Bug section=)

Changed in fuel:
assignee:	Artem Roma (aroma-x) → Anastasia Kuznetsova (akuznetsova)
status:	In Progress → Confirmed

Nastya Urlapova (aurlapova) on 2014-09-02

Changed in mos:
status:	New → Confirmed
importance:	Undecided → High
assignee:	nobody → Anastasia Kuznetsova (akuznetsova)
milestone:	none → 5.1
no longer affects:	fuel