Manually running mock

[Moray Henderson]

> -----Original Message-----
> From: Mike McLean [mailto:mikem at redhat.com]
> Sent: 29 May 2012 17:03
> 
> On 05/25/2012 12:21 PM, Moray Henderson wrote:
> > 3 weeks ago, before I went on holiday, I could debug build problems
> by
> > logging into my koji build server and get into the mock chroot with
> > something like
> >
> >    su - kojibuilder -c "mock -v -r koji/slsbox-1.1-build-186-252 --
> shell"
> >
> > Now when I try it, it fails with
> 
> So mock init succeeds, but mock --shell fails? Perhaps the chroot is
> lacking /bin/bash. Have you looked? Were there any unusual errors in
> root.log?

I think that it was Koji housekeeping removing the mock root as fast as I was building it.  Do mock roots with failed builds last longer than successful ones?  I never had this problem going into a mock root to investigate a failed build, but when I try to reinitialize an older root - even when the mock config is still available - Koji seems to find it and remove it almost immediately.

The "error" in root.log I was trying to investigate was "Could not downgrade policy file /etc/selinux/targeted/policy/policy.24" from SELinux.  Looks like that is not really an error, just what happens when Policy is loaded while SELinux is disabled.


Moray.
“To err is human; to purr, feline.”