Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2352

cbopinfo generates files with creation time of epoch date

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 2.1.0, 2.2.0, 2.2.1
    • not-targeted
    • operator
    • None
    • 1

    Description

      It looks like each file contained within a cbopinfo is created with a creation time of the epoch (1st Jan 1970)

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          simon.murray Simon Murray added a comment -

          How's this a bug?  Has it stopped you or I being able to diagnose customer issues in 4 years?  Pedantry my friend, pedantry.

          simon.murray Simon Murray added a comment - How's this a bug?  Has it stopped you or I being able to diagnose customer issues in 4 years?  Pedantry my friend, pedantry.
          tim.bradgate Tim Bradgate added a comment -

          More of an issue for the tooling which uses the file created time to determine when the logs were collected. Am cheating and using the filename as it has the timestamp in it, but this probably isn't the most desirable behaviour either way

          tim.bradgate Tim Bradgate added a comment - More of an issue for the tooling which uses the file created time to determine when the logs were collected. Am cheating and using the filename as it has the timestamp in it, but this probably isn't the most desirable behaviour either way
          simon.murray Simon Murray added a comment -

          Why not just ask for the timestamp to be included in the metadata (which as you point out would just be a duplicate of the filename)?  That's a constant at least as of v2.2?  You cannot depend on the file content of the archive, with the exception of that file.  To be true to reality, if I was going to add ctime, mtime and atime I'd probably use time.Now() as it is, so that cannot be trusted either (but it does give some indication of tooling performance).

          simon.murray Simon Murray added a comment - Why not just ask for the timestamp to be included in the metadata (which as you point out would just be a duplicate of the filename)?  That's a constant at least as of v2.2?  You cannot depend on the file content of the archive, with the exception of that file.  To be true to reality, if I was going to add ctime, mtime and atime I'd probably use time.Now() as it is, so that cannot be trusted either (but it does give some indication of tooling performance).
          tim.bradgate Tim Bradgate added a comment -

          Using the filename will do for my purposes there's no immediate action item needed here, but thought I'd raise this for awareness in case it was something we wanted to change for future releases to be analogous to the other log collection scripts

          tim.bradgate Tim Bradgate added a comment - Using the filename will do for my purposes there's no immediate action item needed here, but thought I'd raise this for awareness in case it was something we wanted to change for future releases to be analogous to the other log collection scripts
          simon.murray Simon Murray added a comment -

          Hey, at least you get an ISO8601 date, with timezone!

          simon.murray Simon Murray added a comment - Hey, at least you get an ISO8601 date, with timezone!
          tim.bradgate Tim Bradgate added a comment -

          I never said I was complaining

          tim.bradgate Tim Bradgate added a comment - I never said I was complaining
          simon.murray Simon Murray added a comment -

          If we wanted to be proper clever dicks, then we could even use

          metadata:
            creationTimestamp: "2021-08-13T14:00:57Z

          to drive the file ctimes... options options!  But I think that's just over complication, the contents matter not the file itself

          simon.murray Simon Murray added a comment - If we wanted to be proper clever dicks, then we could even use metadata: creationTimestamp: "2021-08-13T14:00:57Z to drive the file ctimes... options options!  But I think that's just over complication, the contents matter not the file itself

          People

            simon.murray Simon Murray
            tim.bradgate Tim Bradgate
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty