yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32594
[Bug 1451399] Re: subnet-create arguments order is too strict (not backward compatibility)
I believe cidr should go last per command help, isn't it?
** Project changed: neutron => python-neutronclient
** Changed in: python-neutronclient
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1451399
Title:
subnet-create arguments order is too strict (not backward
compatibility)
Status in Python client library for Neutron:
Incomplete
Bug description:
Changing arguments order cause CLI error:
[root@puma14 ~(keystone_admin)]# neutron subnet-create public --gateway 10.35.178.254 10.35.178.0/24 --name public_subnet
Invalid values_specs 10.35.178.0/24
Changing order:
[root@puma14 ~(keystone_admin)]# neutron subnet-create --gateway 10.35.178.254 --name public_subnet public 10.35.178.0/24
Created a new subnet:
+-------------------+--------------------------------------------------+
| Field | Value |
+-------------------+--------------------------------------------------+
| allocation_pools | {"start": "10.35.178.1", "end": "10.35.178.253"} |
| cidr | 10.35.178.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 10.35.178.254 |
| host_routes | |
| id | 19593f99-b13c-4624-9755-983d7406cb47 |
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | public_subnet |
| network_id | df7af5c2-c84b-4991-b370-f8a854c29a80 |
| subnetpool_id | |
| tenant_id | 7e8736e9aba546e98be4a71a92d67a77 |
+-------------------+--------------------------------------------------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1451399/+subscriptions
References