bootstrap fails with failure to execute queries before end of atomic block
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Julian Edwards | ||
1.7 |
Fix Released
|
Critical
|
Julian Edwards |
Bug Description
We're hitting 500 INTERNAL SEVER ERROR during boostrap. There were no additional juju debug log error since this failed before instance was launched. We saw this with one pipeline deploy build:
Launching instance
WARNING picked arbitrary tools &{1.20.
ERROR bootstrap failed: cannot start bootstrap instance: gomaasapi: got error back from server: 500 INTERNAL SERVER ERROR (An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block.)
Bootstrap failed, destroying environment
ERROR cannot start bootstrap instance: gomaasapi: got error back from server: 500 INTERNAL SERVER ERROR (An error occurred in the current transaction. You can't execute queries until the end of the 'atomic' block.)
2014-10-29 15:12:51,033 [ERROR] oil_ci.juju.client: Calling "juju bootstrap" failed!
2014-10-29 15:12:51,034 [ERROR] oil_ci.cli: Deployment failed:
+ rc=1
+ echo 'Deployment returned: 1'
Deployment returned: 1
+ [[ 1 == 0 ]]
Related branches
- Graham Binns (community): Approve
- Newell Jensen (community): Approve
-
Diff: 128 lines (+50/-11)3 files modifiedsrc/maasserver/locks.py (+3/-0)
src/maasserver/models/staticipaddress.py (+22/-11)
src/maasserver/models/tests/test_staticipaddress.py (+25/-0)
- Christian Reis (community): Needs Information
- Julian Edwards (community): Approve
-
Diff: 128 lines (+50/-11)3 files modifiedsrc/maasserver/locks.py (+3/-0)
src/maasserver/models/staticipaddress.py (+22/-11)
src/maasserver/models/tests/test_staticipaddress.py (+25/-0)
- Julian Edwards (community): Approve
-
Diff: 2560 lines (+1719/-477) (has conflicts)17 files modifiedMakefile (+2/-2)
docs/changelog.rst (+937/-466)
src/maasserver/api/tests/test_node.py (+6/-1)
src/maasserver/forms_settings.py (+10/-0)
src/maasserver/models/config.py (+1/-0)
src/maasserver/models/node.py (+162/-0)
src/maasserver/models/tests/test_bootsource.py (+4/-0)
src/maasserver/models/tests/test_node.py (+417/-0)
src/maasserver/tests/test_bootresources.py (+19/-0)
src/maasserver/views/nodes.py (+5/-0)
src/maasserver/views/tests/test_nodes.py (+54/-0)
src/metadataserver/api.py (+17/-3)
src/metadataserver/models/commissioningscript.py (+22/-5)
src/metadataserver/models/tests/test_noderesults.py (+27/-0)
src/metadataserver/tests/test_api.py (+15/-0)
src/provisioningserver/rpc/boot_images.py (+14/-0)
src/provisioningserver/rpc/tests/test_boot_images.py (+7/-0)
Changed in juju-core: | |
status: | Incomplete → New |
tags: | added: bootstrap maas-provider |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in juju-core: | |
importance: | Critical → High |
milestone: | none → 1.21-alpha3 |
Changed in maas: | |
milestone: | none → 1.7.1 |
Changed in juju-core: | |
milestone: | 1.21-alpha3 → 1.21-beta1 |
Changed in maas: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 1.7.1 → none |
no longer affects: | juju-core |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Larry, are you able to attach the logs from MAAS? /var/log/maas/*.log and /var/log/ apache2/ error.log are the most useful.