After upgrading some Elasticsearch deployments and pods are missed in OCP 4

Solution Verified - Updated -

Issue

  • After upgrading some Elasticsearch pods are missed
  • After upgrading some Elasticsearch deployments were deleted
  • After upgrading, some Elasticsearch deployments are missed and the error in the Elasticsearch Operator is:

    nodes:
    - deploymentName: elasticsearch-cdm-xxxxx-1
      upgradeStatus:
        upgradePhase: controllerUpdated
    - deploymentName: elasticsearch-cdm-xxxxx-2
      upgradeStatus:
        upgradePhase: controllerUpdated
    - conditions:
      - lastTransitionTime: "2020-08-20T11:24:58Z"
        message: '0/13 nodes are available: 2 Insufficient memory, 2 node(s) had volume node affinity conflict, 3 node(s) were unschedulable, 6 node(s) didn''t match node selector.'
        reason: Unschedulable
        status: "True"
        type: Unschedulable
      deploymentName: elasticsearch-cdm-xxxxx-3
      upgradeStatus:
        upgradePhase: controllerUpdated
    

Environment

  • Red Hat OpenShift Container Platform
    • 4.4
    • 4.5

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