Back to bug 2178619
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Orit Wasserman | 2023-03-15 14:05:22 UTC | CC | owasserm | |
| Nitin Goyal | 2023-03-16 11:57:01 UTC | Link ID | Github red-hat-storage/odf-operator/pull/301 | |
| Status | NEW | POST | ||
| krishnaram Karthick | 2023-03-16 12:53:45 UTC | CC | kramdoss | |
| OpenShift BugZilla Robot | 2023-03-16 12:56:49 UTC | Link ID | Github red-hat-storage/odf-operator/pull/302 | |
| OpenShift BugZilla Robot | 2023-03-16 14:22:54 UTC | Status | POST | MODIFIED |
| RHEL Program Management | 2023-03-25 07:28:36 UTC | Target Release | --- | ODF 4.13.0 |
| errata-xmlrpc | 2023-04-04 13:00:01 UTC | Status | MODIFIED | ON_QA |
| Sunil Kumar Acharya | 2023-04-10 12:22:18 UTC | CC | nigoyal | |
| Flags | needinfo?(nigoyal) | |||
| Nitin Goyal | 2023-04-10 12:43:54 UTC | Doc Text | Previously, odf-operator's sub-dependencies' Subscriptions were created with old/stale/non-existent ownerReferences when the odf-operator Subscription was deleted and recreated. This caused a hotloop of creation, deletion, and re-creation of the sub-dependencies' Subscriptions, leaving the entire ocs-consumer/provider stack in an unresolved state. The issue was due to odf-operator-controller-manager caching the metadata.uid of the odf-operator Subscription and using it to create/reconcile sub-dependency Subscriptions instead of getting the latest odf-operator Subscription present in the cluster. This issue has been addressed in the current release by removing the cache, ensuring that the latest odf-operator Subscription is used to create/reconcile sub-dependency Subscriptions. | |
| Flags | needinfo?(nigoyal) | |||
| Elad | 2023-04-25 05:58:28 UTC | QA Contact | ebenahar | nberry |
| Neha Berry | 2023-04-28 13:15:59 UTC | QA Contact | nberry | ikave |
| Itzhak | 2023-05-29 14:56:45 UTC | Flags | needinfo?(ykukreja) needinfo?(nigoyal) | |
| Nitin Goyal | 2023-05-30 04:48:19 UTC | Flags | needinfo?(nigoyal) | |
| Sunil Kumar Acharya | 2023-06-01 15:29:09 UTC | Blocks | 2154341 | |
| Itzhak | 2023-06-01 16:40:12 UTC | Status | ON_QA | VERIFIED |
| Mudit Agarwal | 2023-06-02 11:32:19 UTC | Doc Text | Previously, odf-operator's sub-dependencies' Subscriptions were created with old/stale/non-existent ownerReferences when the odf-operator Subscription was deleted and recreated. This caused a hotloop of creation, deletion, and re-creation of the sub-dependencies' Subscriptions, leaving the entire ocs-consumer/provider stack in an unresolved state. The issue was due to odf-operator-controller-manager caching the metadata.uid of the odf-operator Subscription and using it to create/reconcile sub-dependency Subscriptions instead of getting the latest odf-operator Subscription present in the cluster. This issue has been addressed in the current release by removing the cache, ensuring that the latest odf-operator Subscription is used to create/reconcile sub-dependency Subscriptions. | |
| Blocks | 2154341 | |||
| Itzhak | 2023-06-08 13:45:11 UTC | Keywords | AutomationTriaged | |
| errata-xmlrpc | 2023-06-21 14:41:57 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-21 15:24:39 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-06-21 15:24:39 UTC | |||
| errata-xmlrpc | 2023-06-21 15:25:57 UTC | Link ID | Red Hat Product Errata RHBA-2023:3742 | |
| Elad | 2023-08-09 17:00:26 UTC | CC | odf-bz-bot |
Back to bug 2178619