Mirantis OpenStack

Deploy_heat_simple failed with Time limit exceeded

Bug #1353501 reported by Egor Kotko on 2014-08-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Mirantis OpenStack	Invalid	Undecided	Unassigned	Mirantis OpenStack 5.1

Bug Description

{"build_id": "2014-08-06_02-01-17", "ostf_sha": "be71965998364bf8e6415bd38b75c84b63aab867", "build_number": "405", "auth_required": true, "api": "1.0", "nailgun_sha": "f64b06c788e2b92fcb8e678ea6d0c9b86e8d0ab7", "production": "docker", "fuelmain_sha": "124ea87f1ac1c06e27613fe3b31fd5fc6b39e82d", "astute_sha": "99a790ad1b7526cbbd5bf8add0cb2b4e503fccd4", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "513ec5cdcdef74c7419d5bae967b9edc7da8dbd7"}

System test. Ubuntu. Deploy_heat_simple failed with Time limit exceeded

http://jenkins-product.srt.mirantis.net:8080/view/0_master_swarm/job/master_fuelmain.system_test.ubuntu.services_simple/59/testReport/%28root%29/deploy_heat_simple/deploy_heat_simple/

heat-engine log contains:
http://paste.openstack.org/show/91045/

Tags:

Revision history for this message

Egor Kotko (ykotko) wrote on 2014-08-06:

fuel-snapshot-2014-08-06_09-15-43.tgz Edit (3.0 MiB, application/x-tar)

Nastya Urlapova (aurlapova) on 2014-08-06

no longer affects:	fuel
Changed in mos:
importance:	Undecided → High
assignee:	nobody → MOS Heat (mos-heat)
milestone:	none → 5.1

Timur Nurlygayanov (tnurlygayanov) on 2014-08-07

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

Revision history for this message

Sergey Kraynev (skraynev) wrote on 2014-08-07:

This problem looks like fixed in master https://bugs.launchpad.net/heat/+bug/1315044, Also this was backported in stable icehouse, but after our merge commit.
Should we cherry-pick this commit in our 5.1 branch?

Note: These bugs have similar behavior in logs, but I am not sure, that it may be cause of failing test.
According to the heat-engine logs, the real problem is absent data for triggering autoscaling.

One related question: what OS was used for deploying this test lab (not for this test)? centos or ubuntu?

Revision history for this message

Anastasia Kuznetsova (akuznetsova) wrote on 2014-08-07:

After some investigating of this problem, were decided that root of this issue in the problem with Neutron.
During test execution Floating Ip was assigned to VM and after test tried to connect to it, but it wan't successful.

Revision history for this message

Anastasia Kuznetsova (akuznetsova) wrote on 2014-08-07:

Probably it connects with https://bugs.launchpad.net/mos/+bug/1352203