[AI/ML Pipeline] Always attempt to connect to the cluster

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Component/s: AI/ML
    • None
    • Not Needed

      Summary

      What is the problem or use case, what are we trying to achieve?
      We have occasionally seen certificate verification errors, which could be due to the certificates on the host being out of date or missing.

      In some cases, we are interacting with the cluster during the setup phase to populate collections/indexes when metadata is given, and would see the error there.

      We should make sure that we always attempt to connect to the Atlas server to surface these errors as setup failures.

      Example failure:

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

      [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate 
      

      See also INTPYTHON-781.

            Assignee:
            Unassigned
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: