-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHECK [memory_availability] fail when run ansible playbook on OKD 3.11 #85
Comments
Will take a look into this shortly. Any special changes you made to the setup that made it non-standard? |
no, just make infrastructure and make openshift. |
Have you tried rerunning make openshift? It can be a little flakey on the
ansible side, but is idempotent so safe to run and rerun
…On Fri, 5 Apr 2019 at 12:21 PM, Pichate Ins ***@***.***> wrote:
no, just make infrastructure and make openshift.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB1nSATxXHb6rbEk7XbbboA8-GUl-fY0ks5vds9EgaJpZM4cc_F9>
.
|
i try to run many time. but still got same error |
I have completely cleaned and retried locally, everything works: I think you are encountering the below: openshift/openshift-ansible#11369 I have some other things I'm looking into (see below) but for now I think it is the issue above. Will update this comment as tI debug more. There's not been any activity on that issue for a while - have you tried again recently? It might have been that the image was just unavailable for a period of time... Potential things to try
Similar Issues Searching for similar issues, I've found these:
Summarising:
In all cases it is a failure to download a specific image. In your case, the specific image which is failing to download is: As indicated by:
So right now it looks like an issue with quay.io/coreos/etcd:v3.2.22 |
I was testing on ap-southeast-1 got the same issue but the ap-southeast-2 was working smoothly |
That is bizarre.... Let me see if I can repro in the same way |
I am also getting the same issue, it worked yesterday, I destroyed everything and then when I tried it again, getting the issue even after several retries, deleted the tf state files and tried everything from beginning still getting the same issue. |
I was getting this as well. The issue may be related to this issue: openshift/openshift-ansible#10741 The workaround to disable the availability check worked for me and I was able to install this cluster successfully. |
@dwmkerr hello any workaround for this issue ? I have the same problem |
I too see the same with openshift-ansible-3.11.37-1.git.0.3b8b341.el7.noarch on Centos 7.
regards, L. |
CHECK [memory_availability : ip-10-0-1-238.ap-southeast-1.compute.internal] ****
fatal: [ip-10-0-1-238.ap-southeast-1.compute.internal]: FAILED! => {"changed": true, "checks": {"disk_availability": {}, "docker_image_availability": {"changed": true, "failed": true, "failures": [["OpenShiftCheckException", "One or more required container images are not available:\n quay.io/coreos/etcd:v3.2.22\nChecked with: skopeo inspect [--tls-verify=false] [--creds=:] docker:///\n"]], "msg": "One or more required container images are not available:\n quay.io/coreos/etcd:v3.2.22\nChecked with: skopeo inspect [--tls-verify=false] [--creds=:] docker:///\n"}, "docker_storage": {"changed": true, "data_pct_used": 0.023671361645169142, "data_threshold": 90.0, "data_total": "34.18 GB", "data_total_bytes": 36700495544.32, "data_used": "19.92 MB", "data_used_bytes": 20887633.92, "metadata_pct_used": 0.00011372055802915023, "metadata_threshold": 90.0, "metadata_total": "88.08 MB", "metadata_total_bytes": 92358574.08, "metadata_used": "57.34 kB", "metadata_used_bytes": 58716.16, "msg": "Thinpool usage is within thresholds.", "vg_free": "48.00g", "vg_free_bytes": 51539607552.0}, "memory_availability": {}, "package_availability": {"changed": false, "invocation": {"module_args": {"packages": ["PyYAML", "bash-completion", "bind", "ceph-common", "dnsmasq", "docker", "firewalld", "flannel", "glusterfs-fuse", "httpd-tools", "iptables", "iptables-services", "iscsi-initiator-utils", "libselinux-python", "nfs-utils", "ntp", "openssl", "origin", "origin-clients", "origin-hyperkube", "origin-node", "pyparted", "python-httplib2", "yum-utils"]}}}, "package_version": {"changed": false, "invocation": {"module_args": {"package_list": [{"check_multi": false, "name": "origin", "version": "3.11"}, {"check_multi": false, "name": "origin-master", "version": "3.11"}, {"check_multi": false, "name": "origin-node", "version": "3.11"}], "package_mgr": "yum"}}}}, "msg": "One or more checks failed", "playbook_context": "install"}
The text was updated successfully, but these errors were encountered: