New Koji Setup - regen-repo task fails

[Mike McLean]

On 02/12/2015 03:00 PM, Kirk Harr wrote:
> When setting up a new Koji setup, I submit a regen-repo task which is picked up by the single builder host that I have setup, which fails with a message in the kojid.log file:
> 
> <snip>
> 2015-02-12 14:48:35,496 [WARNING] koji.TaskManager: TRACEBACK: Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/koji/daemon.py", line 1161, in runTask
>     response = (handler.run(),)
>   File "/usr/lib/python2.7/site-packages/koji/tasks.py", line 157, in run
>     return koji.util.call_with_argcheck(self.handler, self.params, self.opts)
>   File "/usr/lib/python2.7/site-packages/koji/util.py", line 139, in call_with_argcheck
>     return func(*args, **kwargs)
>   File "/usr/sbin/kojid", line 3536, in handler
>     raise koji.GenericError, "Repo directory missing: %s" % path
> GenericError: Repo directory missing: /mnt/koji/repos/dist-centos6-build/1085
> </snip>
> 
> This directory /mnt/koji/repos/dist-centos6-build/1085 does exist on the host inside /mnt/koji which is a GlusterFS share which the Kojira/Koji-hub/Koji-web host and the builder host share with each other. Is there any cause for this error to occur when the directory referenced as missing does actually exist?


The test that appears to be failing is:
> if not os.path.isdir(path):
>     raise koji.GenericError, "Repo directory missing: %s" % path

This test happens just after the hub call to host.repoInit (which
creates the stub repo dir with basic data).

A few possibilities:
1) some sort of race issue where the new directory is still unknown to
the builder
2) some sort of permission error where the kojid process cannot see the
directory (does gluster do anything like "root squash"?)
3) the mount isn't set up on the builder after all
4) some sort of path mismatch (e.g. mounted in the wrong place)