There is no way to get UUID of a verification after it is created by "rally verify start" or "rally verify import_results" when --no-use is set

Bug #1587034 reported by Arata Notsu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rally
Fix Released
Undecided
Unassigned

Bug Description

If remove --no-use, the command prints a line "Verification UUID: <UUID>". So we can get UUID by grep or something. But with --no-use, no output like that so we cannot get UUID. Though we can search output of "rally verify list", this method is not so reliable in a situation where multiple verifications are running at a time.

Although one can easily workaround this by removing --no-use, it is an unreasonable restriction that should be removed.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to rally (master)

Reviewed: https://review.openstack.org/321381
Committed: https://git.openstack.org/cgit/openstack/rally/commit/?id=051a8c1c6fc9d959d50eea2d78dff9dcf74ec3c2
Submitter: Jenkins
Branch: master

commit 051a8c1c6fc9d959d50eea2d78dff9dcf74ec3c2
Author: Arata Notsu <email address hidden>
Date: Thu May 26 15:15:59 2016 +0900

    verify: start and import_results always print uuid

    Previously UUID of verifications that ware created by these commands
    with --no-use were not printed to stdout. It unnecessarily force
    users to stop using --no-use or to search the UUID in rally.log or
    in "rally verify list".

    With this change, a line "Verification UUID: <UUID>" will always
    appear in output of these command, regardless of weather if --no-use
    is specified. It allows users to extract UUID by a relatively simple
    filter such as "| grep -Po '(?<=^Verification UUID: ).*$'".

    Closes-bug: 1587034
    Change-Id: I4afbaf82472068ccf9b9c074d1d94a36fcbf246a

Changed in rally:
status: New → Fix Released
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.