Back to bug 2073209
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Neha Ojha | 2022-04-07 22:01:07 UTC | Assignee | nojha | gfarnum |
| Target Release | 6.1 | 5.2 | ||
| Red Hat One Jira (issues.redhat.com) | 2022-04-07 22:02:12 UTC | Link ID | Red Hat Issue Tracker RHCEPH-3951 | |
| Raghavendra Talur | 2022-04-19 14:48:24 UTC | Flags | needinfo?(gfarnum) | |
| Vikhyat Umrao | 2022-04-25 23:27:11 UTC | Status | NEW | ASSIGNED |
| Greg Farnum | 2022-04-28 02:20:53 UTC | Flags | needinfo?(gfarnum) | |
| Neha Ojha | 2022-05-19 21:20:50 UTC | Flags | needinfo?(gfarnum) | |
| Red Hat Bugzilla | 2022-05-26 08:30:57 UTC | CC | ngangadh | |
| CC | ceph-qe-bugs | |||
| Niels de Vos | 2022-05-27 09:10:34 UTC | Link ID | Red Hat Issue Tracker RHSTOR-2994 | |
| Dependent Products | Red Hat OpenShift Data Foundation | |||
| Greg Farnum | 2022-06-01 05:23:13 UTC | Flags | needinfo?(gfarnum) | |
| Status | ASSIGNED | POST | ||
| errata-xmlrpc | 2022-06-01 07:41:05 UTC | Status | POST | MODIFIED |
| CC | tserlin | |||
| Fixed In Version | ceph-16.2.8-27.el8cp | |||
| Status | MODIFIED | ON_QA | ||
| Greg Farnum | 2022-06-28 16:55:33 UTC | Fixed In Version | ceph-16.2.8-27.el8cp | ceph-16.2.8-30.el8cp |
| Flags | needinfo?(gfarnum) | |||
| Flags | needinfo?(gfarnum) | |||
| Pawan | 2022-07-05 16:31:01 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2022-07-06 08:19:44 UTC | CC | akraj | |
| Flags | needinfo?(gfarnum) | |||
| Blocks | 2102272 | |||
| Docs Contact | akraj | |||
| Greg Farnum | 2022-07-06 23:06:47 UTC | Doc Text | Feature: It is now possible to blocklist a CIDR range, in addition to individual client instances and IPs. Reason: In some circumstances, you may want to blocklist all clients in an entire data center or rack (for instance, when failing over a workload to a different set of machines and wanting to prevent the old workload instance from continuing to partially operate), instead of specifying individual clients to blocklist. Result: This is now possible using a "blocklist range" analogous to the existing "blocklist" command. | |
| Flags | needinfo?(gfarnum) | |||
| Akash Raj | 2022-07-13 07:27:47 UTC | Doc Text | Feature: It is now possible to blocklist a CIDR range, in addition to individual client instances and IPs. Reason: In some circumstances, you may want to blocklist all clients in an entire data center or rack (for instance, when failing over a workload to a different set of machines and wanting to prevent the old workload instance from continuing to partially operate), instead of specifying individual clients to blocklist. Result: This is now possible using a "blocklist range" analogous to the existing "blocklist" command. | .Users can now blocklist a CIDR range With this release, you can blocklist a CIDR range, in addition to individual client instances and IPs. In certain circumstances, you would want to blocklist all clients in an entire data center or rack instead of specifying individual clients to blocklist. For example, failing over a workload to a different set of machines and wanting to prevent the old workload instance from continuing to partially operate. This is now possible using a "blocklist range" analogous to the existing "blocklist" command. |
| Flags | needinfo?(gfarnum) | |||
| Greg Farnum | 2022-07-21 13:27:22 UTC | Flags | needinfo?(gfarnum) | |
| errata-xmlrpc | 2022-08-09 09:58:38 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:38:20 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-08-09 17:38:20 UTC | |||
| errata-xmlrpc | 2022-08-09 17:38:54 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2073209