No indication if cluster controller is failing to connect
Bug #1066668 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Gavin Panella | ||
| 1.2 |
Fix Released
|
Critical
|
Julian Edwards | ||
Bug Description
At the moment, if something is misconfigured in a cluster controller, it spins endlessly (pausing 1 minute inbetween) trying to register itself with the region controller.
However, during all this time, it does not appear to be logging failure messages anywhere. I manually hacked the start_cluster_
Related branches
lp:~allenap/maas/cluster-worker-logging
- John A Meinel (community): Approve
- Raphaël Badin (community): Approve
-
Diff: 228 lines (+32/-55)9 files modifiedetc/celeryconfig_common.py (+4/-3)
etc/democeleryconfig.py (+1/-1)
etc/democeleryconfig_cluster.py (+2/-2)
src/provisioningserver/boot_images.py (+4/-1)
src/provisioningserver/dhcp/leases.py (+5/-1)
src/provisioningserver/logging.py (+0/-22)
src/provisioningserver/start_cluster_controller.py (+9/-20)
src/provisioningserver/tags.py (+6/-5)
src/provisioningserver/tests/test_start_cluster_controller.py (+1/-0)
lp:~julian-edwards/maas/backport-r1293
- Julian Edwards (community): Approve
-
Diff: 229 lines (+32/-55)9 files modifiedetc/celeryconfig_common.py (+4/-3)
etc/democeleryconfig.py (+1/-1)
etc/democeleryconfig_cluster.py (+2/-2)
src/provisioningserver/boot_images.py (+4/-1)
src/provisioningserver/dhcp/leases.py (+5/-1)
src/provisioningserver/logging.py (+0/-22)
src/provisioningserver/start_cluster_controller.py (+9/-20)
src/provisioningserver/tags.py (+6/-5)
src/provisioningserver/tests/test_start_cluster_controller.py (+1/-0)
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Gavin Panella (allenap) |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| tags: | added: notifications |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note that it does call 'log_error(e)' which calls task_logger.info(). However, task_logger does not seem to actually be connected to an output file at that point.