vdb partitioned with zfsroot, but not mounted: deploy failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned | ||
curtin |
Fix Released
|
High
|
Unassigned |
Bug Description
curtin 18.1-1-
maas 2.4.0~beta1-
I had vdb partioned with zfsroot, but not mounted (i.e., it's not under "file systems").
Tried a deploy with vda-part1 formatted with zfsroot and mounted at /, but that failed:
"""
curtin: Installation started. (18.1-1-
third party drivers not installed or necessary.
zfsroot found in two entries in storage config: [{'fstype': 'zfsroot', 'id': 'vda-part1_format', 'label': '', 'type': 'format', 'uuid': 'd85b2613-
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: zfsroot found in two entries in storage config: [{'fstype': 'zfsroot', 'id': 'vda-part1_format', 'label': '', 'type': 'format', 'uuid': 'd85b2613-
Stderr: ''
"""
Looks like it still "saw" zfs on vdb and got confused.
Related branches
- Ryan Harper (community): Needs Fixing
- Scott Moser (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 191 lines (+93/-28)3 files modifiedcurtin/commands/block_meta.py (+14/-3)
doc/topics/storage.rst (+8/-1)
tests/unittests/test_commands_block_meta.py (+71/-24)
description: | updated |
Changed in curtin: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | 2.4.0beta2 → 2.4.0beta3 |
Changed in maas: | |
milestone: | 2.4.0beta3 → 2.4.0beta4 |
Changed in maas: | |
milestone: | 2.4.0beta4 → 2.4.x |
Hey Andreas,
Can you please attach the curtin config file sent to curtin?
maas <user> machines get-curtin-config <system_id>