## Definition of Triaged/triaged Adding the triaged label to a jira bug is meant to imply that: * No more information is needed from the reporter * That its a valid bug and needs to be fixed * (ideally, but not required) you’ve got an idea why the bug is happening ## Catagorized bug list ### packageserver * [SNO packageserver CSV unknown state during installation](https://issues.redhat.com/browse/OCPBUGS-5044): set priority as Minor * [3 node packageserver CSV in unknown state during upgrade](https://issues.redhat.com/browse/OCPBUGS-5885) * [packageserver CSV stuck in Installing during OCP 4.8.z to 4.9.z upgrade](https://issues.redhat.com/browse/OCPBUGS-4893) ### catalogSource registry pods not managed by any workload API * [OLM's catalogsource pods cause a need to manually force drain a worker to reboot](https://issues.redhat.com/browse/OCPBUGS-6062). Note: DanS had a PR open for this, that is now closed. Looks worth looking into to see if we can pick that PR up and continue. * [CatalogSource reports READY, but pod not present](https://issues.redhat.com/browse/OCPBUGS-6523) ### resolver cache * [State installed CSV entries in the resolver cache](https://issues.redhat.com/browse/OCPBUGS-5080) * [Operator cannot be upgraded with the error "Cannot update: CatalogSource was removed" while CatalogSource exists](https://issues.redhat.com/browse/OCPBUGS-6773) ### fbc * [as of 4.11.z opm render does not use REGISTRY_AUTH_FILE while opm index does](https://issues.redhat.com/browse/OCPBUGS-5845) * Another [OLM pods causing CPU utilization on master nodes](https://issues.redhat.com/browse/OCPBUGS-7128)