Bug 506288 - 'mock --shell' fails if 'mock --init' isn't done first
Summary: 'mock --shell' fails if 'mock --init' isn't done first
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Clark Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-16 15:14 UTC by David Smith
Modified: 2013-01-10 05:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-18 01:22:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Smith 2009-06-16 15:14:20 UTC
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):

mock-0.9.16-1.fc11

How reproducible:

Every time (until 'mock --init' has been run).

Comment 1 Clark Williams 2009-07-08 16:42:31 UTC
added code to raise runtime exception if --shell specified for uninitialized chroot. should go into next release (0.9.17)


Note You need to log in before you can comment on or make changes to this bug.