-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
aws-ovn-serial-1of2 aws-ovn-techpreview-serial-2of3 failed on:
: [sig-mco][OCPFeatureGate:ManagedBootImagesAWS][Serial] Should update
boot images only on MachineSets that are opted in
[apigroup:machineconfiguration.openshift.io]
[Suite:openshift/conformance/serial]
{ fail [github.com/openshift/origin/test/extended/machine_config/boot_image_update_agnostic.go:52]: Unexpected error:
<*fmt.wrapError | 0xc00708c5a0>:
Error running oc label machinesets.machine.openshift.io ci-op-82qp9743-26a0e-bgdfm-worker-us-east-1d -n openshift-machine-api test=boot:
StdOut>
Error from server (Forbidden): admission webhook "validation.machineset.machine.openshift.io" denied the request: providerSpec.blockDevices[0].ebs.throughputMib: Invalid value: 0: must be a value between 125 and 2000
StdErr>
Error from server (Forbidden): admission webhook "validation.machineset.machine.openshift.io" denied the request: providerSpec.blockDevices[0].ebs.throughputMib: Invalid value: 0: must be a value between 125 and 2000
exit status 1
The issue is introduced by https://github.com/openshift/machine-api-operator/pull/1430 .
Dig more, found there is no throughput setting on 4.21.0-0.nightly-2025-11-25-103346. The root cause is https://github.com/openshift/installer/pull/9945 set providerSpec.blockDevices[0].ebs.throughputMib to `0` by default. When users run some operation against the machineset resource, the validation rejected the operation.