Upgrading a disconnected OCP 4 cluster got stuck with Insights Operator degraded

Solution Verified - Updated -

Issue

  • When upgrading an OpenShift Container Platform cluster with Insights Operator degraded, the upgrade will stuck and will not finish properly.
  • Insights Operator is degraded in a restricted network OCP cluster.
  • The following error is shown in the insights pod:

    insightsclient.go:180] Unable to build a request, possible invalid token: Post "https://cloud.redhat.com/api/ingress/v1/upload": dial tcp: i/o timeout
    
  • The Insights Cluster Operator show the following message:

    Message:               Unable to report: unable to build request to connect to Insights server: Post "https://cloud.redhat.com/api/ingress/v1/upload": dial tcp 10.0.0.1:443: i/o timeout
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Disconnected cluster
  • Insights operator

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