[Yahoo-eng-team] [Bug 1615010] [NEW] lbaas member update accept --admin-state-up not --admin-state-down

Public bug reported: This is found at Kilo and Mitaka releases. --admin-state-down argument should be --admin-state-up I think this is not lbaas issue, but neutron CLI. $ ​neutron help lbaas-member-update usage: neutron lbaas-member-update [-h] [--request-format {json}]

[Yahoo-eng-team] [Bug 1611054] [NEW] mitaka release tags + tags-any causing internal server error

Public bug reported: Internal server error when query neutron network resources using --tags and tags-any combination. This is found at Mitaka release. stack@falcon-devstack ~ $ ​net-list -c id -c name --tenant-id f900b2f993234d31b450ca58d0cae025 -c tags

[Yahoo-eng-team] [Bug 1606659] [NEW] add-tag Normal response code is 200, not 201

Public bug reported: This is found at stable/mitaka release According to networking API v2.0 extensions:

[Yahoo-eng-team] [Bug 1594419] Re: lbaas loadbalancers statuses command failed on stable/liberty release

** Changed in: neutron Status: New => Invalid ** Changed in: neutron-lbaas (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1594419 Title:

[Yahoo-eng-team] [Bug 1594969] Re: stable/liberty lbaas http package not forwarded

comment at ovs_integration_bridge was inserted to lbaas config as it is, and not removed by lbaas agent which causing problems. ovs_integration_bridge = test-switch # nix-managed after remove the comment, packets are forwarded. Please close the bug. ** Changed in: neutron Status: New

[Yahoo-eng-team] [Bug 1594969] [NEW] stable/liberty lbaas http package not forwarded

Public bug reported: The latest neutron-lbaas stable/liberty repo, the loadbalancer VIP will not forward http packets to its pool members. http to pool members are OK, but http to loadbalancer VIP failed. Look at the VIP's port security-group, and it is correctly wired to the security-group-id.

[Yahoo-eng-team] [Bug 1585373] Re: qos-policy update without specify --shared causing it change to default False

same is true at policy creation time: nicira@newton-devstack:~$ neutron qos-policy-create --description="3k bw-limiter" --shared bw-limiter Created a new policy: +-+--+ | Field | Value|

[Yahoo-eng-team] [Bug 1585373] [NEW] qos-policy update without specify --shared causing it change to default False

Public bug reported: update policy 3k-bm-limiter as shared policy. update policy 3k-bm-limiter with only name field, causing default field shared=False being used. Here is the console log: nicira@newton-devstack:~$ neutron qos-policy-show 3k-bm-limiter

[Yahoo-eng-team] [Bug 1571097] [NEW] unable to delete lbaasv2 health monitor if its listener deleted

Public bug reported: problem is in Kilo neutron-lbaas branch. monitor is attached a pool. When pool and listener were deleted, not error reported that there is a health-monitor associated to pool. If all lbaas resoruces except health-monitor were deleted, health monitor can not be deleted.