Fix operand phase error for Elasticsearch in OperandRequest

[YCShen1010]

Issue: https://github.ibm.com/IBMPrivateCloud/roadmap/issues/63588#issuecomment-80838597

Enhancement:

• If the operator is not managed by ODLM, it will set the operatorPhase to Failed instead.
• Clean up the phase value of OperandRequest and of each operand member at the beginning of each opreq reconciliation.

How to test

image: quay.io/yuchen_shen/odlm:operand_phase

• Before applying the fix image:
  • request ibm-elasticsearch-operator
  • remove label and annotation in elasticsearch subscription:

    operator.ibm.com/opreq-control: 'true'
    cs-condition.example-service.ibm-elasticsearch-operator/request: v1.1
    

  • obverse operand phase failed in OperandRequest, even there is no operand for elasticsearch

    members:
     - name: ibm-elasticsearch-operator
       phase:
         operandPhase: Failed
    phase: Failed

• Applying the fix image:
  • will see the error changes to operator failed (Assume the removed label and annotation are not added back at this time)

    members:
     - name: ibm-elasticsearch-operator
       phase:
         operatorPhase: Failed
    phase: Failed

  • add above label back to the subscription operator.ibm.com/opreq-control: 'true'
  • OperandRequest phase status is back to Running with

    members:
     - name: ibm-elasticsearch-operator
       phase:
         operatorPhase: Running
    phase: Running

[Daniel-Fan]

/lgtm

[ibm-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Daniel-Fan, YCShen1010

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Daniel-Fan,YCShen1010]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment