curtin raises an error using the bcache storage layout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Undecided
|
Javier Fuentes |
Bug Description
Using bcache as storage layout raises an error during the deployment phase of a(n arm64) machine. Any other storage layout complete the deployment successfully without errors.
This has been observed consistently in 3 different machines, all arm64, deploying Ubuntu 22 and 20. The MAAS installation used is snap for the version 3.2.
The error reported in the machine installation logs ("Installation output" tab) is as follows:
'''
Running command ['umount', '/tmp/tmptbdyj2
finish: cmd-install/
finish: cmd-install/
finish: cmd-install/
Traceback (most recent call last):
File "/curtin/
ret = args.func(args)
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
File "/curtin/
return subp(*args, **kwargs)
File "/curtin/
return _subp(*args, **kwargs)
File "/curtin/
raise ProcessExecutio
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmptbdyj2
Exit code: 1
Reason: -
Stdout: ''
Stderr: Installing grub to /boot/efi.
'''
MAAS logs extracted from snap/maas/ common/ log/maas. log snap/maas/ common/ log/rackd. log snap/maas/ common/ log/regiond. log
/var/
/var/
/var/
Other logs _script_ c4mxmt. txt -> maas $ADMIN node-script-result download $SYSTEM_ID current- commissioning | tee <file>.txt
commissioning
Configurations snap/maas/ 32954/preseeds/ curtin_ userdata
/var/
Machine installation logs (downloaded through the "Download" button in the "Installation output" subtab in the "Logs" tab) infra-1- arm.maas- installation- output- 2024-04- 04.log infra-1- arm.maas- curtin- 2024-04- 04.tar lab2-infra- 1-arm.maas- machine- output- 2024-04- 04.xml infra-1- arm.maas- machine- output- 2024-04- 04.yaml
installation output: sqa-lab2-
curtin-logs: sqa-lab2-
machine output (xml):sqa-
machine output (yaml): sqa-lab2-