Recofigure image loading path for scenario tests

Bug #1393881 reported by Chris Hoge on 2014-11-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Medium
Matthew Treinish

Bug Description

After reviewing the scenario test options and code path at the Kilo Design Summit, we determined that the options related to Amazon images needed to be removed as they introduce a failure path:

aki_img_file
ami_img_file
ari_img_file

The `img_dir` option also needs to be removed in favor of using a full path for `img_file`.

Changed in tempest:
importance: Undecided → Medium
status: New → Confirmed
Jason Wong (wantwatering) wrote :

Which means scenario tests such as test_large_ops and test_encrypted_cinder_volumes won't prepare their own images any more?

Changed in tempest:
assignee: nobody → Emily Hugenbruch (ekhugen)

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

Changed in tempest:
status: Confirmed → In Progress
Matthew Treinish (treinish) wrote :

@Jason Wong sorry I missed your comment on this before. To answer your question, no the scenario tests will still upload their own images if they were before. All this bug is saying that the config options around this will be simplified significantly, instead of having 2 sets of of options to use either a single file image or the 3 file ec2 images and then having a non-obvious convoluted fallback logic in place between them. This will be simplified to just be the options for a single file image, additionally we'll stop using a split img_dir and img_file and just switch to a single option with a full path.

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

Changed in tempest:
assignee: Emily Hugenbruch (ekhugen) → Matthew Treinish (treinish)

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

Reviewed: https://review.openstack.org/267670
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=5d5e20a2ee4644b31207027cbe0c02d07bf11b5d
Submitter: Jenkins
Branch: master

commit 5d5e20a2ee4644b31207027cbe0c02d07bf11b5d
Author: Matthew Treinish <email address hidden>
Date: Thu Jan 14 10:54:30 2016 -0500

    Mark amazon image file config options deprecated

    This commit marks the 4 options used in the scenario section as
    deprecated. The behavior of these options and the other image file
    options in the scenario section have a very convoluted and difficult
    to understand. There is no reason for this complexity we should just
    have a single option to tell tempest where the image file is. As the
    first step in cleaning this up this marks the options which will be
    removed as deprecated to signal to users the future change here.

    Partial Bug: #1393881

    Change-Id: I8a6ee167384c8a2d17905db3a4061c06398980ad

Change abandoned by Emily Hugenbruch (<email address hidden>) on branch: master
Review: https://review.openstack.org/185174
Reason: Bug got fixed under another patch

Change abandoned by Matthew Treinish (<email address hidden>) on branch: master
Review: https://review.openstack.org/267679

chandan kumar (chkumar246) wrote :

Unassigning this bug as there is no activity from last 6 months. If you are still want to work on this bug, feel free to assign yourself.

Changed in tempest:
assignee: Matthew Treinish (treinish) → nobody
Changed in tempest:
assignee: nobody → Matthew Treinish (treinish)

Hi,

Is anybody working on this issue?

Thanks.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers