Dagster k8s job run fails sql connection, but works from command line. about dagster HOT 3 CLOSED

More info here. Looks like kerberos is correctly setup in the dagster run container.
I added this code to dagster, a URL that needs windows credentials, and works correct.
`try:
# Construct the curl command
cmd = ["curl", "--negotiate", "-u", ":", "-O", url]

    # Open a subprocess to execute the curl command
    curl_process = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
    curl_output, curl_error = curl_process.communicate()

    # Check for success or failure based on the return code
    if curl_process.returncode == 0:
        context.log.info("Curl request successful")
    else:
        context.log.info(f"Curl request failed. Error: {curl_error.decode()}")
except Exception as e:
    context.log.info(f"An error occurred: {e}")`

Still, i have no idea what is happening with pyodbc / dagster together.
can i add more verbosity the whole process?

from dagster.

Hi, i tried to isolate the problem, and the issue is on dagster, not kerberos or pyodbc or sql provider.

I deploy a code location with Dagster Helm. i have a an asset called "Test" with a 10 minutes timeout, so i can launch the pod and connect to the pod.
Connected to the "dagster-run" pod, i check that kerberos is correct.
Then i run:
dagster asset materialize --select test-from-cmd -f assets.py

and the connection to SQL Server via Windows auth is correct!!!.

Im in a point that i dont understand whey this does work if i run the same assets from the web UI?

from dagster.

So, happily i will close the ticket.
The reason why is not working on my current setup (dagster 1.6.1, python version, kerberos libraries, OS libraries, etc) it can be multiple. But due to the nature of dagster running jobs on multiprocess.spawn, this can cause many problems in the way kerberos works and how tickets can be used between multiple threads. That can explain why pyodbc/sql driver/kerberos always worked when submitting dagster jobs from command line.

I run tests on debian and alpine python3.11 and it didnt work.
However, with redhat/ubi9:python3.11 all works perfectly.

i close the issue.

from dagster.