bootresources.yaml contains "selections: null"
Bug #1298652 reported by
Raphaël Badin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Julian Edwards |
Bug Description
After installing the daily package, /etc/maas/
# <lots of comments>
boot:
sources:
- keyring: /usr/share/
path: http://
selections: null
storage: /var/lib/
Looks related to the config-rewriting code that landed recently.
The result is that *all* the images published in http://
Related branches
lp:~julian-edwards/maas/selections-wiped-bug-1298652
- Jeroen T. Vermeulen (community): Approve
-
Diff: 30 lines (+6/-2)2 files modifiedsrc/provisioningserver/tests/test_upgrade_cluster.py (+2/-1)
src/provisioningserver/upgrade_cluster.py (+4/-1)
description: | updated |
Changed in maas: | |
milestone: | none → 14.04 |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Julian Edwards (julian-edwards) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think I found the source of the bug. This code is wrong:
def rewrite_ boot_resources_ config( config_ file): yaml` configuration.
"""Rewrite the `bootresources.
Supports the `generate_ boot_resources_ config` upgrade hook. load_from_ cache() ['tftp' ]['root' ]
"""
tftproot = Config.
tftproot ends up pointing at the *new* tftp area rather than the old one. This is because the default tftp "root" config on pserv.yaml is commented out so it comes from the default schema value which has been updated to the new area.
This highlights a second problem; if someone altered their tftp root and configured it in pserv.yaml, the new boot resources will not be found.