Neutron network tags should not be empty string

[shihanzhang]

Now neutron network tags can be empty string, but I think there is no use case for a empty string tag, so we should add a check for tags.

root@server201:~# neutron tag-add --resource-type network --resource test --tag 'test_tag'
root@server201:~# neutron tag-add --resource-type network --resource test --tag ' '
root@server201:~# neutron net-show test
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| availability_zone_hints | |
| availability_zones | |
| created_at | 2016-07-15T01:45:51 |
| description | |
| id | f1060382-c7fa-43d5-a214-e8525184e7f0 |
| ipv4_address_scope | |
| ipv6_address_scope | |
| mtu | 1450 |
| name | test |
| port_security_enabled | True |
| provider:network_type | vxlan |
| provider:physical_network | |
| provider:segmentation_id | 26 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tags | |
| | test_tag |
| tenant_id | 9e211e5ad3c0407aaf6c5803dc307c27 |
| updated_at | 2016-07-15T01:45:51 |
+---------------------------+--------------------------------------+

[Tristan Cacqueray (tristan-cacqueray)]

Is there a reason why this has been switched to Public Security?

[Jeremy Stanley (fungi)]

This looks like it was probably switched from Public to Public Security on accident, so I'm setting it back to Public now.

In the future, if switching a bug from Public to Public Security (indicating that it represents a report of a suspected security vulnerability), please accompany that with an explanation of the security risks represented... ideally along with a reasonable attack scenario.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-neutronclient 6.3.0 release.

[M V P Nitesh (m-nitesh)]

Fixed by this patch https://review.openstack.org/#/c/446451/