Back to bug 1944009
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Matt Benjamin (redhat) | 2021-03-29 13:25:18 UTC | Status | NEW | ASSIGNED |
| CC | ivancich | |||
| Assignee | mbenjamin | ivancich | ||
| Flags | needinfo?(ivancich) | |||
| Gaurav Sitlani | 2021-03-29 14:00:50 UTC | CC | gsitlani | |
| J. Eric Ivancich | 2021-04-13 20:26:00 UTC | Flags | needinfo?(ivancich) | needinfo?(mbenjamin) |
| J. Eric Ivancich | 2021-04-14 17:07:28 UTC | Flags | needinfo?(mbenjamin) | |
| J. Eric Ivancich | 2021-04-14 20:21:31 UTC | Comment 3 is private | 1 | 0 |
| J. Eric Ivancich | 2021-04-14 20:49:00 UTC | Status | ASSIGNED | POST |
| Veera Raghava Reddy | 2021-04-24 18:18:10 UTC | CC | vereddy | |
| Ken Dreyer (Red Hat) | 2021-04-30 22:07:14 UTC | CC | kdreyer | |
| Link ID | Github ceph/ceph/pull/40862 | |||
| Red Hat One Jira (issues.redhat.com) | 2021-06-02 19:05:03 UTC | Link ID | Red Hat Issue Tracker RHCEPH-217 | |
| Ken Dreyer (Red Hat) | 2021-10-05 21:24:48 UTC | Fixed In Version | ceph-16.2.6-1.el8cp | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2021-10-05 21:45:46 UTC | Status | MODIFIED | ON_QA |
| Madhavi Kasturi | 2021-11-12 14:39:11 UTC | CC | mkasturi | |
| Red Hat Bugzilla | 2021-12-09 06:35:29 UTC | CC | sweil | |
| Aron Gunn | 2022-01-12 22:27:28 UTC | CC | agunn | |
| Blocks | 2031073 | |||
| Tejas | 2022-01-25 07:09:01 UTC | QA Contact | tchandra | vimishra |
| Aron Gunn | 2022-01-25 19:46:27 UTC | Docs Contact | agunn | |
| Flags | needinfo?(ivancich) | |||
| Vidushi Mishra | 2022-02-07 05:30:08 UTC | Status | ON_QA | VERIFIED |
| J. Eric Ivancich | 2022-02-14 18:06:17 UTC | Doc Text | Feature: Normal/expected lock contention during resharding is no longer logged to imply there's an error. Instead those log entries are now tagged with "INFO:". Reason: Customers were concerned when reviewing their RGW logs that there was a problem with RGW when normal/expected log contention was underway. Result: We expect that because "INFO:" is contained in the log messages, customers will now view them as only informational. | |
| Flags | needinfo?(ivancich) | |||
| Doc Type | If docs needed, set a value | Enhancement | ||
| Ranjini M N | 2022-02-16 09:10:13 UTC | Doc Text | Feature: Normal/expected lock contention during resharding is no longer logged to imply there's an error. Instead those log entries are now tagged with "INFO:". Reason: Customers were concerned when reviewing their RGW logs that there was a problem with RGW when normal/expected log contention was underway. Result: We expect that because "INFO:" is contained in the log messages, customers will now view them as only informational. | .The message for Ceph Object Gateway log during reshard is informational Previously, when the Ceph Object Gateway failed to get a lock on a reshard log, it would like an error due to which the customers were concerned when reviewing their Ceph Object Gateway logs that there was a problem with normal/expectant log contention was underway. With this release, the messages are more informational instead of an error message and are logged as “INFO:” |
| CC | rmandyam | |||
| Flags | needinfo?(ivancich) | |||
| J. Eric Ivancich | 2022-02-16 20:38:58 UTC | Flags | needinfo?(ivancich) | needinfo?(rmandyam) |
| Ranjini M N | 2022-02-17 11:36:34 UTC | Doc Text | .The message for Ceph Object Gateway log during reshard is informational Previously, when the Ceph Object Gateway failed to get a lock on a reshard log, it would like an error due to which the customers were concerned when reviewing their Ceph Object Gateway logs that there was a problem with normal/expectant log contention was underway. With this release, the messages are more informational instead of an error message and are logged as “INFO:” | .Lock contention messages from the Ceph Object Gateway reshard queue are marked as informational Previously, when the Ceph Object Gateway failed to get a lock on a reshard queue, the output log entry would appear to be an error causing concern to customers. With this release the entries in the output log appear as informational and are tagged as “INFO:”. |
| Flags | needinfo?(rmandyam) | |||
| Aron Gunn | 2022-02-21 17:29:30 UTC | Docs Contact | agunn | rmandyam |
| Ranjini M N | 2022-03-09 09:33:44 UTC | Doc Text | .Lock contention messages from the Ceph Object Gateway reshard queue are marked as informational Previously, when the Ceph Object Gateway failed to get a lock on a reshard queue, the output log entry would appear to be an error causing concern to customers. With this release the entries in the output log appear as informational and are tagged as “INFO:”. | .Lock contention messages from the Ceph Object Gateway reshard queue are marked as informational Previously, when the Ceph Object Gateway failed to get a lock on a reshard queue, the output log entry would appear to be an error causing concern to customers. With this release, the entries in the output log appear as informational and are tagged as “INFO:”. |
| J. Eric Ivancich | 2022-03-09 19:31:26 UTC | CC | ivancich | |
| errata-xmlrpc | 2022-04-04 08:00:32 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-04-04 10:19:55 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-04-04 10:19:55 UTC | |||
| errata-xmlrpc | 2022-04-04 10:20:14 UTC | Link ID | Red Hat Product Errata RHSA-2022:1174 |
Back to bug 1944009