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
Please include the bosh deploy... command, including all the operations files (plus any experimental operation files you're using):
N/A
Please provide output that helps describe the issue:
Task 34
Task 34 | 20:37:07 | Error: Instance group 'nats' references an unknown vm type 'medium'
Task 34 Started Sun Sep 8 20:37:07 UTC 2024
Task 34 Finished Sun Sep 8 20:37:07 UTC 2024
Task 34 Duration 00:00:00
Task 34 error
What IaaS is this issue occurring on?
N/A
Is there anything else unique or special about your setup?
No.
Tag your pair, your PM, and/or team!
It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.
The text was updated successfully, but these errors were encountered:
Sorry, I figured that the infrastructure was immaterial. I'm developing a new CPI for LXD. After not finding the medium VM size, I noticed the release indicating medium was v43, so I just dropped down to the latest of v42. Deployment worked fine, so that was my immediate goal.
It will be appreciated once the medium size gets documented.
What is this issue about?
In your own words, describe the issue.
What steps/actions led to the issue?
I tried to deploy the latest version of CF using the existing documentation (specifically: https://github.com/cloudfoundry/cf-deployment/blob/main/texts/on-cloud-configs.md#vm-types).
Deployment errors because VM type
medium
does not exist.Side note: I like the table setup, for example, that exists for OpenStack -- especially since it suggests the ephemeral disk size. (see: https://github.com/cloudfoundry/cf-deployment/blob/main/iaas-support/openstack/README.md)
The
medium
VM doesn't appear to be in any example cloud-configs either.What version of cf-deployment are you using?
v43.1.0
Please include the
bosh deploy...
command, including all the operations files (plus any experimental operation files you're using):N/A
Please provide output that helps describe the issue:
What IaaS is this issue occurring on?
N/A
Is there anything else unique or special about your setup?
No.
Tag your pair, your PM, and/or team!
It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.
The text was updated successfully, but these errors were encountered: