incorrect result of adding tags for network

Bug #1602150 reported by shihanzhang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Fix Released
Low
Unassigned

Bug Description

I add a empty tag to a network, neutron-server return incorrect result, the details is below:

neutronclient version: 4.2.0
neutron --debug tag-add --resource-type network --resource 9eb7f03f-aaf0-4079-9244-65200176c901 --tag ''
root@server201:~# neutron net-show 9eb7f03f-aaf0-4079-9244-65200176c901
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| availability_zone_hints | |
| availability_zones | |
| created_at | 2016-07-12T08:02:01 |
| description | |
| id | 9eb7f03f-aaf0-4079-9244-65200176c901 |
| ipv4_address_scope | |
| ipv6_address_scope | |
| mtu | 1450 |
| name | test |
| port_security_enabled | True |
| provider:network_type | vxlan |
| provider:physical_network | |
| provider:segmentation_id | 8 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tags | .json |
| tenant_id | 9e211e5ad3c0407aaf6c5803dc307c27 |
| updated_at | 2016-07-12T08:02:01 |
+---------------------------+--------------------------------------+

Changed in python-neutronclient:
assignee: nobody → shihanzhang (shihanzhang)
Revision history for this message
Brandon Logan (brandon-logan) wrote :

FYI: This is what the client is actually sending to the server:

DEBUG: keystoneauth.session REQ: curl -g -i -X PUT http://192.168.33.12:9696/v2.0/networks/80a98608-a814-4a28-91e9-aa6c99fe65ba/tags/.json -H "User-Agent: python-neutronclient" -H "Accept: application/json" -H "X-Auth-Token: {SHA1}4529f87d3b08a34dd027de34cfc3763f5767c5c1"
DEBUG: keystoneauth.session RESP: [201] Content-Type: application/json Content-Length: 4 X-Openstack-Request-Id: req-157ca980-4c25-4426-9ecc-b278dc3e5101 Date: Tue, 12 Jul 2016 18:50:50 GMT Connection: keep-alive

specifically:
curl -g -i -X PUT http://192.168.33.12:9696/v2.0/networks/80a98608-a814-4a28-91e9-aa6c99fe65ba/tags/.json

Changed in python-neutronclient:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-neutronclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/342536

Changed in python-neutronclient:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on python-neutronclient (master)

Change abandoned by shihanzhang (<email address hidden>) on branch: master
Review: https://review.openstack.org/342536

Revision history for this message
Akihiro Motoki (amotoki) wrote :

OSC network tag support is under development. We can fix this in neutron CLI side too.

Changed in python-neutronclient:
assignee: shihanzhang (shihanzhang) → nobody
status: In Progress → Confirmed
Akihiro Motoki (amotoki)
Changed in python-neutronclient:
importance: Undecided → Low
Akihiro Motoki (amotoki)
tags: added: low-hanging-fruit
Changed in python-neutronclient:
assignee: nobody → Benard Okolie (benokolie)
Revision history for this message
Benard Okolie (benokolie) wrote :

It looks like this problem has already been fixed in the latest version of python-neutronclient with https://review.openstack.org/#/c/396727/.

Can we go ahead and close this bug?

Changed in python-neutronclient:
assignee: Benard Okolie (benokolie) → nobody
Revision history for this message
Akihiro Motoki (amotoki) wrote :
Changed in python-neutronclient:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.