If the rabbit password changes, clusters are not informed
Bug #1300554 reported by
Julian Edwards
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Gavin Panella | ||
Bug Description
The RabbitMQ password can be changed for many legitimate reasons. In this case, the cluster celery daemons are left high and dry and unable to connect to Rabbit.
The solution is to make the region send an update to the clusters when it knows the password changed. I don't yet know how we could detect that though, it may need to be an explicit admin action.
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in maas: | |
| milestone: | none → 14.10 |
| Changed in maas: | |
| milestone: | 1.6.0 → none |
| Changed in maas: | |
| assignee: | nobody → Gavin Panella (allenap) |
| status: | Triaged → Fix Committed |
| milestone: | none → 1.7.0 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
