Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-6328

Installing of CLO v6 stays pending when LFME instance is not deleted from RHOL v5

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Before this changes, errors would occur during upgrades to version 6.0 if a Log File Metric Exporter instance was present. This update resolves the issue, allowing upgrades to proceed smoothly without errors.
    • Bug Fix

      Description of problem:

      When trying to install CLO v6 , the csv of the operator goes into pending state due to schema change halting the new version installation

      Error in the Image attached 

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

      RHOL 6

      How reproducible:

      Steps to Reproduce:

      1. Deploy a cluster with RHOL v5.9
      2. Create CL and LFME instance
      3. Now uninstall CLO version 5.9 and try to CLO version 6
      4. The operator installation is stalled with error in the subscription page.

      Actual results:

      CSV in pending operator installation incomplete.

      Expected results:

      Operator operator should be completed correctly

      Additional info:

        1. Screenshot 2024-09-29 at 12.49.05.png
          Screenshot 2024-09-29 at 12.49.05.png
          64 kB

            [LOG-6328] Installing of CLO v6 stays pending when LFME instance is not deleted from RHOL v5

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Logging for Red Hat OpenShift - 5.8.15), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHBA-2024:10052

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Logging for Red Hat OpenShift - 5.8.15), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2024:10052

            Anping Li added a comment -

            Verified using cluster-logging.v5.8.15.

            cluster-logging.v5.8.15 can be upgraded to cluster-logging.v6.0.2 without error when LFME is running.

            Anping Li added a comment - Verified using cluster-logging.v5.8.15. cluster-logging.v5.8.15 can be upgraded to cluster-logging.v6.0.2 without error when LFME is running.

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in merge request !4599 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.8-rhel-9_upstream_bfa771660c06dc670dd26d4b9ce2c5c4:

            Updated US source to: 12cab7d LOG-6201: avoid empty Reason and Message fields in Ready Condition

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in merge request !4599 of openshift-logging / Log Collection Midstream on branch openshift-logging-5.8-rhel-9_ upstream _bfa771660c06dc670dd26d4b9ce2c5c4 : Updated US source to: 12cab7d LOG-6201 : avoid empty Reason and Message fields in Ready Condition

            Jeffrey Cantrill added a comment -

            This issue requires Release Notes Text. Please modify the Release Note Text or set the Release Note Type to "Release Note Not Required"

            Jeffrey Cantrill added a comment - This issue requires Release Notes Text. Please modify the Release Note Text or set the Release Note Type to "Release Note Not Required"

              vparfono Vitalii Parfonov
              rhn-support-ssonigra Sonigra Saurab
              Anping Li Anping Li
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: