Back to bug 1853638
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2020-07-03 12:26:31 UTC | Keywords | FutureFeature | |
| Ashish Singh | 2020-07-11 04:31:17 UTC | CC | assingh | |
| Mudit Agarwal | 2020-11-04 15:50:40 UTC | CC | muagarwa | |
| Red Hat Bugzilla | 2020-11-04 15:50:40 UTC | Doc Type | If docs needed, set a value | No Doc Update |
| Nimrod Becker | 2020-11-19 11:08:40 UTC | CC | ebenahar | |
| Nimrod Becker | 2021-01-19 09:33:59 UTC | Flags | needinfo?(nberry) | |
| Nimrod Becker | 2021-03-04 13:13:17 UTC | Blocks | 1931936 | |
| CC | rohgupta | |||
| Nimrod Becker | 2021-04-05 12:32:34 UTC | CC | owasserm | |
| Flags | needinfo?(owasserm) | |||
| Nimrod Becker | 2021-04-05 12:53:41 UTC | CC | mmanjuna | |
| Orit Wasserman | 2021-04-11 07:56:50 UTC | Flags | needinfo?(nberry) needinfo?(owasserm) | |
| Nimrod Becker | 2021-04-18 06:53:12 UTC | CC | aclewett | |
| Nimrod Becker | 2021-06-30 17:59:04 UTC | Status | NEW | POST |
| Link ID | Github noobaa/noobaa-operator/pull/672 | |||
| Nimrod Becker | 2021-08-04 14:08:52 UTC | Status | POST | MODIFIED |
| Nimrod Becker | 2021-08-08 06:54:50 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | v4.9.0-51.ci | |||
| Mudit Agarwal | 2021-08-16 07:40:02 UTC | Doc Type | No Doc Update | Enhancement |
| Elad | 2021-08-22 13:50:00 UTC | QA Contact | ratamir | amagrawa |
| Rejy M Cyriac | 2021-09-26 16:56:45 UTC | CC | rcyriac | |
| RHEL Program Management | 2021-09-26 16:56:54 UTC | Target Release | --- | OCS 4.9.0 |
| Rejy M Cyriac | 2021-09-26 21:07:26 UTC | Target Release | OCS 4.9.0 | --- |
| Rejy M Cyriac | 2021-09-26 21:11:49 UTC | Product | Red Hat OpenShift Container Storage | Red Hat OpenShift Data Foundation |
| Component | Multi-Cloud Object Gateway | Multi-Cloud Object Gateway | ||
| RHEL Program Management | 2021-09-26 21:28:02 UTC | Target Release | --- | ODF 4.9.0 |
| Neha Berry | 2021-09-28 10:17:42 UTC | QA Contact | amagrawa | belimele |
| Ben Eli | 2021-09-30 10:50:08 UTC | Flags | needinfo?(nbecker) | |
| CC | nbecker | |||
| Nimrod Becker | 2021-09-30 11:13:33 UTC | Flags | needinfo?(nbecker) | |
| Ben Eli | 2021-09-30 13:44:13 UTC | Status | ON_QA | VERIFIED |
| Mudit Agarwal | 2021-11-03 04:17:34 UTC | Blocks | 2011326 | |
| Nimrod Becker | 2021-11-16 13:41:16 UTC | Doc Text | Feature: Enable movement of Core and DB pods when a node fails. Reason: Kubernetes / OCP does not mark a node disconnected on a node failure unless it was chosen to be deleted. This means that stateful sets are not automatically evicted on such noded. Result: With this enhancement, the DB and Core pods (which are stateful sets) will be evicted and moved to a new node on a node failure |
|
| Kusuma | 2021-11-25 15:03:43 UTC | CC | kbg | |
| Doc Text | Feature: Enable movement of Core and DB pods when a node fails. Reason: Kubernetes / OCP does not mark a node disconnected on a node failure unless it was chosen to be deleted. This means that stateful sets are not automatically evicted on such noded. Result: With this enhancement, the DB and Core pods (which are stateful sets) will be evicted and moved to a new node on a node failure | .Enable movement of Core and DB pods when a node fails Previously, when a node failed, OpenShift Container Platform would not mark the node as disconnected unless it was deleted. As a result, Core and DB pods, which are the statefulsets are not automatically evicted on such failed nodes. With this enhancement, when a node fails, the DB and Core pods are evicted and moved to a new node. | ||
| Flags | needinfo?(nbecker) | |||
| Nimrod Becker | 2021-11-25 15:05:32 UTC | Flags | needinfo?(nbecker) | |
| Doc Text | .Enable movement of Core and DB pods when a node fails Previously, when a node failed, OpenShift Container Platform would not mark the node as disconnected unless it was deleted. As a result, Core and DB pods, which are the statefulsets are not automatically evicted on such failed nodes. With this enhancement, when a node fails, the DB and Core pods are evicted and moved to a new node. | .Enable movement of Core and DB pods when a node fails When a node fails, OpenShift Container Platform would not mark the node as disconnected unless it was deleted. As a result, Core and DB pods, which are the statefulsets are not automatically evicted on such failed nodes. With this enhancement, when a node fails, the DB and Core pods are evicted and moved to a new node. |
||
| Kusuma | 2021-12-09 01:13:53 UTC | Doc Text | .Enable movement of Core and DB pods when a node fails When a node fails, OpenShift Container Platform would not mark the node as disconnected unless it was deleted. As a result, Core and DB pods, which are the statefulsets are not automatically evicted on such failed nodes. With this enhancement, when a node fails, the DB and Core pods are evicted and moved to a new node. | .Movement of Core and DB pods is enabled when a node fails OpenShift Container Platform does not mark the node as disconnected unless it is deleted. As a result, Core and DB pods, which are the statefulsets are not automatically evicted on such failed nodes. With this update, when a node fails, the DB and Core pods are evicted and moved to a new node. |
| errata-xmlrpc | 2021-12-13 15:17:27 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2021-12-13 17:44:23 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2021-12-13 17:44:23 UTC | |||
| errata-xmlrpc | 2021-12-13 17:44:44 UTC | Link ID | Red Hat Product Errata RHSA-2021:5086 | |
| Prasad Desala | 2022-02-04 07:56:12 UTC | CC | tdesala | |
| Link ID | Github red-hat-storage/ocs-ci/pull/4966/ | |||
| Elad | 2023-08-09 16:49:53 UTC | CC | odf-bz-bot |
Back to bug 1853638