Restarting image import leaves boot-resources empty (selection is made but not saved)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse | ||
2.1 |
Fix Released
|
High
|
Blake Rouse |
Bug Description
Sometimes in the CI, boot resources do not start downloading. In the UI, the selections are still shown, but the button says 'Save Selections' indicating that they have not been persisted. In the CLI, boot-sources and boot-source-
root@autopkgtes
Success.
Machine-readable output follows:
[
{
"id": 1,
"updated": "2016-11-
"created": "2016-11-
"url": "http://
}
]
root@autopkgtes
Success.
Machine-readable output follows:
[
{
"arches": [
"amd64"
],
"os": "ubuntu",
"*"
],
"labels": [
"*"
],
"release": "xenial",
"id": 1
}
]
root@autopkgtes
Success.
Machine-readable output follows:
[]
Restarting the import again with stop-import and import calls, seems to make things work again.
Related branches
- Mike Pontillo (community): Approve
-
Diff: 43 lines (+16/-0)2 files modifiedsrc/maasserver/api/boot_resources.py (+6/-0)
src/maasserver/api/tests/test_boot_resources.py (+10/-0)
- Mike Pontillo (community): Approve
-
Diff: 43 lines (+16/-0)2 files modifiedsrc/maasserver/api/boot_resources.py (+6/-0)
src/maasserver/api/tests/test_boot_resources.py (+10/-0)
description: | updated |
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Undecided → High |
milestone: | none → 2.2.0 |
tags: | added: cdoqa-blocker |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
tags: |
added: cdo-qa-blocker removed: cdoqa-blocker |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Here's a link the the MAAS log - there are a lot of 'interesting' messages in there