Possible race condition when enabling TLS
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.4 |
Won't Fix
|
Low
|
Unassigned | |||
3.5 |
Won't Fix
|
Low
|
Unassigned | |||
3.6 |
Triaged
|
Low
|
Unassigned |
Bug Description
When MAAS CLI is used to configure TLS, it updates configuration in the database. After database values are changed, trigger will raise NOTIFY event, and all regiond services will handle it (using PostgreSQL LISTEN). Once handled, regiond service will render correct nginx config file and restart nginx.
There is a chance when regiond might miss that event:
1. regiond is starting. On start it reads existing config
*it takes some time to start up all the services
2. CLI used to configure TLS. DB values are updated and NOTIFY executed.
* regiond is not yet in the state where it "subscribed" to events with LISTEN command.
Possible workarounds:
1. Ensure that regiond is fully started and retry CLI command
2. Restart MAAS. It will pick up new values on start.
Related branches
- MAAS Lander: Approve
- Anton Troyanov: Approve
-
Diff: 13 lines (+2/-0)1 file modifiedsystemtests/fixtures.py (+2/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: bug-council |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
*** note to bug council *** @troyanov would like to discuss this with the bug council when they meet.