neutron cli puts the required parameters into option arguments group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Invalid
|
Low
|
Unassigned | ||
python-neutronclient |
Won't Fix
|
Undecided
|
Ryan Tidwell | ||
python-neutronclient (Ubuntu) |
Invalid
|
Wishlist
|
Yang Yu |
Bug Description
In neutron cli, there are many scenario like below, some parameters such as --peer-ip and --remote-as are defined as required ones, but they are put into optional arguments group. That is wrong.
usage: neutron bgp-peer-create [-h] [-f {json,shell,
Create a BGP Peer.
positional arguments:
NAME Name of the BGP peer to create.
optional arguments:
-h, --help show this help message and exit
--request-format {json}
--tenant-id TENANT_ID
--peer-ip PEER_IP_ADDRESS
--remote-as PEER_REMOTE_AS
--auth-type PEER_AUTH_TYPE
--password AUTH_PASSWORD
Changed in python-neutronclient (Ubuntu): | |
assignee: | nobody → Yang Yu (yuyangbj) |
Changed in python-neutronclient: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in openstack-manuals: | |
assignee: | nobody → iswarya vakati (v-iswarya) |
Changed in openstack-manuals: | |
assignee: | iswarya vakati (v-iswarya) → nobody |
Hi Yang,
Thanks for taking time to report this bug and making Ubuntu and OpenStack better. I'm going to target this bug at upstream python- neutronclient since it is not a package bug.
Thanks,
Corey