OpenStack DBaaS (Trove)

User hostname suffix changes user call behavior

Bug #1171559 reported by Ed Cranford on 2013-04-22

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack DBaaS (Trove)	Fix Released	Undecided	Ed Cranford	OpenStack DBaaS (Trove) 2013.2 "havana"

Bug Description

A call to users.get(username) with no hostname issues a call to /instances/<instanceid>/users/username@%. This causes 404s for calls that previously were fine, especially with usernames that have @ in them.
The client shouldn't be appending the hostname if it isn't provided.

Ed Cranford (ed--cranford) on 2013-04-22

Changed in reddwarf:
assignee:	nobody → Ed Cranford (ed--cranford)

OpenStack Infra (hudson-openstack) on 2013-04-22

Changed in reddwarf:
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2013-04-24: Fix merged to reddwarf (master)

Reviewed: https://review.openstack.org/26781
Committed: http://github.com/stackforge/reddwarf/commit/f224dd5dec7ac479280fab59587fc65c028de42a
Submitter: Jenkins
Branch: master

commit f224dd5dec7ac479280fab59587fc65c028de42a
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: I967eb4b21d8ca3e2c2721db6f362b8dac2551346