POST to containes resource gives http 400 when name is None
Bug #1354767 reported by
Steve Heyman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Barbican |
Fix Released
|
Medium
|
Juan Antonio Osorio Robles |
Bug Description
POST to containers resource to create a container fails with HTTP 400 when name is None.
API documentation says name is optional. Passing in a blank for name is acceptable and results in the expect HTTP 201. However, passing name as None causes the 400 error....the json schema validation fails.
Failing test is test_create_
Changed in barbican: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in barbican: | |
milestone: | none → kilo-1 |
Changed in barbican: | |
milestone: | kilo-1 → none |
Changed in barbican: | |
assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
Changed in barbican: | |
status: | Confirmed → In Progress |
Changed in barbican: | |
milestone: | none → kilo-1 |
status: | Fix Committed → Fix Released |
Changed in barbican: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
I can't seem to replicate this manually...
http:// i.imgur. com/8avoQfH. png
In this example, I didn't pass a name, but the container was created successfully.
http:// i.imgur. com/GlbhTCn. png