Timeout exceeded in OSTF while Murano was deploying Wordpress app

Bug #1467974 reported by Dennis Dmitriev on 2015-06-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Timur Nurlygayanov
Timur Nurlygayanov
Timur Nurlygayanov

Bug Description

1. Create new environment
2. Choose Neutron, GRE
3. Choose Ceph for volumes and Ceph for images
4. Choose Sahara
5. Choose Murano
6. Choose Ceilometer
7. Change "Ceph object replication factor" to 1 (instead 2)
8. Add 1 controller (2 CPU)
9. Add 1 compute (4 CPU, 12Gb RAM)
10. Add 1 ceph (2 CPU, 200Gb for ceph partitions)
11. Add 1 mongo
12. Deploy the environment
13. Verify networks
14. Run OSTF tests

Expected result: OSTF tests are passed

Actual result: OSTF test "Check that user can deploy WordPress app in Murano environment" failed with timeout while waiting for deployed Murano environment.

There is a 30 minutes of timeout, but environment was deployed in ~32 minutes.

Fix proposed to branch: stable/6.1
Review: https://review.openstack.org/194708

Changed in fuel:
assignee: MOS QA Team (mos-qa) → Dennis Dmitriev (ddmitriev)
status: New → In Progress

Hi Dennis, it is not enough to just increase the timeout to fix the issue.
The main issue here is that we are using QEMU hypervisor and in this case on one environment timeout in 2400 seconds will be enough and on the other environment this timeout will be not enough. And we don't want to have infinite timeout :)

Changed in fuel:
status: Confirmed → In Progress

Here is the link with fix for MOS 7.0:

Here is the link with fix for MOS 6.1:

Changed in fuel:
assignee: Timur Nurlygayanov (tnurlygayanov) → Dennis Dmitriev (ddmitriev)

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

commit 3e97178a28eaa2e83f4507d82e6837aefc50f9b0
Author: Dennis Dmitriev <email address hidden>
Date: Tue Jun 23 18:14:23 2015 +0300

    Improved resources validation for Murano OSTF tests

    We can see that sometimes Murano OSTF tests failed for different reasons,
    this commit allows to fix all of them.

    - Changed logic of validation of available resources. Now we will
      verify that we can successfully run required count of VMs on all
      available hypervisors
    - Increased timeout from 30 to 40 min for deployment of Murano env
    - Increased timeout from 10 to 30 sec for checking path availability
      of wordpress app
    - Increased timeout from 5 to 10 sec for deleting the environment
    - Added logging of steps that are performed by tests using
      self.verify() method
    - Changed configuration for default Murano OSTF flavor

    Co-Authored-By: Timur Nurlygayanov <email address hidden>

    Change-Id: I29cf3f38d651eae3654c42cd8f0e1c46869213bf

Changed in fuel:
status: In Progress → Fix Committed
Tatyanka (tatyana-leontovich) wrote :

verified on 60 iso

Change abandoned by tatyana-leontovich (<email address hidden>) on branch: stable/6.1
Review: https://review.openstack.org/194708

tags: added: area-ostf
removed: module-ostf
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers