Incorrect stanza in haproxy.cfg after the redeployment of the related application
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Graylog Charm |
New
|
Low
|
Unassigned | ||
| charm-haproxy |
New
|
Undecided
|
Unassigned | ||
Bug Description
Charm revision: 66 (latest/stable)
Series: focal
charm-graylog was related to haproxy:
graylog:website <-> graylog-
with SSL cert and key configured on haproxy.
After the redeployment of 3 graylog units (remove-unit x3, add-unit x3), haproxy charm started generating an incorrect haproxy.cfg.
No other configs or relations have been changed in the meanwhile.
Correct haproxy.cfg before (redacted confidential information): [0]
Incorrect haproxy.cfg after (redacted confidential information): [1]
juju show-unit output: [2]
Things that we tried:
- re-creating the relation between haproxy and graylog - no luck
- wiping peer relation data on graylog-haproxy (where this bad 82 port config shows up) - no luck
- removed and re-added ssl_{cert,key} config in haproxy - no change at all
- remove unit, full redeployment of the VM, re-add unit - ended up with the same state (port 82)
- removed application, full redeployment of the VM, re-added the application - no luck, port 82 still, port 443 missing
[0] https:/
[1] https:/
[2] https:/
| Przemyslaw Lal (przemeklal) wrote | #1 |
| summary: |
- Iincorrect stanza in haproxy.cfg after the redeployment of the related + Incorrect stanza in haproxy.cfg after the redeployment of the related application |
| tags: | added: bseng-1191 |
| tags: | added: sts |
| Seyeong Kim (seyeongkim) wrote | #2 |
| Changed in charm-graylog: | |
| importance: | Undecided → Low |
| Seyeong Kim (seyeongkim) wrote | #3 |
As a workaround, I just placed the correct config and locked it with `chattr +i`. The unit is blocked in the `maintenance idle` state but at least the app is reachable.