Description of problem: The namespacewatcher in k8sevents pulls in events from kubernetes within the namespace the mgr is running under. If these events have an improper/non-existent timestamp, the 'ls' command fails when it tries to sort the events. The impact is low, since k8sevents carries on - but it means that from a ceph console you no longer have visibility of pod events within the namespace Version-Release number of selected component (if applicable): OCS 4.2.4 How reproducible: Whenever the k8sevents module is loaded Steps to Reproduce: 1. deploy OCS 2. launch the toolbox and enable the module 3. issue ceph k8sevents ls command Actual results: command fails referring to NoneType and datetime.datetime comparisoon Expected results: ls should show all events in the namespace, sorted - most recent first Additional info:
Jeff?
This one has the blocker flag set for 4.1. Can we ensure this is worked on, moved or closed?
I will review with Paul when he's online.
This is not an issue for RHCS. This is not a regression for Ceph (OCS). The bug does not meet blocker criteria. Moving to 4.1z1.
+1 This is not a blocker for 4.1 Some background; - k8sevents is NOT currently enabled by default in either RHCS or OCS4.x - k8sevents performs two tasks - it sends ceph events (pool created, osd added/removed, pool protection level changed, host added/removed) to the k8s events API(this is the main feature of the module and it's not affected by the bug) - it pulls events from the namespace that the mgr is running in, so at the ceph command line the admin can see k8sevents happening in the namespace. This was a secondary feature, and IS where the bug lies To hit the bug in OCS the user would need to start the toolbox pod, rsh to it, and run the ceph k8sevents ls command. However, this workflow is not exactly normal.
upstream is merged (master) - upstream backport to do downstream packport complete, commit pushed to ceph-4.1-rhel-patches
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3003