Image builds on Ubuntu 14.04 fails with errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
diskimage-builder |
Fix Released
|
High
|
azher ullah khan |
Bug Description
While performing the image builds using diskimage-builder on Ubuntu 14.04 (mke2fs 1.42.9) VM the builds fail with the below error. However the build completes successfully while performed on Ubuntu 13.10 (mke2fs 1.42.8) VM.
Below is the error log:
*******
-------
Target: post-install.d
Script Seconds
-------
99-write-
99-clean-up-cache 0.034
99-build-ramdisk 5.360
95-post-
01-ensure-binaries 0.017
00-unconfigure-
-------
mke2fs 1.42.9 (4-Feb-2014)
Discarding device blocks: 4096/393168
Filesystem label=cloudimg-
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
393216 inodes, 393168 blocks
19658 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=402653184
12 block groups
32768 blocks per group, 32768 fragments per group
32768 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/12 done
Writing inode tables: 0/12 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/12 done
mv: cannot remove '/tmp/image.
mv: cannot remove '/tmp/image.
mv: cannot remove '/tmp/image.
mv: cannot remove '/tmp/image.
mv: cannot remove '/tmp/image.
mv: cannot remove '/tmp/image.
mv: cannot remove '/tmp/image.
mv: error reading '/tmp/image.
mv: failed to extend '/tmp/image.
*******
Changed in diskimage-builder: | |
status: | Incomplete → In Progress |
assignee: | Ghe Rivero (ghe.rivero) → azher ullah khan (azher-ullah-khan) |
Changed in diskimage-builder: | |
status: | In Progress → Fix Released |
azher, Thanks for taking the time to file this bug report, it is much appreciated.
I've built quite a few, in the hundreds, of images on Ubuntu 14.04 VMs without seeing this problem.
The error itself doesn't look like an mke2fs problem anyway. Can you look in your logs for apparmor denials, or something of that nature? Also please provide the exact command line you used to produce the error. Also a copy of the output of 'dpkg -l' would be useful.
Thanks!