marking keystone as invalid since we have a duplicate bug here: 1519580
and we now use JSON schema validation for our v3 calls
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribe
Closing stale bug. If this is still an issue please reopen.
** Changed in: cinder
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/120639
There are ongoing discussions on the mailing list right now about this.
I think it's not a bug per say (actually current Nova behavior is what's
asked for).
** Changed in: nova
Assignee: Aswad Rangnekar (aswad-r) => (unassigned)
** Changed in: nova
Status: Confirmed => Opinion
--
Yo
IMHO this is not a bug in Oslo, but a feature request. Please open a
blueprint against Oslo to track this work (I do agree that common code
to do validation is a good idea) Obviously there is some significant
discussion needed first, so I would also suggest sending something to
openstack-dev on t
Hi Dolph,
Should whitespace only role names be allowed? Please see attached
horizon screenshot where this could be confusing to a user.
** Attachment added: "blank role name"
https://bugs.launchpad.net/nova/+bug/1206396/+attachment/3770986/+files/role_whitespace.png
** Changed in: keystone
UTR against keystone directly (sounds like a bug between horizon and
keystoneclient?). Attempting to create a role with a single space as the
name behaves as expected (the name is stored correctly in the sql
driver, not as a null value).
POST http://localhost:35357/v3/roles
{"role": {"name": " "}}
6 matches
Mail list logo
