Red Hat Bugzilla – Bug 506288
'mock --shell' fails if 'mock --init' isn't done first
Last modified: 2013-01-10 00:15:21 EST
Description of problem:
Try to use a mock shell on new configuration:
# mock -r fedora-9-i386 --shell
INFO: mock.py version 0.9.16 starting...
State Changed: init plugins
State Changed: start
State Changed: lock buildroot
ERROR: Command failed. See logs for output.
# mount -n -t proc mock_chroot_proc /var/lib/mock/fedora-9-i386/root/proc
The problem appears to be that 'mock --init' must be done before 'mock --shell'. In the above example, /var/lib/mock/fedora-9-i386 doesn't exist until the 'mock --init' is run.
At minimum, a better error message should be generated.
Version-Release number of selected component (if applicable):
Every time (until 'mock --init' has been run).
added code to raise runtime exception if --shell specified for uninitialized chroot. should go into next release (0.9.17)