Test "Check application deployment in Murano environment with GLARE" fails due to timeout exceeded

Bug #1605847 reported by ElenaRossokhina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
MOS QA Team

Bug Description

Detailed bug description:
CI:
https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.services_ha/3/testReport/(root)/deploy_murano_ha_with_tun/
9.0 + snapshot #36
Steps to reproduce:
Deploy cluster in ha mode with Murano and Neutron VXLAN

        Scenario:
            1. Create cluster. Set install Murano option
            2. Add 3 node with controller role
            3. Add 1 nodes with compute role
            4. Deploy the cluster
            5. Verify Murano services
            6. Run OSTF
            7. Run OSTF Murano platform tests
Expected results:
All OSTF passed

Actual result:
The following tests have not succeeded, while they must have passed:
  - Check application deployment in Murano environment with GLARE (fuel_health.tests.tests_platform.test_murano_linux.MuranoDeployLinuxServicesTests.test_deploy_dummy_app_with_glare). Test status: failure, message: Time limit exceeded while waiting for deleting environment to finish. Please refer to OpenStack logs for more details.

Logs is available: https://drive.google.com/open?id=0B2ag_Bf-ShtTalZRWW5mSXhHOHc

Changed in fuel:
milestone: none → 9.1
assignee: nobody → Fuel QA Team (fuel-qa)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → MOS QA Team (mos-qa)
Revision history for this message
Victor Ryzhenkin (vryzhenkin) wrote :

It looks, that we should just increase timeout for the test. There is nothing criminal in murano logs and according to the logs:
<131>Jul 22 00:18:35 node-3 murano-api: 2016-07-22 00:18:35.798 30059 ERROR murano.utils [req-9ce29055-c937-45f3-8a40-44f5d520f033 ec7cf63d90dc4af6a88ec55b97eb819b 45fddd95b36f4c95990a038d3fc8d5e6 - - -] Environment with id 2d5346a99222485bac39be71df663628 not found
Murano env was removed successfully.
Let's increase environment delete timeout.

Revision history for this message
ElenaRossokhina (esolomina) wrote :

I have checked this test again - the case was observed only one time.

Revision history for this message
Victor Ryzhenkin (vryzhenkin) wrote :

This means, that you can't reproduce it? If yes, please, mark it as invalid. It can be caused by environment lags.

Revision history for this message
ElenaRossokhina (esolomina) wrote :

Victor, ok. We could reopen it later if the issue is displayed more often

Changed in fuel:
status: New → 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.