Description of problem:
The packages api updated to support the old and new api versions and group. After that change, the `list` operation on packages stopped emitting correct list metadata. Kubectl ignores this problem and displays correctly, but console breaks without this meatadata in place. The symptom is that no UI for operatorhub is displayed in the cluster.
Steps to Reproduce:
1. Go to OperatorHub UI
No packages visible
See operator packages
Fix PR here: https://github.com/operator-framework/operator-lifecycle-manager/pull/791
Fix is merged.
No avaialbe payload for the bug verification, 4.0.0-0.nightly-2019-03-29-040459 can't be installed success.
I think a root of confusion here is that there are multiple release payloads. This bug is about the OCP payload, which is different from what CI uses.
I think the ART promotion to machine-os-content went into the OCP stream, which is what this bug is about.
That's a good catch. There may be two issues we're tracking here:
1. The content generated by ART is not what we expected
2. The OCP stream has a copy of the content which is not expected
At this point things should be in working order once more.
We can get the OperatorHub UI now, but there are two problems:
1) there is a dividing line between the "Installed Operators" and the "Operator Hub" on the UI.
2) Click the "Catalog"->"Operator Hub", and pull the scroll bar to the bottom, but it will go back to the top automatically.
[jzhang@dhcp-140-18 ocp42]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.nightly-2019-04-02-081046 True False 133m Cluster version is 4.0.0-0.nightly-2019-04-02-081046
The OLM version:
For the 2nd issue I described in comment 24, it only occurs on the Safari browser, it works well on the Chrome and Firefox.
For the 1st issue I mentioned, I guess it's as designed for the permission restriction. Correct me if I'm wrong.
Thanks for your information! I see, for issues in comment 24, I created bug 1695446 to trace it.
For this bug, I'd like to verify it. Thanks!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.