Cluster gets disconnected after error: provisioningserver.service_monitor.UnknownServiceError: 'maas-dhcpd' is unknown to upstart.
Bug #1457708 reported by
Ashley Lai
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
Bug Description
For the past few hours all deployments in prodstack hit with the 400 error. Please see the logs attached.
ERROR failed to bootstrap environment: cannot start bootstrap instance: gomaasapi: got error back from server: 400 BAD REQUEST ({"power_type": ["The cluster controller for this node is not responding; power type validation is not available.Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:22,838 [ERROR] oil_ci.juju.client: Calling "juju bootstrap" failed!
2015-05-22 01:01:22,838 [ERROR] oil_ci.cli: Deployment failed:
+ rc=1
+ echo 'Deployment returned: 1'
Related branches
lp://qastaging/~rvb/maas/packaging-bug-1457708
- Blake Rouse (community): Needs Fixing
- Gavin Panella (community): Approve
-
Diff: 27 lines (+6/-2)2 files modifieddebian/changelog (+3/-1)
debian/extras/99-maas-sudoers (+3/-1)
lp://qastaging/~rvb/maas/packaging-bug-1457708-2
- Blake Rouse (community): Approve
-
Diff: 25 lines (+3/-1)2 files modifieddebian/changelog (+1/-1)
debian/extras/99-maas-sudoers (+2/-0)
Revision history for this message
| Ashley Lai (alai) wrote | #1 |
| summary: |
- Prostack: all pipelines hit with 400 BAD REQUEST error + 1.8b7: all pipelines hit with 400 BAD REQUEST error |
Revision history for this message
| Raphaël Badin (rvb) wrote Re: 1.8b7: all pipelines hit with 400 BAD REQUEST error | #2 |
Revision history for this message
| Raphaël Badin (rvb) wrote | #3 |
| summary: |
- 1.8b7: all pipelines hit with 400 BAD REQUEST error + Cluster gets disconnected after error: + provisioningserver.service_monitor.UnknownServiceError: 'maas-dhcpd' is + unknown to upstart. |
Revision history for this message
| Raphaël Badin (rvb) wrote | #4 |
| Changed in maas: | |
| importance: | Undecided → Critical |
| status: | New → Triaged |
| assignee: | nobody → Raphaël Badin (rvb) |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| milestone: | none → 1.8.0 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #5 |
Revision history for this message
| Raphaël Badin (rvb) wrote | #6 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
At the time the problem happened, there is this in the regiond logs:
2015-05-22 01:01:21 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:21 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:21 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:21 [-] 127.0.0.1 - - [22/May/
2015-05-22 01:01:22 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:22 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:22 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-
2015-05-22 01:01:22 [maasserver] ERROR: Unable to get RPC connection for cluster 'OIL Cluster' (037c960b-