Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-32709

Reconciliation errors are not reflected on LVMCluster CR status

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • Moderate
    • No
    • None
    • None
    • OCPEDGE Sprint 253, OCPEDGE Sprint 254
    • 2
    • In Progress
    • Bug Fix
    • Hide
      Previously, reconciliation failures were only logged in the operator pod logs, and the state of the `LVMCluster` custom resource (CR) was not affected. This issue makes it difficult to track failures through status conditions. With this fix, the `ResourcesAvailable` and `VolumeGroupsReady` conditions have been added to reflect the reconciliation status and volume group conditions. These conditions determine the state and readiness of the `LVMCluster` CR, providing users with better visibility into reconciliation failures directly through status conditions.
      Show
      Previously, reconciliation failures were only logged in the operator pod logs, and the state of the `LVMCluster` custom resource (CR) was not affected. This issue makes it difficult to track failures through status conditions. With this fix, the `ResourcesAvailable` and `VolumeGroupsReady` conditions have been added to reflect the reconciliation status and volume group conditions. These conditions determine the state and readiness of the `LVMCluster` CR, providing users with better visibility into reconciliation failures directly through status conditions.
    • None
    • None
    • None
    • None

      Description of problem:

      LVMCluster CR status does not have conditions to reflect the reconciliation errors from lvm operator so one needs to check the operator logs to see if there are any errors. Also, these errors do not have an effect on the readiness of the CR.

              sakbas@redhat.com Suleyman Akbas
              sakbas@redhat.com Suleyman Akbas
              None
              None
              Rahul Deore Rahul Deore
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: