Translated message

A translation of this page exists in English.

OpenShift 4 の Ingress Operator で発生する CanaryChecksRepetitiveFailures のトラブルシューティング

Solution In Progress - Updated -

Issue

  • ingress operator が degraded 状態になり、ingress operator の Pod に以下のエラーが表示されるため、OpenShift 4 のアップグレードプロセスが停止します。

    ERROR    operator.canary_controller    wait/wait.go:155    error performing canary route check    {"error": "error sending canary HTTP Request: Timeout: Get \"http://canary-openshift-ingress-canary.apps.<domain>\": dial tcp $IP:80: i/o timeout (Client.Timeout exceeded while awaiting headers)"}
    INFO    operator.ingress_controller    controller/controller.go:244    reconciling    {"request": "openshift-ingress-operator/default"}
    
  • ingress operator が degraded 状態になり、ingress clusteroperator に以下のエラーが表示されるため、OCP 4 のアップグレードプロセスが停止します。

    ingresscontroller "default" is degraded: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=False (CanaryChecksRepetitiveFailures: Canary route checks for the default ingress controller are failing)
    

Environment

  • Red Hat Openshift Container Platform (RHOCP)
    • 4
  • Ingress Operator
  • Canary

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