tempest subunit_describe_calls --verbose not working

Bug #1890060 reported by Doug Schveninger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Doug Schveninger

Bug Description

When subunit_describe_calls was converted from standard python CLI to cliff CLI framework the application argument --verbose boolean conflicts with the Cliff CLI --verbose number.

The application --verbose is to print request and response headers and body in stdout when output is sent to stdout. I would propose to change the --verbose application argument to --all.

Changed in tempest:
assignee: nobody → Doug Schveninger (ds6901)
status: New → In Progress
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.opendev.org/741810
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=6aa733e0f348bc9c3362d0a5c5b881cc77472968
Submitter: Zuul
Branch: master

commit 6aa733e0f348bc9c3362d0a5c5b881cc77472968
Author: Doug Schveninger <email address hidden>
Date: Sat Jul 18 11:03:21 2020 -0500

    Improve unit tests for subunit_describe_calls

    in order to enhance the cmd to support kubernetes url based
    routing over port based routing. Once this is merged I will
    submit another patch set to subunit_describe_calls to support
    -u --urls (Optional) The path to a JSON file describing the urls
      being used by different services. Note Can not be used with -p.

    Added test cases for cliff subprocess and found a bug with the
    -v. The standard -v --verbose of cliff conflict with this command
     so I changed the -v --verbose to -a --all for print header
    with printing to stdout I am also getting ready to add test cases
    for cliff subprocess support for different options. Bug #1890060

    Correct os join in test cases to avoid a conflict with
    https://review.opendev.org/#/c/683026

    Closes-bug: #1890060
    Change-Id: I9459db0dbeda721187ea5f4802c7453c2092dac3

Changed in tempest:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tempest 25.0.1

This issue was fixed in the openstack/tempest 25.0.1 release.

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.