dib fails with error creating loopback file system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
diskimage-builder |
Fix Released
|
High
|
Ian Wienand |
Bug Description
Error log snippet is attached, the relevant lines are also shown below.
2017-06-16 04:26:05.784026 | 2017-06-16 04:26:05.783 | 2017-06-16 04:26:05.753 INFO diskimage_
2017-06-16 04:26:05.785293 | 2017-06-16 04:26:05.784 | 2017-06-16 04:26:05.761 DEBUG diskimage_
2017-06-16 04:26:05.787201 | 2017-06-16 04:26:05.786 | 2017-06-16 04:26:05.761 INFO diskimage_
2017-06-16 04:26:05.788505 | 2017-06-16 04:26:05.788 | 2017-06-16 04:26:05.774 DEBUG diskimage_
2017-06-16 04:26:05.789624 | 2017-06-16 04:26:05.789 | 2017-06-16 04:26:05.775 ERROR diskimage_
2017-06-16 04:26:05.790794 | 2017-06-16 04:26:05.790 | Traceback (most recent call last):
2017-06-16 04:26:05.792530 | 2017-06-16 04:26:05.792 | File "/usr/local/
2017-06-16 04:26:05.793738 | 2017-06-16 04:26:05.793 | node.create()
2017-06-16 04:26:05.794954 | 2017-06-16 04:26:05.794 | File "/usr/local/
2017-06-16 04:26:05.796104 | 2017-06-16 04:26:05.795 | exec_sudo(cmd)
2017-06-16 04:26:05.797612 | 2017-06-16 04:26:05.797 | File "/usr/local/
2017-06-16 04:26:05.798710 | 2017-06-16 04:26:05.798 | ' '.join(sudo_cmd))
2017-06-16 04:26:05.799892 | 2017-06-16 04:26:05.799 | CalledProcessError: Command 'sudo mkfs -t ext4 -i 4096 -J size=64 -L cloudimg-rootfs -U a0bacc98-
Changed in diskimage-builder: | |
assignee: | Michael Johnson (johnsom) → Ian Wienand (iwienand) |
Thanks, we had a report of this in the morning, but this captures that the device isn't there.
Clearly the synchronous option to kpartx isn't all we want it to be. I think a sleep after the call might be the quickest solution here. Or maybe a udevadm settle call ... But maybe that is just a placebo for a sleep.
I'm on a phone so can't propose a change, but I think that will help