Image discovery failed

Hi Team,

I am facing an error while adding a new repository of type “container images” which I am trying to discover it from dockerhub. After adding I am facing endless spinning wheel which later redirecting to “Discovery failed. Error: Timed out connecting to server” Can anyone please guide me? There is no issue when I try to discover the yum repositories. Please find the screenshot attached.

Thanks in advance

Regards
Siddharth

@tbrisker Could you please take a look?

This is probably a question for @katello team, I’m not sure who worked on the repo discovery for containers

Hi @almond - which version of Katello are you running?

I have katello-3.15.3.1 @Jonathon_Turel @katello

@Jonathon_Turel @katello Also I have tried through hammer cli and I am getting this error
Katello::Errors::Pulp3Error: 429, message=‘Too Many Requests’, url=URL(‘https://registry-1.docker.io/v2/library/alpine/manifests/sha256:41ba0806c6113064dd4cff12212eea3088f40ae23f182763ccc07f430b3a52f8’)

Is there any chance you’ve configured an HTTP proxy in your environment?

@Jonathon_Turel @katello yes, there is. And the connection is successful too. Here’s the screenshot

@Jonathon_Turel @katello I would really appreciate if someone checks this issue. I am in edge of my timeline to complete this task. Happy to join a call if need. siddharthn1096@gmail.com is my ID.

It looks like this was fixed in Katello 4.1 => Bug #32036: "Failed to discover docker repositories because 'Content Default HTTP Proxy' is not used to connect to the registry." - Katello - Foreman. If upgrading isn’t an option for you, you might try:

  • disabling the HTTP proxy in your environment (ie not using it) temporarily to use repo discovery
  • creating the products and repos manually (not using discovery)

@Jonathon_Turel @katello Thanks for the reply Jonathan. I tried adding the repo manually and when I click sync now I’m getting this error
Katello::Errors::Pulp3Error: 429, message=‘Too Many Requests’, url=URL(‘https://registry-1.docker.io/v2/library/alpine/manifests/sha256:41ba0806c6113064dd4cff12212eea3088f40ae23f182763ccc07f430b3a52f8 1’)

Any idea why this is showing like this?
If I add sync tags to a specific one, that works fine. But I’m not able to add all the tags.

Ok, right - ‘Too Many Requests’. I don’t think this is HTTP proxy related then since you’ve clearly made contact to the upstream server which is rate-limiting you.

I found a similar issue reported against pulp → Story #3421: As a plugin writer I have HTTPDownloaders which provide exponential backoff for HTTP 429 errors - Pulp however I think that should be fixed in your version of Katello. Can you share the output of rpm -qa | grep pulp | sort from your server?

Unfortunately I’m not feeling optimistic about getting further with this issue on such an old version of Katello

2 Likes

@Jonathon_Turel @katello This is the output for rpm -qa | grep pulp | sort

pulp-client-1.0-1.noarch
pulpcore-selinux-1.0.0-2.el7.x86_64
pulp-deb-plugins-1.10.2-1.el7.noarch
pulp-docker-plugins-3.2.9-1.el7.noarch
pulp-katello-1.0.3-1.el7.noarch
pulp-puppet-plugins-2.21.5-1.el7.noarch
pulp-puppet-tools-2.21.5-1.el7.noarch
pulp-rpm-plugins-2.21.5-1.el7.noarch
pulp-selinux-2.21.5-1.el7.noarch
pulp-server-2.21.5-1.el7.noarch
python3-pulp-2to3-migration-0.1.0-1.el7.noarch
python3-pulp-container-1.0.0-1.el7.noarch
python3-pulpcore-3.0.1-2.el7.noarch
python3-pulp-file-0.1.1-1.el7.noarch
python-isodate-0.5.0-4.pulp.el7.noarch
python-pulp-common-2.21.5-1.el7.noarch
python-pulp-deb-common-1.10.2-1.el7.noarch
python-pulp-docker-common-3.2.9-1.el7.noarch
python-pulp-oid_validation-2.21.5-1.el7.noarch
python-pulp-puppet-common-2.21.5-1.el7.noarch
python-pulp-repoauth-2.21.5-1.el7.noarch
python-pulp-rpm-common-2.21.5-1.el7.noarch
python-pulp-streamer-2.21.5-1.el7.noarch
tfm-rubygem-pulp_2to3_migration_client-0.1.0-1.el7.noarch
tfm-rubygem-pulp_ansible_client-0.2.0b1.dev0.1560866833-1.el7.noarch
tfm-rubygem-pulp_container_client-1.0.0-1.el7.noarch
tfm-rubygem-pulpcore_client-3.0.0-3.el7.noarch
tfm-rubygem-pulp_file_client-0.1.0-1.el7.noarch
tfm-rubygem-pulp_rpm_client-3.0.0-1.el7.noarch
tfm-rubygem-smart_proxy_pulp-2.0.0-2.fm2_0.el7.noarch

Those versions look correct to me. My advice is to upgrade to Katello 4.0+ as soon as you can as I don’t think we can get any further with Katello 3.15

1 Like

Sounds good. I’ll keep you posted