Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6554

Flaky: OIDC k8s failing due to pod being killed [1]

XMLWordPrintableJSON

    • Type: Icon: Build Failure Build Failure
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None

      https://spruce.mongodb.com/task/mongo_node_driver_next_ubuntu20_test_all_oidc_oidc_auth_test_k8s_latest_gke_4bc3e500b6f0e8ab01f052c4a1bfb782d6a29b4e_f168e1328f821bbda265e024cc91ae54_24_11_18_15_37_24/logs?execution=0

       

      [2024/11/19 09:55:48.870] > mongodb@6.10.0 check:oidc-k8s
[2024/11/19 09:55:48.870] > mocha --config test/mocha_mongodb.json test/integration/auth/mongodb_oidc_k8s.prose.07.test.ts
[2024/11/19 09:56:01.344] command terminated with exit code 137
[2024/11/19 09:56:01.344] Command 'subprocess.exec' (step 2 of 2) failed: process encountered problem: exit code 137.

      Note that exit code 137 indicates pod is being killed, potentially due to OOM (out of memory), but could be due to some other external signal (https://stackoverflow.com/a/59764016)

            Assignee:
            Unassigned Unassigned
            Reporter:
            warren.james@mongodb.com Warren James
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: