[10.0] [Swarm] Heat typical actions OSTF is failed

Bug #1654263 reported by Yury Tregubov
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Peter Razumovsky

Bug Description

For several last builds of mos 10.0 since about #1163 after fix of the https://bugs.launchpad.net/fuel/+bug/1590479 the other problem starts to appear.

On SWARM runs the OSTF "Typical stack actions: create, delete, show details, et" is failed after deploy. However env is seems to be operational.

Diagnostic snapshot is:
https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.services_ha/160/artifact/logs/fail_error_deploy_heat_ha-fuel-snapshot-2017-01-05_02-52-47.tar

The CI runs where the problem is seen are: https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.services_ha

======================================================================
FAIL: Deploy Heat cluster in HA mode
  ......................
  File "/home/jenkins/workspace/10.0.system_test.ubuntu.services_ha/core/helpers/log_helpers.py", line 204, in wrapped
    result = func(*args, **kwargs)
  File "/home/jenkins/workspace/10.0.system_test.ubuntu.services_ha/fuelweb_test/models/fuel_web_client.py", line 256, in assert_ostf_run_certain
    indent=1)))
AssertionError: The following tests have not succeeded, while they must have passed:
  - Typical stack actions: create, delete, show details, etc. (fuel_health.tests.tests_platform.test_heat.HeatSmokeTests.test_actions). Test status: error, message:

Changed in fuel:
milestone: none → 10.1
tags: added: swarm-fail
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

neutronclient.v2_0.client: DEBUG: DELETE call to neutron for https://public.fuel.local:9696/v2.0/subnets/7e7b1620-d428-49c2-9d4f-0d35e3724dfe.json used request id req-c567c16a-aac4-48e2-b805-db30d5939ac5
neutronclient.client: DEBUG: REQ: curl -i https://public.fuel.local:9696/v2.0/networks/4f3b7377-d852-449c-a676-3f678c7142f0.json -X DELETE -H "User-Agent: python-neutronclient" -H "X-Auth-Token: {SHA1}46a8637edce16ff28db006fa906c96fce62f344f"
neutronclient.client: DEBUG: RESP: 409 {'Date': 'Thu, 05 Jan 2017 02:52:45 GMT', 'Content-Length': '205', 'Connection': 'close', 'Content-Type': 'application/json; charset=UTF-8', 'X-Openstack-Request-Id': 'req-5018dcd5-ca1e-4d39-afa8-07dac470f94e'} {"NeutronError": {"message": "Unable to complete operation on network 4f3b7377-d852-449c-a676-3f678c7142f0. There are one or more ports still in use on the network.", "type": "NetworkInUse", "detail": ""}}
neutronclient.v2_0.client: DEBUG: Error message: {"NeutronError": {"message": "Unable to complete operation on network 4f3b7377-d852-449c-a676-3f678c7142f0. There are one or more ports still in use on the network.", "type": "NetworkInUse", "detail": ""}}
neutronclient.v2_0.client: DEBUG: DELETE call to neutron for https://public.fuel.local:9696/v2.0/networks/4f3b7377-d852-449c-a676-3f678c7142f0.json used request id req-5018dcd5-ca1e-4d39-afa8-07dac470f94e
fuel_plugin.ostf_adapter.nose_plugin.nose_storage_plugin: ERROR: fuel_health.tests.tests_platform.test_heat.HeatSmokeTests.test_actions
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 67, in testPartExecutor
    yield
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 601, in run
    testMethod()
  File "/usr/lib/python2.7/site-packages/fuel_health/tests/tests_platform/test_heat.py", line 243, in test_actions
    template, parameters=parameters
  File "/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py", line 180, in verify
    " Please refer to OpenStack logs for more details.")
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 666, in fail
    raise self.failureException(msg)
AssertionError: Step 2 failed: Stack was not created properly. Please refer to OpenStack logs for more details.

Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Oleg Bondarev (obondarev) wrote :

Original error from ostf log: http://paste.openstack.org/show/594418/

then ostf test starts to cleanup resources while heat stack is still being created -> hence we have conflicts when deleting neutron net. Need to investigate initial failure with heat

Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Fuel QA Team (fuel-qa)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → MOS QA Team (mos-qa)
Revision history for this message
Yury Tregubov (ytregubov) wrote :

Looks like that neutron network is not deleted during cleanup since it is sill used by instance that is created by heat stack. And the instance is missed in the cleanup for some reason.
But it seems to be not the source of the problem in this case.

Initial creation of the stack is failed:

2017-02-09 11:09:49 FAILURE Typical stack actions: create, delete, show details, etc. (fuel_health.tests.tests_platform.test_heat.HeatSmokeTests.test_actions) Stack was not created properly. Please refer to OpenStack logs for more details. File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 67, in testPartExecutor
    yield
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 601, in run
    testMethod()
  File "/usr/lib/python2.7/site-packages/fuel_health/tests/tests_platform/test_heat.py", line 243, in test_actions
    template, parameters=parameters
  File "/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py", line 180, in verify
    " Please refer to OpenStack logs for more details.")
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 666, in fail
    raise self.failureException(msg)
Step 2 failed: Stack was not created properly. Please refer to OpenStack logs for more details.

After that it is impossible to get the stack after creation with error: Unable to retrieve stack.
And it is impossible to delete that stack even if related instance and network are deleted.

Diagnostic snapshot with fresh reproduction is here: https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.services_ha/175/artifact/logs/fail_error_deploy_heat_ha-fuel-snapshot-2017-02-09_02-54-42.tar

Also feel free to ask me for env for reproduction.

Changed in fuel:
assignee: MOS QA Team (mos-qa) → Fuel Sustaining (fuel-sustaining-team)
tags: added: swarm-blocker
removed: swarm-fail
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → MOS Heat (mos-heat)
Changed in fuel:
assignee: MOS Heat (mos-heat) → Peter Razumovsky (prazumovsky)
Revision history for this message
Peter Razumovsky (prazumovsky) wrote :

Current investigation result:

1. Before [201] build heat tests failed.

2. [201] build image contains https://review.openstack.org/#/c/439653/ patch, which just disable all ceilometer and, suddenly, ALL heat tests, so skipped tests don't fail, of course.

3. After discovery of cases above, Anastasia Kuznetsova pushed patch on review, which enable heat tests and remove "mongo" role from it [1].

4. Patch has been merged, but have a lack with checking ceilometer service availability, so [216] build failed. But @akuznetsova pushed fix for this on review [2].

5. Also, ostf tests, manually started, complete (on1 reverted [216] snapshot).

Conclusion: if after [2] patch heat_ha tests will pass successfully, then I will close this bug as complete. Else continue investigation.

[1] https://review.openstack.org/#/c/448070/

[2] https://review.openstack.org/#/c/448116/

[201] https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.services_ha/201/

[216] https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.services_ha/216/

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Peter Razumovsky (prazumovsky) wrote :

As I said yesterday, I will close bug, if [217] build completes successful. [217] is green => I close this bug.

[217] https://product-ci.infra.mirantis.net/view/10.0_swarm/job/10.0.system_test.ubuntu.services_ha/217/

Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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