Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-1653

KubeletLog intervals can have null locator keys

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • None
    • False

      This shouldn't be possible, it should have a locator pointing to node it's from.

          {
            "level": "Info",
            "display": false,
            "source": "KubeletLog",
            "locator": {
              "type": "",
              "keys": null
            },
            "message": {
              "reason": "ReadinessFailed",
              "cause": "",
              "humanMessage": "Get \"https://10.177.121.252:6443/readyz\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)",
              "annotations": {
                "node": "ci-op-vxiib4hx-9e8b4-wwnfx-master-2",
                "reason": "ReadinessFailed"
              }
            },
            "from": "2024-05-02T16:58:06Z",
            "to": "2024-05-02T16:58:06Z",
            "filename": "e2e-events_20240502-163726.json"
          },
      

            rhn-engineering-dgoodwin Devan Goodwin
            rhn-engineering-dgoodwin Devan Goodwin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: