Hi, the duplicated bug is closed at NotBug which just said to wait a moment and do not say the exact plan to finish migration. So, I can not count on that bug to track the issue. And because our some cases are blocked, I reopen it to request migration plan, like when it will be finished. Thanks
Sorry, I think Dan's comments were a little unclear. In the comments of the bugzilla he listed, there is a pointer to jira that describes the current state of this: https://projects.engineering.redhat.com/browse/CLOUDBLD-2313 It's a fairly massive endeavor for the pipelines, but is absolutely expected. Their plan is to have this completed, since the publishing of these operators into the new catalog is outside the scope of openshift's source or feature freeze.
Hi Kevin, Thanks for the information. https://projects.engineering.redhat.com/browse/CLOUDBLD-2313 is resolved now, and it handles redhat-operator-index, not community operators index. currently after we setup 4.6 cluster, we still do not get community operators. Could you please know where to track community operator index? I change it to New again, and you could close it after we clarify the tracking method for community operators. Thanks