Click fails to create chroot (exit status 100) during Kit creation process
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
click (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Creating a Kit using the Ubuntu SDK startup wizard. Everything starts okay and packages begin to download and install, etc. All of a sudden the process stops and I get the following output in bold red text:
There was an error creating the click target, cleaning up
click target was removed successfully
---Click exited with errors, please check the output---Traceback (most recent call last):
File "/usr/bin/click", line 86, in <module>
sys.
File "/usr/bin/click", line 82, in main
return mod.run(args)
File "/usr/lib/
return args.func(parser, args)
File "/usr/lib/
return chroot.
File "/usr/lib/
self.full_name, ret_code))
click.chroot.
Command returned 100: schroot -u root -c source:
E: Sub-process /usr/bin/dpkg returned an error code (2)
E: Failed to write temporary StateFile /var/lib/
dpkg: unrecoverable fatal error, aborting:
unable to create `/var/lib/
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
dpkg: error processing archive /var/cache/
unable to create `/usr/include/
Moving old data out of the way
Okay, turns out this is not a false reporting. My root filesystem turned out to be eating inodes, locking up my system just a few minutes later.
Still, I'll leave this here in case it presents any usability issues (e.g. better reporting that disk space is the cause).