TASK [upgrade-os : installing ceph]

[mwmw7]

I got a fatal error message while "vagrant up" below is error message that i had { "changed":true, "cmd":"yum install -y ceph", "delta":"0:00:01.250557", "end":"2017-04-17 04:29:45.345051", "failed":true, "rc":1, "start":"2017-04-17 04:29:44.094494", "stderr":"\n\n One of the configured repositories failed (Unknown),\n and yum doesn't have enough cached data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n 1. Contact the upstream for the repository and get them to fix the problem.\n\n 2. Reconfigure the baseurl/etc. for the repository, to point to a working\n upstream. This is most often useful if you are using a newer\n distribution release than is supported by the repository (and the\n packages for the previous distribution release still work).\n\n 3. Run the command with the repository temporarily disabled\n yum --disablerepo=<repoid> ...\n\n 4. Disable the repository permanently, so yum won't use it by default. Yum\n will then just ignore the repository until you permanently enable it\n again or use --enablerepo for temporary usage:\n\n yum-config-manager --disable <repoid>\n or\n subscription-manager repos --disable=<repoid>\n\n 5. Configure the failing repository to be skipped, if it is unavailable.\n Note that yum will try to contact the repo. when it runs most commands,\n so will have to try and fail each time (and thus. yum will be be much\n slower). If it is a very temporary problem though, this is often a nice\n compromise:\n\n yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true\n\nCannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again", "stderr_lines":[ "", "", " 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. Run the command with the repository temporarily disabled", " yum --disablerepo=<repoid> ...", "", " 4. Disable the repository permanently, 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>", " or", " subscription-manager repos --disable=<repoid>", "", " 5. 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 retrieve metalink for repository: epel/x86_64. Please verify its path and try again" ], "stdout":"Loaded plugins: fastestmirror", "stdout_lines":[ "Loaded plugins: fastestmirror" ] }

So I access to kube1 VM and check yum and yum is not wokring in side of VM

[mwmw7]

Sorry there was a proxy setting in my home path This step is pass by removing proxy setting in my home path