Add tests for deployment stop/reset and continue

Bug #1320452 reported by Aleksey Kasatkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Aleksey Kasatkin

Bug Description

Add system tests for the following sequences:

deployment - stop_deployment - deployment
deployment - reset_deployment - deployment

Now we don't have tests on deployment retry after stop/reset.

Related bug: https://launchpad.net/bugs/1319823

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

Related patch, which should be covered by these tests: https://review.openstack.org/#/c/93940/

Dima Shulyak (dshulyak)
tags: added: low-hanging-fruit
Revision history for this message
Dima Shulyak (dshulyak) wrote :

As i remember, the issue was with nailgun-astute communication, and i broke it actually.
We can ofcourse benefit from additional test coverage in nailgun, but maybe we should consider running this scenario in system tests?

Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

AFAIC, it will be more useful within system tests.

Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

Moreover, astute was changed to fix the problem, not nailgun. See https://launchpad.net/bugs/1319823, https://review.openstack.org/#/c/94163/

description: updated
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → Fuel QA Team (fuel-qa)
description: updated
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

actually we have covered by system tests next scenarios::
I.
1. Run provisioning task
2. Run deployment task (simple)
3. Stop deployment
4. Add one node
5. Run deployment (It is covered your first scenario)

II. 1.Deploy simple
     2. Stop deployment
     3.Reset settings
     4. Add 1 node with cinder role
      5. Re-deploy cluster
III
Scenario:
            1. Create cluster
            2. Add 1 node with controller role
            3. Add 1 node with compute role
            4. Deploy cluster
            5. Reset settings
            6. Update net
            7. Re-deploy cluster
            8. Run OSTF
IV
 Scenario:
            1. Create cluster
            2. Add 3 node with controller role
            3. Deploy cluster
            4. Stop deployment
            5. Reset settings
            6. Add 2 nodes with compute role
            7. Re-deploy cluster
            8. Run OSTF
As you can see our tests already covers your scenarios. So may be you want to say that we need add to this scenario some additional checks? if so, could you provide a liitle bit more details, please. If you decide that provided list of scenarios is enaugt - lets move this tas to complete/want' t fix :)|

Changed in fuel:
status: Confirmed → Incomplete
assignee: Fuel QA Team (fuel-qa) → Aleksey Kasatkin (alekseyk-ru)
Revision history for this message
Aleksey Kasatkin (alekseyk-ru) wrote :

AFAIC, list of scenarios provided is enough.

Changed in fuel:
status: Incomplete → Won't Fix
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.