When populating new zuul-merger, some merge operations will eventually fail for example:
GitCommandError: 'git clone -v ssh://email@example.com:29418/operations/puppet /srv/zuul/git/operations/puppet' returned with exit code 128
stderr: 'fatal: destination path '/srv/zuul/git/operations/puppet' already exists and is not an empty directory.
In the above case, the repository operations/puppet/mariadb had a merge request handled. That creates the directory /srv/zuul/git/**operations/puppet**.
Later when a merge request is handled for `operations/puppet` git clone fails due to the path already existing.
1) delete the directory entirely and manually clone as zuul user or `recheck` till a merge job runs on that host
sudo -H -u zuul bash -l
git init .
git remote add origin ssh://firstname.lastname@example.org:29418/operations/software
git remote set-head origin --auto
zuul-merger should not just git-clone but be smarter and gracefully handle a directory that already exists.