Queries with unintentional fragment identifier part in test_volumes_negative module

Bug #1545407 reported by Eyal Posener
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Undecided
Ghanshyam Mann

Bug Description

The following tests, has the hash tag in one of the queries parameter, which splits the url to a url + fragment identifier part.
Some WSGI backends (such as uwsgi) might cut this part of the url, and pass it in a different environment variable.

The tests are:
1. test_get_invalid_volume_id which results in an HTTP GET on .../volumes/#$%%&^&^
2. test_delete_invalid_volume_id which results in an HTTP DELETE on .../volumes/!@#$%^&*()

The hash tag should be removed from the requested ID.

Eyal Posener (eyal-6)
Changed in tempest:
assignee: nobody → Eyal Posener (eyal-6)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

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

Changed in tempest:
assignee: Eyal Posener (eyal-6) → Ghanshyam Mann (ghanshyammann)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/419311
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=9e294c4b347ddefacec54136354d7762eefb0af4
Submitter: Jenkins
Branch: master

commit 9e294c4b347ddefacec54136354d7762eefb0af4
Author: ghanshyam <email address hidden>
Date: Thu Jan 12 06:52:41 2017 +0000

    Use invalid id with rand string instead of special char

    Many negative tests use invalid id with combination of special char
    like '#$%%&^&^'.
    It has the hash tag which splits the url to a url + fragment identifier part.
    Some WSGI backends (such as uwsgi) might cut this part of the url,
    and pass it in a different environment variable.

    Change-Id: Id69baf8d364f31e6fa745929fea890652d7ee118
    Closes-bug: #1545407

Changed in tempest:
status: In Progress → 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.