Operate First Support cases list

[tumido]

For tracking purposes, let's keep a list of support cases opened by Operate First:

• [x] Timeouts in monitoring dashboards
• [x] Permanently silencing an alert via inhibit rules?
• [x] OCS operator stuck in "pending" state, errors showing up in event stream
• [x] Storage is in "warning" state, but we can't figure out why
• [x] Noobaa management console reports "high number of issues"
• [x] Unable to authenticate to openshift api; web console not available
• [x] PersistentVolumeClaims getting stuck in "pending" state
• [x] Console ui is unavailable
• [x] pods failing to start because "CNI request failed with status 400...failed to get pod annotation"
• [x] ACM failing to install baremetal cluster: no nodes defined in Ironic
• [x] ACM baremetal install fails: "Error: could not fetch data from user_data_url"
• [x] Problems adding additional bare metal nodes to cluster
• [x] OCS cluster in HEALTH_WARN state after node failure
• [x] Bare metal failing to complete 4.7.0 -> 4.7.2 upgrade
• [x] Update of bare metal cluster from 4.7.0 to 4.7.2 is stuck after updating controllers
• [x] Bare metal node became "NotReady", high load from kubelet
• [x] Stalled upgrade from 4.7.2 to 4.7.7 due to machine config failing to apply
• [ ] Poor performance for OCS storage
• [x] Unable to create ObjectBucketClaims on Noobaa StorageClass
• [x] How do we get an alert when the api certificate is about to expire?
• [ ] nodenetworkconfigurationpolicy failing to apply
• [ ] Failed ACM/baremetal install (ocp 4.7)
• [ ] Noobaa object storage is unresponsive; noobaa core is logging RPC errors
• [ ] https://access.redhat.com/support/cases/#/case/03229640

[sesheta]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[tumido]

/remove-lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/support/issues/745): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.