Comment 1 for bug 1606181

Revision history for this message
Artem Hrechanychenko (agrechanichenko) wrote : Re: deploy master node failed due to [Errno 256] No more mirrors to try

Update

looks like problem in dns

[root@nailgun ~]# yum clean all
Loaded plugins: fastestmirror, priorities
Bad id for repo: CentOS-7 - Extras, byte = 8
Cleaning repos: 10.0_auxiliary CentOS-Plus CentOS-contrib base extras mos mos10.0-base mos10.0-security mos10.0-updates updates
Cleaning up everything
Cleaning up list of fastest mirrors
[root@nailgun ~]# yum install -y ami-creator
Loaded plugins: fastestmirror, priorities
Bad id for repo: CentOS-7 - Extras, byte = 8
10.0_auxiliary | 2.9 kB 00:00:00
http://mirror.centos.org/centos/7.2.1511//centosplus/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: mirror.centos.org; Unknown error"
Trying other mirror.
http://mirror.centos.org/centos/7.2.1511//cr/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: mirror.centos.org; Unknown error"
Trying other mirror.
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=genclo error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"

 One of the configured repositories failed (Unknown),
 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 <repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
[root@nailgun ~]# ping ya.ru
ping: unknown host ya.ru
[root@nailgun ~]# cat /etc/resolv.conf
search test.domain.local
domain test.domain.local
nameserver 10.109.21.2

Before starting bootstrap_admin_node.sh dns nameserver for searching was 8.8.8.8

[root@nailgun ~]# cat /etc/hiera/astute.yaml |grep DNS
"DNS_DOMAIN": "test.domain.local"
"DNS_SEARCH": "test.domain.local"
"DNS_UPSTREAM": "10.109.21.1"

after changing 10.109.21.2 to 8.8.8.8 in /etc/resolv.conf all works fine