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

[Core] Launching on a just launched existing cluster with --fast does not skip the provision #4460

Open
Michaelvll opened this issue Dec 11, 2024 · 2 comments · May be fixed by #4463
Open
Assignees

Comments

@Michaelvll
Copy link
Collaborator

To reproduce:

  1. sky launch -c test-fast --cloud aws --cpus 2 echo hi
  2. sky launch -c test-fast --fast echo hi: does not skip provisioning
  3. sky launch -c test-fast --fast echo hi: skips the provisioning

Version & Commit info:

  • sky -v: PLEASE_FILL_IN
  • sky -c: PLEASE_FILL_IN
@cg505 cg505 self-assigned this Dec 11, 2024
@cg505
Copy link
Collaborator

cg505 commented Dec 11, 2024

provider.availability_zone in the cluster yaml changes from initial launch (lists all zones) to second and all future launches (only lists the zone that the cluster is actually in)

I will add a mechanism to ignore some fields from the cluster yaml for the config hash calculation. Was trying to avoid that but I think its the best way to go.

@concretevitamin
Copy link
Member

@cg505 cg505 linked a pull request Dec 11, 2024 that will close this issue
3 tasks
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

Successfully merging a pull request may close this issue.

3 participants