| 2012-08-31 06:11:42 |
Jiajun Liu |
bug |
|
|
added bug |
| 2012-08-31 06:14:34 |
Jiajun Liu |
description |
policy check do not work properly for update_port operation in quantum v2 API.
For example, I want to check the fixed_ip of a port and I typed the following cmd:
$ quantum update-port 89b8d2aa-9d2a-4d79-a7d2-08362a435c73 --fixed_ip {"subnet_id": "3e3142c6-cc0f-49c2-bedb-9f6c1b23c801", "ip_address": "10.0.1.2"}
then policy_enforce got called with:
target = {'status': u'ACTIVE', 'network_id': u'c46727f3-8b02-4dd9-8295-171e2a91c4fa', u'port': {u'fixed_ip': [u'{subnet_id:', u'3e3142c6-cc0f-49c2-bedb-9f6c1b23c801,', u'ip_address:', u'10.0.1.2}']}, 'id': u'89b8d2aa-9d2a-4d79-a7d2-08362a435c73', 'tenant_id': u'251bd6bb546a4bd2a08b7e2b2907e18c'}
However, _is_attribute_explicitly_set will try to get 'fixed_ip' field on building match list which will always fail. This issue exists for all update_port operation because all the field need to update was packed in 'port' field of target. |
policy check do not work properly for update_port operation in quantum v2 API.
For example, I want to change the fixed_ip of a port and I typed the following cmd:
$ quantum update-port 89b8d2aa-9d2a-4d79-a7d2-08362a435c73 --fixed_ip {"subnet_id": "3e3142c6-cc0f-49c2-bedb-9f6c1b23c801", "ip_address": "10.0.1.2"}
then policy_enforce got called with:
action = 'update_port'
target = {'status': u'ACTIVE', 'network_id': u'c46727f3-8b02-4dd9-8295-171e2a91c4fa', u'port': {u'fixed_ip': [u'{subnet_id:', u'3e3142c6-cc0f-49c2-bedb-9f6c1b23c801,', u'ip_address:', u'10.0.1.2}']}, 'id': u'89b8d2aa-9d2a-4d79-a7d2-08362a435c73', 'tenant_id': u'251bd6bb546a4bd2a08b7e2b2907e18c'}
However, _is_attribute_explicitly_set will try to get 'fixed_ip' field on building match list which will always fail. This issue exists for all update_port operation because all the field need to update was packed in 'port' field of target. |
|
| 2012-08-31 06:14:58 |
Jiajun Liu |
description |
policy check do not work properly for update_port operation in quantum v2 API.
For example, I want to change the fixed_ip of a port and I typed the following cmd:
$ quantum update-port 89b8d2aa-9d2a-4d79-a7d2-08362a435c73 --fixed_ip {"subnet_id": "3e3142c6-cc0f-49c2-bedb-9f6c1b23c801", "ip_address": "10.0.1.2"}
then policy_enforce got called with:
action = 'update_port'
target = {'status': u'ACTIVE', 'network_id': u'c46727f3-8b02-4dd9-8295-171e2a91c4fa', u'port': {u'fixed_ip': [u'{subnet_id:', u'3e3142c6-cc0f-49c2-bedb-9f6c1b23c801,', u'ip_address:', u'10.0.1.2}']}, 'id': u'89b8d2aa-9d2a-4d79-a7d2-08362a435c73', 'tenant_id': u'251bd6bb546a4bd2a08b7e2b2907e18c'}
However, _is_attribute_explicitly_set will try to get 'fixed_ip' field on building match list which will always fail. This issue exists for all update_port operation because all the field need to update was packed in 'port' field of target. |
policy check do not work properly for update_port operation in quantum v2 API.
For example, I want to change the fixed_ip of a port and I typed the following cmd:
$ quantum update-port 89b8d2aa-9d2a-4d79-a7d2-08362a435c73 --fixed_ip {"subnet_id": "3e3142c6-cc0f-49c2-bedb-9f6c1b23c801", "ip_address": "10.0.1.2"}
then policy.enforce got called with:
action = 'update_port'
target = {'status': u'ACTIVE', 'network_id': u'c46727f3-8b02-4dd9-8295-171e2a91c4fa', u'port': {u'fixed_ip': [u'{subnet_id:', u'3e3142c6-cc0f-49c2-bedb-9f6c1b23c801,', u'ip_address:', u'10.0.1.2}']}, 'id': u'89b8d2aa-9d2a-4d79-a7d2-08362a435c73', 'tenant_id': u'251bd6bb546a4bd2a08b7e2b2907e18c'}
However, _is_attribute_explicitly_set will try to get 'fixed_ip' field on building match list which will always fail. This issue exists for all update_port operation because all the field need to update was packed in 'port' field of target. |
|
| 2012-08-31 06:15:47 |
Jiajun Liu |
description |
policy check do not work properly for update_port operation in quantum v2 API.
For example, I want to change the fixed_ip of a port and I typed the following cmd:
$ quantum update-port 89b8d2aa-9d2a-4d79-a7d2-08362a435c73 --fixed_ip {"subnet_id": "3e3142c6-cc0f-49c2-bedb-9f6c1b23c801", "ip_address": "10.0.1.2"}
then policy.enforce got called with:
action = 'update_port'
target = {'status': u'ACTIVE', 'network_id': u'c46727f3-8b02-4dd9-8295-171e2a91c4fa', u'port': {u'fixed_ip': [u'{subnet_id:', u'3e3142c6-cc0f-49c2-bedb-9f6c1b23c801,', u'ip_address:', u'10.0.1.2}']}, 'id': u'89b8d2aa-9d2a-4d79-a7d2-08362a435c73', 'tenant_id': u'251bd6bb546a4bd2a08b7e2b2907e18c'}
However, _is_attribute_explicitly_set will try to get 'fixed_ip' field on building match list which will always fail. This issue exists for all update_port operation because all the field need to update was packed in 'port' field of target. |
policy check do not work properly for update_port operation in quantum v2 API.
For example, I want to change the fixed_ip of a port and I typed the following cmd:
$ quantum update-port 89b8d2aa-9d2a-4d79-a7d2-08362a435c73 --fixed_ip {"subnet_id": "3e3142c6-cc0f-49c2-bedb-9f6c1b23c801", "ip_address": "10.0.1.2"}
then policy.enforce got called with:
action = 'update_port'
target = {'status': u'ACTIVE', 'network_id': u'c46727f3-8b02-4dd9-8295-171e2a91c4fa', u'port': {u'fixed_ip': [u'{subnet_id:', u'3e3142c6-cc0f-49c2-bedb-9f6c1b23c801,', u'ip_address:', u'10.0.1.2}']}, 'id': u'89b8d2aa-9d2a-4d79-a7d2-08362a435c73', 'tenant_id': u'251bd6bb546a4bd2a08b7e2b2907e18c'}
However, _is_attribute_explicitly_set will try to get 'fixed_ip' field on building match list which will always fail. This issue exists for all update_port operation because all the field need to be updated was packed in the 'port' field of target. |
|
| 2012-08-31 06:28:56 |
dan wendlandt |
quantum: assignee |
|
Salvatore Orlando (salvatore-orlando) |
|
| 2012-08-31 06:28:59 |
dan wendlandt |
quantum: milestone |
|
folsom-rc1 |
|
| 2012-08-31 06:29:50 |
dan wendlandt |
quantum: status |
New |
Confirmed |
|
| 2012-08-31 10:32:06 |
dan wendlandt |
quantum: assignee |
Salvatore Orlando (salvatore-orlando) |
ljjjustin (ljjjustin) |
|
| 2012-09-07 23:45:22 |
Salvatore Orlando |
quantum: importance |
Undecided |
Medium |
|
| 2012-09-07 23:45:24 |
Salvatore Orlando |
quantum: assignee |
ljjjustin (ljjjustin) |
Salvatore Orlando (salvatore-orlando) |
|
| 2012-09-07 23:49:21 |
OpenStack Infra |
quantum: status |
Confirmed |
In Progress |
|
| 2012-09-08 07:05:47 |
OpenStack Infra |
quantum: status |
In Progress |
Fix Committed |
|
| 2012-09-12 08:24:33 |
Thierry Carrez |
quantum: status |
Fix Committed |
Fix Released |
|
| 2012-09-27 15:13:46 |
Thierry Carrez |
quantum: milestone |
folsom-rc1 |
2012.2 |
|
