[Fuel-OSTF] 'assert' in test.py is needless

Bug #1461091 reported by Oleksandr Kyrylchuk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Wishlist
Timur Nurlygayanov

Bug Description

In file test.py, there's such block:

https://github.com/stackforge/fuel-ostf/blob/master/fuel_health/test.py#L84-L86

In fact, this block does nothing useful (OSTF tests work fine even after commenting a line with 'assert').
Also, this assertion causes critical problems for Cloudvalidation Project, where such assertion provokes crash while trying to run a test suite.

So, there can be a reason of removing this assertion from test.py file.

Changed in fuel:
assignee: nobody → Fuel QA Team (fuel-qa)
milestone: none → 7.0
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

does not affect ostf at all, just code clean up, so move to the wishlist

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → MOS QA Team (mos-qa)
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Sebastian Kalinowski (prmtl) wrote :

I'm tempted to make it as Invalid/Wont Fix since there is a comment explaining the need of this assert. I would rather consider fixing bug on Cloudvalidation Project.

Please describe what is exactly wrong and example of the issue.

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Oleksandr Kyrylchuk (okyrylchuk) wrote :

@prmtl: Generally speaking, you're right. Let me explain the situation.

In Cloudvalidation Project we implemented an Adapter for OSTF tests which is more flexible than the one from OSTF project (it does not require nailgun for running the tests). For this reason we needed just to register some additional options, but ran into the specific features in fuel-ostf. For now we have a workable solution except the problem of 'assert' mentioned in topic. With this assertion commented, we ran OSTF against MOS 6.X in Fuel Dashboard and against devstack with our Adapter: both worked fine. It seems that such simple fix should not reduce stability of Fuel OSTF, but it would enable running OSTF tests against almost any Openstack cloud.

@tatyana-leontovich: Sure, from the point of OSTF itself it's rather 'nice to have'.

Changed in fuel:
assignee: MOS QA Team (mos-qa) → Timur Nurlygayanov (tnurlygayanov)
status: Incomplete → Invalid
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Timur why do we set invalid here? Is it stop affect @Oleksander?

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Tatyana, we discussed the issue and looks like it is not bug in OSTF itself. Of course we can change this part of code, I know the right way and will prepare the fix.

Changed in fuel:
status: Invalid → Confirmed
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/200576

Changed in fuel:
status: Confirmed → In Progress
Changed in fuel:
milestone: 7.0 → 8.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-ostf (master)

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

Dmitry Pyzhov (dpyzhov)
tags: added: tech-debt
Changed in fuel:
status: In Progress → Confirmed
Dmitry Pyzhov (dpyzhov)
tags: added: area-qa
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

I'm tempted to make it as Invalid/Wont Fix since there is a comment explaining the need of this assert. I would rather consider fixing bug on Cloudvalidation Project.

Please describe what is exactly wrong and example of the issue.

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