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

TALM cli state is not correct when cgu is enabled after backup

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.12.0
    • TALM Operator
    • None
    • CNF RAN Sprint 232, CNF RAN Sprint 233, CNF RAN Sprint 234
    • 3
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      CGU printercolumn state shows wrong condition. The order of conditions is not correct.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1. create disable cgu with enabled backup
      2. enable cgu after back up is done
      

      Actual results:

      conditions:
        - lastTransitionTime: "2023-02-08T13:56:20Z"
          message: Policy remediation took too long
          reason: TimedOut
          status: "False"
          type: Progressing
        - lastTransitionTime: "2023-02-08T09:56:14Z"
          message: Backup is completed for all clusters
          reason: BackupCompleted
          status: "True"
          type: BackupSuceeded

      Expected results:

        - lastTransitionTime: "2023-02-08T09:56:14Z"
          message: Backup is completed for all clusters
          reason: BackupCompleted
          status: "True"
          type: BackupSuceeded
        - lastTransitionTime: "2023-02-08T13:56:20Z"
          message: Policy remediation took too long
          reason: TimedOut
          status: "False"
          type: Progressing

      Additional info:

      https://redhat-internal.slack.com/archives/C02EG99MR9C/p1675846320946689
      previous attempt to fix:https://github.com/openshift-kni/cluster-group-upgrades-operator/pull/352

            saskari@redhat.com Saeid Askari
            saskari@redhat.com Saeid Askari
            Joshua Clark Joshua Clark
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: