Toggling admin_state_up has no effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Fix Released
|
High
|
Michael Johnson |
Bug Description
This was my setup - a single loadbalancer, one listener, one pool, and two members. `admin_state_up = False` on all of these resources.
===== Loadbalancer pglbutt-lb =====
{
"name": "pglbutt-lb",
"operating_
"id": "782ede0c-
"pools": "{\"id\": \"bef3be76-
"provider": "octavia",
"description": "",
"admin_
"tenant_id": "98a68f01476c4a
"provisioni
"vip_
"listeners": "{\"id\": \"0786e713-
"vip_address": "10.0.0.10",
"vip_port_id": "83168479-
}
==== Listener pglbutt-listener =====
{
"name": "pglbutt-listener",
"id": "0786e713-
"default_
"connection
"protocol_
"protocol": "HTTP",
"description": "",
"default_
"admin_
"loadbalanc
"tenant_id": "98a68f01476c4a
"sni_
}
===== Pool pglbutt-pool =====
{
"name": "pglbutt-pool",
"id": "bef3be76-
"members": "6b24a190-
"listeners": "{\"id\": \"0786e713-
"lb_algorithm": "ROUND_ROBIN",
"protocol": "HTTP",
"description": "",
"admin_
"loadbalanc
"tenant_id": "98a68f01476c4a
"session_
"healthmoni
}
==== Member pglbutt-2 =====
{
"id": "6b24a190-
"protocol_
"address": "10.0.0.13",
"tenant_id": "98a68f01476c4a
"subnet_id": "70fc37ca-
"admin_
"weight": 1,
"name": "pglbutt-2"
}
==== Member pglbutt-1 =====
{
"id": "ba471f88-
"protocol_
"address": "10.0.0.8",
"tenant_id": "98a68f01476c4a
"subnet_id": "70fc37ca-
"admin_
"weight": 1,
"name": "pglbutt-1"
}
In this case admin_state_up is false everywhere, but curling the loadbalancer vip still allows traffic through:
stack@
Hello, world (10.0.0.8)!
stack@
Hello, world (10.0.0.13)!
stack@
Hello, world (10.0.0.8)!
stack@
Hello, world (10.0.0.13)!
Changed in octavia: | |
status: | New → Incomplete |
status: | Incomplete → Triaged |
Changed in octavia: | |
assignee: | nobody → Michael Johnson (johnsom) |
I am seeing that admin-state- up=False does not work for loadbalancer and listener via the neutron client.
Pool and members do work.