You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When launching a managed job where the controller is on k8s, there is no spinner showing up after the job is submitted, which feels like the system is hanging. However, sky jobs logs --controller does show that the job cluster is being launched.
$ sky jobs launch test.yaml --cloud aws --cpus 2 -n test-mount-bucketTask from YAML spec: test.yamlManaged job 'test-mount-bucket' will be launched on (estimated):Considered resources (1 node):---------------------------------------------------------------------------------------- CLOUD INSTANCE vCPUs Mem(GB) ACCELERATORS REGION/ZONE COST ($) CHOSEN ---------------------------------------------------------------------------------------- AWS m6i.large 2 8 - us-east-1 0.10 ✔ ----------------------------------------------------------------------------------------Launching a managed job 'test-mount-bucket'. Proceed? [Y/n]: ⚙︎ Translating workdir and file_mounts with local source paths to SkyPilot Storage... Workdir: 'examples' -> storage: 'skypilot-filemounts-vscode-47fbf511'. Folder : 'examples' -> storage: 'skypilot-filemounts-vscode-47fbf511'. Created S3 bucket 'skypilot-filemounts-vscode-47fbf511' in us-east-1 Excluded files to sync to cluster based on .gitignore.✓ Storage synced: examples -> s3://skypilot-filemounts-vscode-47fbf511/ View logs at: ~/sky_logs/sky-2025-01-30-23-32-05-747700/storage_sync.log Excluded files to sync to cluster based on .gitignore.✓ Storage synced: examples -> s3://skypilot-filemounts-vscode-47fbf511/ View logs at: ~/sky_logs/sky-2025-01-30-23-32-12-937934/storage_sync.log✓ Uploaded local files/folders.Launching managed job 'test-mount-bucket' from jobs controller...Warning: Credentials used for [GCP, AWS] may expire. Clusters may be leaked if the credentials expire while jobs are running. It is recommended to use credentials that never expire or a service account.⚙︎ Mounting files. Syncing (to 1 node): /tmp/managed-dag-test-mount-bucket-ksc7nx8g -> ~/.sky/managed_jobs/test-mount-bucket-c2d4.yaml Syncing (to 1 node): /tmp/tmp3j5i1vru -> ~/.sky/managed_jobs/test-mount-bucket-c2d4.config_yaml✓ Files synced. View logs at: ~/sky_logs/sky-2025-01-30-23-32-19-231465/file_mounts.logAuto-stop is not supported for Kubernetes and RunPod clusters. Skipping.⚙︎ Job submitted, ID: 2
The text was updated successfully, but these errors were encountered:
When launching a managed job where the controller is on k8s, there is no spinner showing up after the job is submitted, which feels like the system is hanging. However,
sky jobs logs --controller
does show that the job cluster is being launched.The text was updated successfully, but these errors were encountered: