We encountered some issues with operator metadata build recently, and we just fixed some of those issues.
https://github.com/openshift/doozer/pull/175 and https://github.com/openshift/doozer/pull/178 were merged and deployed to buildvm. Not sure if all issues with operator metadata build are solved. Triggered another build and watching...
FYI internal JIRA tracker https://issues.redhat.com/browse/ART-1534
All PRs merged. Waiting for a new operator metadata build.
We can get a more fresher nightly operator builds now. $ oc rsh qe-app-registry-66ffd998b4-25w26 sh-4.2$ cat downloaded/local-storage-operator/local-storage-operator-abqeayzh/local-storage-operator.package.yaml channels: - currentCSV: local-storage-operator.4.2.19-202002101212 name: '4.2' - currentCSV: local-storage-operator.4.3.2-202002112006 name: '4.3' - currentCSV: local-storage-operator.4.2.19-202002101212-s390x name: 4.2-s390x - currentCSV: local-storage-operator.4.4.0-202002110930 name: '4.4' defaultChannel: '4.4' packageName: local-storage-operator
This should have been closed with the 4.4 GA release.