yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #37311
[Bug 1489197] [NEW] Flavor service profiles map lacks tenant_id
Public bug reported:
The neutron v2 base.py auto populates a 'tenant_id' attribute on calls
if the attribute is not passed, pulling from the context.
This causes a POST to create a flavor service binding to fail when verifying attributes, as currently the tenant_id is not
part of the expected attribute map.
curl -g -i -X POST http://192.168.181.169:9696/v2.0/flavors/e38b4b6d-
872e-4656-b7bc-70e15455ee46/service_profiles.json -H "User-Agent:
python-neutronclient" -H "Content-Type: application/json" -H "Accept:
application/json" -H "X-Auth-Token: <AnAuthToken>" -d
'{"service_profile": {"id": "7fd54b73-6bf6-4fc8-9999-0045a808eec2"}}'
RESP BODY: {"NeutronError": {"message": "Unrecognized attribute(s)
'tenant_id'", "type": "HTTPBadRequest", "detail": ""}}
The solution, used by folks like QOS, is to add the tenant_id as a
common field to the attribute map.
** Affects: neutron
Importance: Undecided
Assignee: James Arendt (james-arendt-7)
Status: New
** Changed in: neutron
Assignee: (unassigned) => James Arendt (james-arendt-7)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1489197
Title:
Flavor service profiles map lacks tenant_id
Status in neutron:
New
Bug description:
The neutron v2 base.py auto populates a 'tenant_id' attribute on calls
if the attribute is not passed, pulling from the context.
This causes a POST to create a flavor service binding to fail when verifying attributes, as currently the tenant_id is not
part of the expected attribute map.
curl -g -i -X POST http://192.168.181.169:9696/v2.0/flavors/e38b4b6d-
872e-4656-b7bc-70e15455ee46/service_profiles.json -H "User-Agent:
python-neutronclient" -H "Content-Type: application/json" -H "Accept:
application/json" -H "X-Auth-Token: <AnAuthToken>" -d
'{"service_profile": {"id": "7fd54b73-6bf6-4fc8-9999-0045a808eec2"}}'
RESP BODY: {"NeutronError": {"message": "Unrecognized attribute(s)
'tenant_id'", "type": "HTTPBadRequest", "detail": ""}}
The solution, used by folks like QOS, is to add the tenant_id as a
common field to the attribute map.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1489197/+subscriptions
Follow ups