You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Amazon Linux 2 AMI and running the proxy deployment script from control host fails with this error:
fatal: [10.173.86.8]: FAILED! => {"changed": false, "msg": "Repository 'docker-ce-edge' is missing name in configuration, using id\nhttps://download.docker.com/linux/centos/2/x86_64/stable/repodata/repomd.xml:[Errno 14] HTTPS Error 404 - Not Found\nTrying other mirror.\n\n\n One of the configured repositories failed (Docker CE Stable - x86_64),\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. forthe 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=docker-ce-stable ...\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 docker-ce-stable\n or\n subscription-manager repos --disable=docker-ce-stable\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=docker-ce-stable.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.\nhttps://download.docker.com/linux/centos/2/x86_64/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\n", "rc": 1, "results": []}
fatal: [10.173.86.220]: FAILED! => {"changed": false, "msg": "Repository 'docker-ce-edge' is missing name in configuration, using id\nhttps://download.docker.com/linux/centos/2/x86_64/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\nTrying other mirror.\n\n\n One of the configured repositories failed (Docker CE Stable - x86_64),\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=docker-ce-stable ...\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 docker-ce-stable\n or\n subscription-manager repos --disable=docker-ce-stable\n\n 5. Configure the failing repository to be skipped, if it is unavailable.\n Note that yum willtry 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=docker-ce-stable.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.\nhttps://download.docker.com/linux/centos/2/x86_64/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\n", "rc": 1, "results": []}
fatal: [10.173.86.126]: FAILED! => {"changed": false, "msg": "Repository 'docker-ce-edge' is missing name in configuration, using id\nhttps://download.docker.com/linux/centos/2/x86_64/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\nTrying other mirror.\n\n\n One of the configured repositories failed (Docker CE Stable - x86_64),\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=docker-ce-stable ...\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 docker-ce-stable\n or\n subscription-manager repos --disable=docker-ce-stable\n\n 5. Configure the failing repository to be skipped, if it is unavailable.\n Note that yum willtry 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=docker-ce-stable.skip_if_unavailable=true\n\nfailure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.\nhttps://download.docker.com/linux/centos/2/x86_64/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found\n", "rc": 1, "results": []}```
┆Issue is synchronized with this [Jira Task](https://datastax.jira.com/browse/ZDM-588) by [Unito](https://www.unito.io)
┆Components: Automation
┆Priority: Major
The text was updated successfully, but these errors were encountered:
Using Amazon Linux 2 AMI and running the proxy deployment script from control host fails with this error:
The text was updated successfully, but these errors were encountered: