LBAAS HM: 404 within a range of allowed status codes, but still instance removed from the pool

Bug #1580115 reported by Slobodan Blatnjak
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.21.x
New
High
Rudra Rugge
Trunk
New
High
Rudra Rugge

Bug Description

When using a range (200-500) for allowed status codes in the lbaas monitor a 404 response removes the instance from the pool.
Setting the status code specifically to 404 does work. (Version 2.21-102)

neutron lb-healthmonitor-create --help
--expected-codes EXPECTED_CODES
                        The list of HTTP status codes expected in response
                        from the member to declare it healthy. This attribute
                        can contain one value, or a list of values separated
                        by comma, or a range of values (e.g. "200-299"). If
                        this attribute is not specified, it defaults to "200".

Please let me know if you need lb-healthmonitor-show or any other output.

Tags: lbaas ebay
information type: Proprietary → Public
Jeba Paulaiyan (jebap)
tags: added: lbaas
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.