router-interface-delete command has incorrect help

Bug #1702876 reported by George Shuklin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Won't Fix
Low
Brian Haley

Bug Description

router-interface-delete says it need router and INTERFACE, while command itself requires subnet.

usage: neutron router-interface-delete [-h] [--request-format {json}]
                                       ROUTER INTERFACE

neutron router-interface-delete a88edee2-f4e0-47d1-977a-f0714c305fd6 73417bb1-74ac-4182-ab4d-53510b72aa10
Unable to find subnet with name or id '73417bb1-74ac-4182-ab4d-53510b72aa10'

description: updated
Changed in python-neutronclient:
status: New → Confirmed
Changed in python-neutronclient:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-neutronclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/481658

Changed in python-neutronclient:
assignee: nobody → Brian Haley (brian-haley)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on python-neutronclient (master)

Change abandoned by Brian Haley (<email address hidden>) on branch: master
Review: https://review.openstack.org/481658

Revision history for this message
Brian Haley (brian-haley) wrote :

The INTERFACE name was used to be generic for subnet or port, so I guess this will stay as it is.

Changed in python-neutronclient:
status: In Progress → Won't Fix
Revision history for this message
Akihiro Motoki (amotoki) wrote :

The correct format is (SUBNET|subnet=SUBNET|port=PORT). INTERFACE is used as a compromise.
One idea is to change INTERFACE to (SUBNET|subnet=SUBNET|port=PORT).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.