User hostname suffix changes user call behavior
Bug #1171559 reported by
Ed Cranford
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Ed Cranford |
Bug Description
A call to users.get(username) with no hostname issues a call to /instances/
The client shouldn't be appending the hostname if it isn't provided.
Changed in reddwarf: | |
assignee: | nobody → Ed Cranford (ed--cranford) |
Changed in reddwarf: | |
status: | New → In Progress |
Changed in trove: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/26781 github. com/stackforge/ reddwarf/ commit/ f224dd5dec7ac47 9280fab59587fc6 5c028de42a
Committed: http://
Submitter: Jenkins
Branch: master
commit f224dd5dec7ac47 9280fab59587fc6 5c028de42a
Author: Ed Cranford <email address hidden>
Date: Thu Apr 11 14:41:16 2013 -0500
Fixes test in response to optional hostname fix
Several tests have had their behavior changed
with the client appending the default host.
With that new behavior reversed in the client,
some tests use a username that contains an @,
causing an ambiguous case for the API to parse.
Deliberately including the host in the tests
fixes this.
Fixes Bug #1171559
Change-Id: I967eb4b21d8ca3 e2c2721db6f362b 8dac2551346