What steps did you take and what happened?
Tried to create a windows VM with an all-digit name.
It failed during the customize step because the computerName is not allowed to be all digits.
A specified parameter was not correct: spec.identity.userData.computerName
What did you expect to happen?
I expected the webhook validator to reject the request, similar if I try with capital letters/special characters/starting or ending with hyphen.
Is there anything else you would like to add?
Please tell us about your environment.
|
Value |
How to Obtain |
| Supervisor version |
VMware-wcp-0.1.10-24098299.x86_64 |
rpm -qa VMware-wcp on the vCenter appliance |
| Supervisor node image version |
VMware-wcpovf-4.0.636-24098300.x86_64 |
rpm -qa VMware-wcpovf on the vCenter appliance |
| Kubernetes version |
v1.29.3+vmware.wcp.1 |
kubectl version |
| VM Operator version |
0.1.0-97aa976-1.8.6-dcf635df-24093626 |
kubectl -n vmware-system-vmop get pods \
-ojsonpath='{range .items[*].spec.containers[*]}{.image}{"\n"}{end}' | \
sort -u | \
grep vmop | \
awk -F'/' '{print $3}' | \
awk -F: '{print $2}' |
What steps did you take and what happened?
Tried to create a windows VM with an all-digit name.
It failed during the customize step because the computerName is not allowed to be all digits.
What did you expect to happen?
I expected the webhook validator to reject the request, similar if I try with capital letters/special characters/starting or ending with hyphen.
Is there anything else you would like to add?
Please tell us about your environment.
VMware-wcp-0.1.10-24098299.x86_64rpm -qa VMware-wcpon the vCenter applianceVMware-wcpovf-4.0.636-24098300.x86_64rpm -qa VMware-wcpovfon the vCenter appliancev1.29.3+vmware.wcp.1kubectl version0.1.0-97aa976-1.8.6-dcf635df-24093626