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

OperatorHub UI shows Operator Channels in random order for FBC Catalogs

XMLWordPrintable

    • Low
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Before this update, the channels of some Operators were displayed on OperatorHub in a random order. With this update, Operator channels are displayed in lexicographical order.
      (link:https://issues.redhat.com/browse/OCPBUGS-7910[*OCPBUGS-7910*])
      Show
      * Before this update, the channels of some Operators were displayed on OperatorHub in a random order. With this update, Operator channels are displayed in lexicographical order. (link: https://issues.redhat.com/browse/OCPBUGS-7910 [* OCPBUGS-7910 *])
    • Bug Fix
    • Done

      Description of problem:

      Any FBC enabled OLM Catalog displays the Channels in a random order.

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a catalog source for icr.io/cpopen/ibm-operator-catalog:latest
2. Navigate to OperatorHub
3. Click on the `ibm-mq` operator
4. Click on the Install button.

      Actual results:

      The list of channels is in random order. The order changes with each page refresh.

      Expected results:

      The list of channels should be in lexicographical ascending order as it was for SQLITE based catalogs.

      Additional info:

      See related operator-registry upstream issue:
https://github.com/operator-framework/operator-registry/issues/1069#top

Note:  I think both `operator-registry` and the OperatorHub should provide deterministic sorting of these channels.

              agreene1991 Alexander Greene (Inactive)
              cdjohnson-cpeng Chris Johnson (Inactive)
              Jian Zhang Jian Zhang
              Michael Peter Michael Peter
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: