It looks like the order in which the channels are being returned via the GetPackage GRPC API in the FBC catalog is non-deterministic, whereas they appeared either in lexicographical ascending order or registry add <bundle> order (not sure which). This results in various clients to display the channels in a random order, whereas they were being displayed in a seemingly-sorted order before (e.g. the OpenShift Console).
We have a large catalog. We just converted it from sqlite to fbc: FBC:
icr.io/cpopen/ibm-operator-catalog:latest
SQLITE:
icr.io/cpopen/ibm-operator-catalog:sqlite-latest
It looks like the order in which the channels are being returned via the GetPackage GRPC API in the FBC catalog is non-deterministic, whereas they appeared either in lexicographical ascending order or
registry add <bundle>
order (not sure which). This results in various clients to display the channels in a random order, whereas they were being displayed in a seemingly-sorted order before (e.g. the OpenShift Console).To reproduce:
vs the sqlite version: