neutron --version 2.4.0 usage: neutron net-create [-h] [-f {shell,table,value}] [-c COLUMN] [--max-width <integer>] [--prefix PREFIX] [--request-format {json,xml}] [--tenant-id TENANT_ID] [--admin-state-down] [--shared] [--provider:network_type <network_type>] [--provider:physical_network <physical_network_name>] [--provider:segmentation_id <segmentation_id>] [--vlan-transparent {True,False}] NAME Create a network for a given tenant. positional arguments: NAME Name of network to create. optional arguments: -h, --help show this help message and exit --request-format {json,xml} The XML or JSON request format. --tenant-id TENANT_ID The owner tenant ID. --admin-state-down Set admin state up to false. --shared Set the network as shared. --provider:network_type <network_type> The physical mechanism by which the virtual network is implemented. --provider:physical_network <physical_network_name> Name of the physical network over which the virtual network is implemented. --provider:segmentation_id <segmentation_id> VLAN ID for VLAN networks or tunnel-id for GRE/VXLAN networks. --vlan-transparent {True,False} Create a vlan transparent network. output formatters: output formatter options -f {shell,table,value}, --format {shell,table,value} the output format, defaults to table -c COLUMN, --column COLUMN specify the column(s) to include, can be repeated table formatter: --max-width <integer> Maximum display width, 0 to disable shell formatter: a format a UNIX shell can parse (variable="value") --prefix PREFIX add a prefix to all variable names
So this is a somewhat-duplicate bugzilla of [1]. Long story short is that nmagnezi tried to fix this issue, but the fix was soon reverted because it breaks backward compatibility, since the original addition of router:external was somewhat of a special case (it used the extra argument mechanism of argparse, unlike the rest of the arguments) and further attempts to fix this issue are still ongoing upstream [2]. See [3] on the ongoing upstream discussions about this issue. TL;DR: The current implementation reduces user experience, upstream is aware, they are trying to fix this themselves. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1221327 [2]: https://review.openstack.org/#/c/137279/ [3]: https://bugs.launchpad.net/python-neutronclient/+bug/1237820/comments/6
No need to track this downstream.