Back to bug 1847685

Who When What Removed Added
Prasad Desala 2020-06-18 10:51:57 UTC CC tdesala
Depends On 1846989
Neha Ojha 2020-06-19 00:43:25 UTC Status NEW ASSIGNED
Link ID Github ceph/ceph/pull/34542
Yaniv Kaul 2020-06-25 12:25:52 UTC Blocks 1846989
Depends On 1846989
Yaniv Kaul 2020-07-12 11:40:23 UTC Dependent Products Red Hat OpenShift Container Storage
Josh Durgin 2020-07-15 15:43:09 UTC Keywords CodeChange
Veera Raghava Reddy 2020-07-20 20:11:41 UTC CC vereddy
Prashant Dhange 2020-07-29 00:20:26 UTC CC pdhange
Prashant Dhange 2020-07-30 06:43:47 UTC Link ID Red Hat Knowledge Base (Solution) 5254921
Neha Ojha 2020-08-03 16:47:55 UTC CC mkasturi
Scott Ostapovicz 2020-08-05 14:59:24 UTC CC sostapov
Mike Hackett 2020-08-06 15:21:05 UTC CC mhackett
Josh Durgin 2020-08-06 15:46:47 UTC Status ASSIGNED POST
errata-xmlrpc 2020-08-07 04:50:19 UTC Status POST MODIFIED
CC tserlin
Fixed In Version ceph-14.2.8-90.el8cp, ceph-14.2.8-90.el7cp
Target Milestone z2 z1
Status MODIFIED ON_QA
Mudit Agarwal 2020-08-13 06:43:55 UTC CC muagarwa
Aron Gunn 2020-08-17 15:16:58 UTC CC agunn
Docs Contact agunn
Flags needinfo?(nojha)
Neha Ojha 2020-08-17 17:10:09 UTC Doc Text Cause: The use of some kernels and/or hardware can trigger a monotonic clock that goes back in time.

Consequence: This can lead to a negative monotonic
time span, which can trigger an assert in the monitors.

Fix: Tolerate this case and interpret
it as a 0-length interval and not a negative value.

Result: No crash seen on the monitors due to this assert.
Doc Type If docs needed, set a value Bug Fix
Flags needinfo?(nojha)
Aron Gunn 2020-08-17 19:05:00 UTC Doc Text Cause: The use of some kernels and/or hardware can trigger a monotonic clock that goes back in time.

Consequence: This can lead to a negative monotonic
time span, which can trigger an assert in the monitors.

Fix: Tolerate this case and interpret
it as a 0-length interval and not a negative value.

Result: No crash seen on the monitors due to this assert.
.Ceph Monitors can crash due to a negative time span

Previously, Ceph Monitors could crash when triggered by a monotonic clock going back in time. These crashes caused a negative monotonic time span and triggered an assertion into the Ceph Monitor leading them to crash. The Ceph Monitor code was updated to tolerate this assertion and interprets it as a zero-length interval and not a negative value. As a result, the Ceph Monitor does not crash when this assertion is made.
Aron Gunn 2020-08-17 19:05:53 UTC Doc Text .Ceph Monitors can crash due to a negative time span

Previously, Ceph Monitors could crash when triggered by a monotonic clock going back in time. These crashes caused a negative monotonic time span and triggered an assertion into the Ceph Monitor leading them to crash. The Ceph Monitor code was updated to tolerate this assertion and interprets it as a zero-length interval and not a negative value. As a result, the Ceph Monitor does not crash when this assertion is made.
.Crashing Ceph Monitors caused by a negative time span

Previously, Ceph Monitors could crash when triggered by a monotonic clock going back in time. These crashes caused a negative monotonic time span and triggered an assertion into the Ceph Monitor leading them to crash. The Ceph Monitor code was updated to tolerate this assertion and interprets it as a zero-length interval and not a negative value. As a result, the Ceph Monitor does not crash when this assertion is made.
Aron Gunn 2020-08-17 20:56:23 UTC Blocks 1816167
Hideshi Fukumoto 2020-08-18 22:41:30 UTC CC hfukumot
errata-xmlrpc 2020-08-19 17:26:31 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2020-08-19 19:50:24 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2020-08-19 19:50:24 UTC
errata-xmlrpc 2020-08-19 19:50:36 UTC Link ID Red Hat Product Errata RHBA-2020:3524
Yaniv Kaul 2020-12-03 09:46:11 UTC Blocks 1903969

Back to bug 1847685