Open WoosukKwon opened 2 years ago
Nice catch @WoosukKwon! Wdyt about leaving the unsupported VM types out of the catalog for now? This way users can get a nicer "VM type not found/supported" error.
In the future we can also consider adding a CLI that shows all supported VM types by looking into the catalogs.
@concretevitamin Sounds good. Then I think we can keep E2 and only remove t2a and f1-micro VMs. WDYT?
@concretevitamin Sounds good. Then I think we can keep E2 and only remove t2a and f1-micro VMs. WDYT?
Sounds good.
@concretevitamin Added the filter in PR #1004.
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This issue was closed because it has been stalled for 10 days with no activity.
Related to #3066
I tested the provisioning of the GCP VMs which will be added in the new GCP catalog (see their specs in https://cloud.google.com/compute/docs/machine-types):
Among theses, I failed to get on-demand E2, on-demand/spot T2A, and on-demand/spot f1-micro. Here are the error messages:
On-demand E2 (note that I could get a spot E2 instance though)
On-demand/spot T2A (same errors)
on-demand/spot f1-micro (no response after the head node is up)
We may have to test and document the unsupported machine types.