Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error applying Kueue CRDs on MacOS #9

Open
danielvegamyhre opened this issue Nov 7, 2023 · 1 comment
Open

Error applying Kueue CRDs on MacOS #9

danielvegamyhre opened this issue Nov 7, 2023 · 1 comment

Comments

@danielvegamyhre
Copy link
Collaborator

danielvegamyhre commented Nov 7, 2023

(I will update this bug with more information to help reproduce this issue later)

Environment: MacOS

Command:

python xpk.py cluster create --cluster xpk-test --tpu-type=v4-16 --num-slices 1 --cluster-cpu-machine-type=n1-standard-8

Everything works as expected until we start applying the Kueue CRDs here.

[XPK] Starting xpk
...
[XPK] Task: `Set Kueue On Cluster` terminated with code `0`
[XPK] Enable Kueue CRDs
[XPK] Try 1: Applying Kueue CRDs
[XPK] Task: `Applying Kueue CRDs` is implemented by `kubectl apply -f 3`, streaming output live.
[XPK] Waiting for `Applying Kueue CRDs`, for 0 seconds
[XPK] Waiting for `Applying Kueue CRDs`, for 1 seconds
error: the path "3" does not exist

As you can see, the temporary file name generated ("3") seems to be invalid/garbage.

When running this same command on Linux, it works, and we see the following log line:

[XPK] Task: `Applying Kueue CRDs` is implemented by `kubectl apply -f /tmp/tmppwercgir, streaming output live.

This shows a valid temporary filename in the expected location, /tmp.

Right now, my hunch is it is one of the following:

A) There is a discrepancy in the way the tempfile package creates/handles/ temporary files on MacOS vs Linux.
B) Perhaps this is a weird manifestation of a permissions issue.
C) Some discrepancy in Python version being used, or version of tempfile package being used.

@rwitten
Copy link
Collaborator

rwitten commented Nov 10, 2023

Great bug report. I think we should just check if we're on Mac and refuse to run -- we can't test than environment and we can't deliver an A+ experience there (the docker create and uploads will similarly be degraded on a dev's laptop).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants