ACM successfully deployed in one cluster and other cluster fails with git clone issue

Solution Verified - Updated -

Issue

  • We found an issue with deploying an application through ACM where one cluster is able to deploy and the other cluster fails with GIT clone, even though both clusters have the same cluster proxy.

    I0203 21:14:54.043747       1 git_subscriber_item.go:273] exit doSubscription: redhat-acm-test/redhat-acm-test-subscription-1
    E0203 21:14:54.043755       1 git_subscriber_item.go:160] Failed to clone git: https://redhat-acm-test/application.git err: Get "https://redhat-acm-test/application.git/info/refs?service=git-upload-pack": context deadline exceeded (Client.Timeout exceeded while awaiting headers)Subscription error.
    I0203 21:14:54.043763       1 git_subscriber_item.go:161] mark appsub (redhat-acm-test/redhat-acm-test-subscription-1) as failed with reason: Failed to clone git: https://redhat-acm-test/application.git err: Get "https://redhat-acm-test/application.git/info/refs?service=git-upload-pack": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    

Environment

  • Red Hat Advanced Cluster Management for Kubernetes 2.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content