[ostf] Murano test "Create and delete Murano environment" fails without any message when Murano service unavailable

Bug #1282533 reported by Anastasiia Naboikina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Anastasiia Naboikina

Bug Description

Steps to reproduce:
1. Deploy a cluster with Murano service.
2. Turn off Murano service.
3. Run OSTF test "Create and Delete Murano environment"

Expected result:
There is a descriptive message about unavailability of Murano service.

Acutal result:
Test failed without any message (see screenshot).
There are the following errors in OSTF logs:
CommunicationError: Error communicating with http://172.16.0.2:8082 [Errno 113] No route to host

fuel_plugin.ostf_adapter.nose_plugin.nose_storage_plugin: ERROR: fuel_health.tests.sanity.test_sanity_murano.MuranoSanityTests.test_create_and_delete_service
Traceback (most recent call last):
  File "/opt/fuel_plugins/ostf/lib/python2.6/site-packages/unittest2/case.py", line 340, in run
    testMethod()
  File "/opt/fuel_plugins/ostf/lib/python2.6/site-packages/fuel_health/tests/sanity/test_sanity_murano.py", line 43, in test_create_and_delete_service
    "ost1_test-Murano_env01")
  File "/opt/fuel_plugins/ostf/lib/python2.6/site-packages/fuel_health/common/test_mixins.py", line 192, in verify
    " Please refer to OpenStack logs for more details.")
  File "/opt/fuel_plugins/ostf/lib/python2.6/site-packages/unittest2/case.py", line 415, in fail
    raise self.failureException(msg)
AssertionError: Step 1 failed: Can't create environment. Murano API isn't available. Please refer to OpenStack logs for more details.

A check has to be added that verifies if Murano is available before launching the test.

Tags: ostf
Revision history for this message
Anastasiia Naboikina (anaboikina) wrote :
summary: - Murano test "Create and delete Murano environment" fails without any
- message when Murano service unavailable
+ [ostf] Murano test "Create and delete Murano environment" fails without
+ any message when Murano service unavailable
Changed in fuel:
status: New → Confirmed
assignee: nobody → Anastasiia Naboikina (anaboikina)
Mike Scherbakov (mihgen)
Changed in fuel:
milestone: none → 4.1
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-ostf (master)

Fix proposed to branch: master
Review: https://review.openstack.org/75128

Revision history for this message
Mike Scherbakov (mihgen) wrote :

Considering this as Medium (it doesn't affect functionality and OSTF provides right results, the only is that it doesn't provide information on WHY murano test case fails, when it truly not working). This is still highly-wanted in 4.1 bugfix.

Changed in fuel:
importance: High → Medium
Mike Scherbakov (mihgen)
Changed in fuel:
milestone: 4.1 → 5.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-ostf (master)

Reviewed: https://review.openstack.org/75128
Committed: https://git.openstack.org/cgit/stackforge/fuel-ostf/commit/?id=d3e410acb13c064b739af767d4e786625e44ef3b
Submitter: Jenkins
Branch: master

commit d3e410acb13c064b739af767d4e786625e44ef3b
Author: Anstasiia Naboikina <email address hidden>
Date: Thu Feb 20 20:31:41 2014 +0200

    Add tests failure when murano not available

    Added check that Murano service is available and
    self.fail when it`s not to setUp class for Murano
    tests. Added check to tearDown to prevent errors.

    Closes-bug: #1282533

    Change-Id: I901c5307417f33ee0873274b9391607388a03bb0

Changed in fuel:
status: In Progress → Fix Committed
Changed in fuel:
milestone: 5.0 → 4.1
tags: added: in progress
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

Verified on ISO #228

Revision: ba019bf15a9597a154e7c1d6ecc840614d21414c
origin/master

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

Other bug subscribers

Bug attachments

Remote bug watches

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