python-neutronclient

Client expects specific ordering of arguments

Bug #1047617 reported by Sumit Naiksatam
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Invalid
Undecided
Unassigned

Bug Description

I tried doing this and got an error:

stack@d5:~/devstack$ quantum --debug net-create --tenant_id 1c6c41e329764d89993a3f92149198a0 --provider:network_type flat flat_net --shared True
usage: quantum net-create [-h] [-f {shell,table}] [-c COLUMN]
                          [--variable VARIABLE] [--prefix PREFIX]
                          [--request-format {json,xml}]
                          [--tenant-id tenant-id] [--admin-state-down]
                          name ...
quantum net-create: error: unrecognized arguments: --provider:network_type

Then I changed ordering of the args, and it worked:

stack@d5:~/devstack$ quantum --debug net-create --tenant_id 1c6c41e329764d89993a3f92149198a0 flat_net --provider:network_type flat --shared True
Created a new network:
...

See original description
Sumit Naiksatam (snaiksat)
description: updated
Revision history for this message
dan wendlandt (danwent) wrote :

Adding Yong. My understanding is that this is expected (though certainly tricky) behavior with cliff. Yong, can you comment?

Revision history for this message
yong sheng gong (gongysh) wrote :

quantum --debug net-create --tenant_id 1c6c41e329764d89993a3f92149198a0 flat_net --provider:network_type flat --shared True

the provider:network_type is one customized option so it should be put after positional arguments.

Changed in python-quantumclient:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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