Reconciler error: failed to set PXE boot one for server: failed to set the boot orde r: 400

[clyann]

@damyan

Got a reconciler error after manually adding a new endpoint for this hardware:

Manufacturer: GIGABYTE
Model: R282-P91-00

This is the error:

2024-11-27T16:37:56Z ERROR Reconciler error {"controller": "server", "controllerGroup": "metal.ironcore.dev", "controllerKind": "Server", "Server": {"name":"compute3-system-0"}, "namespace": "", "name": "compute3-system-0", "reconcileID": "1f4c9db2-186f-43b2-a100-f9178acc72ea", "error": "failed to ensure server state transition: failed to set PXE boot for server: failed to set PXE boot one for server: failed to set the boot order: 400: {"error":{"@Message.ExtendedInfo":[{"@odata.type":"#Message.v1_0_8.Message","Message":"Support of this Operation for Boot Properties is moved to FutureState URI(/redfish/v1/Systems/Self/SD)","MessageArgs":["Boot","/redfish/v1/Systems/Self/SD"],"MessageId":"Ami.1.0.OperationSupportedInFutureStateURI","RelatedProperties":["/Boot"],"Resolution":"Repeat the operation on FutureState(SD) URI for applying these changes","Severity":"Critical"}],"code":"Ami.1.0.OperationSupportedInFutureStateURI","message":"Support of this Operation for Boot Properties is moved to FutureState URI(/redfish/v1/Systems/Self/SD)"}}"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:316
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:263
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:224

This is the metal-operator deployment (removed private identifiers):

Name: metal-operator-controller-manager-85d69878b7-c597s
Namespace: metal-operator-system
Priority: 0
Service Account: metal-operator-controller-manager
Node:
Start Time: Wed, 27 Nov 2024 16:26:05 +0000
Labels: control-plane=controller-manager
pod-template-hash=85d69878b7
Annotations: kubectl.kubernetes.io/default-container: manager
Status: Running
IP:
IPs:
IP:
Controlled By: ReplicaSet/metal-operator-controller-manager-85d69878b7
Containers:
manager:
Container ID: containerd://df012b341e069d09e1c6f6758ce834195946b9b4930e025ec4616c3155dfe630
Image: ghcr.io/ironcore-dev/metal-operator-controller-manager@sha256:89ece1e6a8f47cee38ec48e7247e79317ec0da6c9f08714978faab01e469a845
Image ID: ghcr.io/ironcore-dev/metal-operator-controller-manager@sha256:89ece1e6a8f47cee38ec48e7247e79317ec0da6c9f08714978faab01e469a845
Port:
Host Port:
Command:
/manager
Args:
--leader-elect
--mac-prefixes-file=/etc/macdb/macdb.yaml
--probe-image=ghcr.io/ironcore-dev/metalprobe:latest
--probe-os-image=core.harbor.onmetal.de/onmetal/gardenlinux:1592.2
--insecure=false
--registry-url=http://[]:30010
State: Running
Started: Wed, 27 Nov 2024 16:26:08 +0000
Ready: True
Restart Count: 0
Limits:
cpu: 300m
memory: 200Mi
Requests:
cpu: 300m
memory: 50Mi
Liveness: http-get http://:8081/healthz delay=15s timeout=1s period=20s #success=1 #failure=3
Readiness: http-get http://:8081/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
Environment:
Mounts:
/etc/macdb/ from macdb (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-d9l5x (ro)
kube-rbac-proxy:
Container ID: containerd://bfffca572512aa8e5c384187110d08d4bfb18408a4146368ad2f9b586f7908de
Image: gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0
Image ID: gcr.io/kubebuilder/kube-rbac-proxy@sha256:d8cc6ffb98190e8dd403bfe67ddcb454e6127d32b87acc237b3e5240f70a20fb
Port: 8443/TCP
Host Port: 8443/TCP
Args:
--secure-listen-address=0.0.0.0:8443
--upstream=http://127.0.0.1:8080/
--logtostderr=true
--v=0
State: Running
Started: Wed, 27 Nov 2024 16:26:08 +0000
Ready: True
Restart Count: 0
Limits:
cpu: 500m
memory: 128Mi
Requests:
cpu: 5m
memory: 64Mi
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-d9l5x (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
macdb:
Type: Secret (a volume populated by a Secret)
SecretName: macdb-6b98k27hk7
Optional: false
kube-api-access-d9l5x:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 23m default-scheduler Successfully assigned metal-operator-system/metal-operator-controller-manager-85d69878b7-c597s to ...
Normal Pulling 23m kubelet Pulling image "ghcr.io/ironcore-dev/metal-operator-controller-manager@sha256:89ece1e6a8f47cee38ec48e7247e79317ec0da6c9f08714978faab01e469a845"
Normal Pulled 23m kubelet Successfully pulled image "ghcr.io/ironcore-dev/metal-operator-controller-manager@sha256:89ece1e6a8f47cee38ec48e7247e79317ec0da6c9f08714978faab01e469a845" in 2.388s (2.388s including waiting). Image size: 26785072 bytes.
Normal Created 23m kubelet Created container manager
Normal Started 23m kubelet Started container manager
Normal Pulled 23m kubelet Container image "gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0" already present on machine
Normal Created 23m kubelet Created container kube-rbac-proxy
Normal Started 23m kubelet Started container kube-rbac-proxy