Ontap S3 push request fails with unexpected HTTP status: 500 Internal Server Error
Applies to
- ONTAP 9
- S3
- Redhat Quay
- OpenShift
Issue
- While trying to pull images from an OpenShift S3 client, it fails with the error:
‘Error: parsing image configuration: fetching blob: received unexpected HTTP status: 500 Internal Server Error’.
Command used on the client: [root@hostname-registry]# podman pull dr-quay-registry-quay-quay-enterprise.apps.s2.abc.xyz/init/ngnix:latest, which has a registry configured consisting of all the details like hostname, access-key, secret-key required for S3 bucket access.
- The issue occurs only when connecting using the hostname. When the host IP address is used instead, the error does not appear
Troubleshoot:
Use tools like ping, nslookup, or dig to check if the hostname resolves correctly:
- Check Configured DNS Servers,on Linux, run:
cat /etc/resolv.conf- Verify that valid DNS servers are listed. - Attempt Forward Lookup, from a terminal, run:
nslookup <hostname>-Confirm that the hostname resolves to an IP address. - Attempt Reverse Lookup, from a terminal, run:
nslookup <IP_address_of_host>-Confirm that the IP resolves back to the expected hostname.
