network will fail to create when more than one option is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Version
=======
Grizzly/
Description
===========
network creation will fail to create when -- name is not used with additional parameters
1. create network with only tenant ID and name - it works ,
if using --name < name > it will fails
( neutron net-create --tenant-id < ID > <network name > )
2. create network with tenant ID , shared option & name - it will fail
neutron net-create --tenant-id < ID > --shared True <network name >
3. create network with tenant ID , shared option & -- name < name> - will pass
neutron net-create --tenant-id < ID > --shared True --name <network name >
--name should not be a MUST when using other options
Example:
[root@puma04 ~(keystone_admin)]# neutron net-create --tenant-id e91cdd9e867b490
Created a new network:
+------
| Field | Value |
+------
| admin_state_up | True |
| id | 18c78edf-
| name | ofer1 |
| provider:
| provider:
| provider:
| shared | True |
| status | ACTIVE |
| subnets | |
| tenant_id | e91cdd9e867b490
+------
[root@puma04 ~(keystone_admin)]# neutron net-create --tenant-id e91cdd9e867b490
Invalid values_specs ofer2
[root@puma04 ~(keystone_admin)]#
since --name is not a must , ofer2 should work
Parameter '--shared' doesn't have argumentsю In the example #2 word 'True' is treated as name and word 'ofer2' is left unmatched causing error message.