{"action":"created","issue":{"url":"https://api.github.com/repos/CiscoCloud/mantl/issues/1697","repository_url":"https://api.github.com/repos/CiscoCloud/mantl","labels_url":"https://api.github.com/repos/CiscoCloud/mantl/issues/1697/labels{/name}","comments_url":"https://api.github.com/repos/CiscoCloud/mantl/issues/1697/comments","events_url":"https://api.github.com/repos/CiscoCloud/mantl/issues/1697/events","html_url":"https://github.com/CiscoCloud/mantl/issues/1697","id":165391888,"number":1697,"title":"repository failure when updating mantl nodes using ansible","user":{"login":"ACluelessOne","id":18348293,"avatar_url":"https://avatars.githubusercontent.com/u/18348293?v=3","gravatar_id":"","url":"https://api.github.com/users/ACluelessOne","html_url":"https://github.com/ACluelessOne","followers_url":"https://api.github.com/users/ACluelessOne/followers","following_url":"https://api.github.com/users/ACluelessOne/following{/other_user}","gists_url":"https://api.github.com/users/ACluelessOne/gists{/gist_id}","starred_url":"https://api.github.com/users/ACluelessOne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ACluelessOne/subscriptions","organizations_url":"https://api.github.com/users/ACluelessOne/orgs","repos_url":"https://api.github.com/users/ACluelessOne/repos","events_url":"https://api.github.com/users/ACluelessOne/events{/privacy}","received_events_url":"https://api.github.com/users/ACluelessOne/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-07-13T18:39:33Z","updated_at":"2016-07-14T09:56:50Z","closed_at":null,"body":"Whern running\r\nansible-playbook playbooks/upgrade-packages.yml\r\nthe following error occurs and only 2 nodes are successful\r\n\r\nTASK: [refresh yum cache] *****************************************************\r\nfailed: [mantl-control-01] => {\"changed\": true, \"cmd\": [\"yum\", \"makecache\"], \"delta\": \"0:00:00.560416\", \"end\": \"2009-10-01 11:08:47.928627\", \"rc\": 1, \"start\": \"2009-10-01 11:08:47.368211\", \"warnings\": [\"Consider using yum module rather than running yum\"]}\r\nstderr:\r\n\r\n One of the configured repositories failed (Unknown),\r\n and yum doesn't have enough cached data to continue. At this point the only\r\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\r\n\r\n     1. Contact the upstream for the repository and get them to fix the problem.\r\n\r\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\r\n        upstream. This is most often useful if you are using a newer\r\n        distribution release than is supported by the repository (and the\r\n        packages for the previous distribution release still work).\r\n\r\n     3. Disable the repository, so yum won't use it by default. Yum will then\r\n        just ignore the repository until you permanently enable it again or use\r\n        --enablerepo for temporary usage:\r\n\r\n            yum-config-manager --disable <repoid>\r\n\r\n     4. Configure the failing repository to be skipped, if it is unavailable.\r\n        Note that yum will try to contact the repo. when it runs most commands,\r\n        so will have to try and fail each time (and thus. yum will be be much\r\n        slower). If it is a very temporary problem though, this is often a nice\r\n        compromise:\r\n\r\n            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true\r\n\r\nCannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again\r\nstdout: Loaded plugins: fastestmirror, langpacks\r\nfailed: [mantl-worker-002] => {\"changed\": true, \"cmd\": [\"yum\", \"makecache\"], \"delta\": \"0:00:00.584094\", \"end\": \"2009-10-01 11:08:47.952997\", \"rc\": 1, \"start\": \"2009-10-01 11:08:47.368903\", \"warnings\": [\"Consider using yum module rather than running yum\"]}\r\nstderr:\r\n\r\n One of the configured repositories failed (Unknown),\r\n and yum doesn't have enough cached data to continue. At this point the only\r\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\r\n\r\n     1. Contact the upstream for the repository and get them to fix the problem.\r\n\r\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\r\n        upstream. This is most often useful if you are using a newer\r\n        distribution release than is supported by the repository (and the\r\n        packages for the previous distribution release still work).\r\n\r\n     3. Disable the repository, so yum won't use it by default. Yum will then\r\n        just ignore the repository until you permanently enable it again or use\r\n        --enablerepo for temporary usage:\r\n\r\n            yum-config-manager --disable <repoid>\r\n\r\n     4. Configure the failing repository to be skipped, if it is unavailable.\r\n        Note that yum will try to contact the repo. when it runs most commands,\r\n        so will have to try and fail each time (and thus. yum will be be much\r\n        slower). If it is a very temporary problem though, this is often a nice\r\n        compromise:\r\n\r\n            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true\r\n\r\nCannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again\r\nstdout: Loaded plugins: fastestmirror, langpacks\r\nfailed: [mantl-worker-003] => {\"changed\": true, \"cmd\": [\"yum\", \"makecache\"], \"delta\": \"0:00:00.674464\", \"end\": \"2009-10-01 12:10:42.225450\", \"rc\": 1, \"start\": \"2009-10-01 12:10:41.550986\", \"warnings\": [\"Consider using yum module rather than running yum\"]}\r\nstderr:\r\n\r\n One of the configured repositories failed (Unknown),\r\n and yum doesn't have enough cached data to continue. At this point the only\r\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\r\n\r\n     1. Contact the upstream for the repository and get them to fix the problem.\r\n\r\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\r\n        upstream. This is most often useful if you are using a newer\r\n        distribution release than is supported by the repository (and the\r\n        packages for the previous distribution release still work).\r\n\r\n     3. Disable the repository, so yum won't use it by default. Yum will then\r\n        just ignore the repository until you permanently enable it again or use\r\n        --enablerepo for temporary usage:\r\n\r\n            yum-config-manager --disable <repoid>\r\n\r\n     4. Configure the failing repository to be skipped, if it is unavailable.\r\n        Note that yum will try to contact the repo. when it runs most commands,\r\n        so will have to try and fail each time (and thus. yum will be be much\r\n        slower). If it is a very temporary problem though, this is often a nice\r\n        compromise:\r\n\r\n            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true\r\n\r\nmantl-control-01           : ok=1    changed=1    unreachable=0    failed=1\r\nmantl-control-02           : ok=1    changed=1    unreachable=0    failed=1\r\nmantl-control-03           : ok=1    changed=1    unreachable=0    failed=1\r\nmantl-edge-01              : ok=4    changed=2    unreachable=0    failed=0\r\nmantl-edge-02              : ok=1    changed=1    unreachable=0    failed=1\r\nmantl-worker-001           : ok=4    changed=2    unreachable=0    failed=0\r\nmantl-worker-002           : ok=1    changed=1    unreachable=0    failed=1\r\nmantl-worker-003           : ok=1    changed=1    unreachable=0    failed=1\r\n\r\n\r\n- Ansible version (`ansible --version`):  1.9.6 \r\n- Python version (`python --version`): 2.7.5\r\n- Git commit hash or branch: \r\n- Cloud Environment: CentOS 7 with vsphere/vcenter\r\n- Terraform version (`terraform version`): 0.6.16\r\n"},"comment":{"url":"https://api.github.com/repos/CiscoCloud/mantl/issues/comments/232620827","html_url":"https://github.com/CiscoCloud/mantl/issues/1697#issuecomment-232620827","issue_url":"https://api.github.com/repos/CiscoCloud/mantl/issues/1697","id":232620827,"user":{"login":"ACluelessOne","id":18348293,"avatar_url":"https://avatars.githubusercontent.com/u/18348293?v=3","gravatar_id":"","url":"https://api.github.com/users/ACluelessOne","html_url":"https://github.com/ACluelessOne","followers_url":"https://api.github.com/users/ACluelessOne/followers","following_url":"https://api.github.com/users/ACluelessOne/following{/other_user}","gists_url":"https://api.github.com/users/ACluelessOne/gists{/gist_id}","starred_url":"https://api.github.com/users/ACluelessOne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ACluelessOne/subscriptions","organizations_url":"https://api.github.com/users/ACluelessOne/orgs","repos_url":"https://api.github.com/users/ACluelessOne/repos","events_url":"https://api.github.com/users/ACluelessOne/events{/privacy}","received_events_url":"https://api.github.com/users/ACluelessOne/received_events","type":"User","site_admin":false},"created_at":"2016-07-14T09:56:49Z","updated_at":"2016-07-14T09:56:49Z","body":"Installed Packages\r\nName        : epel-release\r\nArch        : noarch\r\nVersion     : 7\r\nRelease     : 7\r\nSize        : 24 k\r\nRepo        : installed\r\nFrom repo   : epel\r\nSummary     : Extra Packages for Enterprise Linux repository configuration\r\nURL         : http://download.fedoraproject.org/pub/epel\r\nLicense     : GPLv2\r\nDescription : This package contains the Extra Packages for Enterprise Linux\r\n            : (EPEL) repository GPG key as well as configuration for yum.\r\n\r\nno packages marked for updates when i try to update ca-certificates"}}
{"actor":{"display_login":"ACluelessOne"}}