LBaaS V2 - LB Update --admin-state-up does not need value specified

Bug #1549017 reported by Bhaargavi Natarajan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Invalid
Undecided
Unassigned

Bug Description

Using LBaaS V2 CLI command to update Loadbalancer, it appears that when changing admin-state-up from FALSE to TRUE, the attribute is not required. If no value is specified, True is taken by default.

For example:

 neutron lbaas-loadbalancer-update Lb2 --admin-state-up

is the same as:

 neutron lbaas-loadbalancer-update Lb2 --admin-state-up TRUE.

Tags: lbaas v2
Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :

It's not a bug. Excerpt from documentation:

"Some attributes receive default values if you omit them from the request:

admin_state_up. Default is true.

name. Default is an empty string.

description. Default is an empty string."

http://developer.openstack.org/api-ref-networking-v2-ext.html#createLoadBalancerv2

Changed in python-neutronclient:
status: New → Invalid
Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :

Added bug for openstack-api-site to update documentation with appropriate information: https://bugs.launchpad.net/openstack-api-site/+bug/1549343

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.