INFO: mock.py version 1.1.38 starting...
Start: init plugins
INFO: tmpfs initialized
INFO: selinux disabled
Finish: init plugins
Start: run
INFO: Start(/mnt/dar/packages/galera/galera-25.3.5-6.fc20.art.src.rpm)  Config(fedora-9-x86_64)
Start: lock buildroot
Start: clean chroot
INFO: chroot (/var/lib/mock/fedora-9-x86_64) unlocked and deleted
Finish: clean chroot
Finish: lock buildroot
Start: chroot init
Start: lock buildroot
Mock Version: 1.1.38
INFO: Mock Version: 1.1.38
INFO: calling preinit hooks
INFO: mounting tmpfs at /var/lib/mock/fedora-9-x86_64/root/.
INFO: enabled root cache
INFO: enabled yum cache
Start: cleaning yum metadata
Finish: cleaning yum metadata
INFO: enabled ccache
Start: device setup
Finish: device setup
Start: yum update
INFO: unmounting tmpfs.
ERROR: Exception(/mnt/dar/packages/galera/galera-25.3.5-6.fc20.art.src.rpm) Config(fedora-9-x86_64) 0 minutes 0 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-9-x86_64/result
ERROR: Command failed: 
 # ['/usr/bin/yum', '--installroot', '/var/lib/mock/fedora-9-x86_64/root/', 'groupinstall', 'buildsys-build']
There is no installed groups file.
Maybe run: yum groups mark convert (see man yum)
http://build/atomicorp/atomic/fedora/9/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: build"
Trying other mirror.


 One of the configured repositories failed (atomic),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable atomic

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=atomic.skip_if_unavailable=true

failure: repodata/repomd.xml from atomic: [Errno 256] No more mirrors to try.
http://build/atomicorp/atomic/fedora/9/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: build"