`frontend` service not changing `default_backend` on hook configuration
Bug #1437008 reported by
Brandon Clark
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
haproxy (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
When applying the following code:
```
relation-set "services=[
{'server_options': ['maxconn 100', 'cookie S{i} check'], 'service_name': 'mindproject', 'servers': [['mindproject', '${host}', '${port}', '']], 'service_options': ['mode http', 'balance leastconn', 'cookie SRVNAME insert', 'option httpchk GET / HTTP/1.0']}]"
```
Default yaml service name remains after configuration change hook:
```
frontend mind-proxy
default_backend haproxy_service
```
Should be changed to after configuration change hook:
```
frontend mind-proxy
default_backend mindproject
```
summary: |
- `frontend` service not changing `use_default` on hook configuration + `frontend` service not changing `default_backend` on hook configuration |
To post a comment you must log in.