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
1.6603249394315164e+09 ERROR controllers.Server failed to check power state {"server": "/009d38f7-264d-ea11-8397-a4bf0164f174", "error": "run /usr/sbin/ipmitool ipmitool -H 172.30.223.79 -U sidero -I lanplus -E -p 623 raw 0x00 0x01: Error in open session response message : insufficient resources for session\n\nError: Unable to establish IPMI v2 / RMCP+ session\n (exit status 1)"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
/.cache/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:114
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/.cache/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:311
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/.cache/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/.cache/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:227
Checking the documentation, these BMCs since 2016 require the "17" cipher.
Trying out the invocation in the pod without (fails) and with (succeeds).
[root@dill04 test (⎈|admin@workload:default)]# kubectl --context admin@bootstrap exec -n sidero-system sidero-controller-manager-7554d4b757-874hn -it -c manager -- /usr/sbin/ipmitool -I lanplus -H 172.30.223.79 -U root -P foo -p 623 raw 0x00 0x01
Error in open session response message : insufficient resources for session
Error: Unable to establish IPMI v2 / RMCP+ session
command terminated with exit code 1
[root@dill04 test (⎈|admin@workload:default)]# kubectl --context admin@bootstrap exec -n sidero-system sidero-controller-manager-7554d4b757-874hn -it -c manager -- /usr/sbin/ipmitool -I lanplus -H 172.30.223.79 -U root -P foo -p 623 -C 17 raw 0x00 0x01
00 10 40 70
The version of ipmitool in the sidero image and my shell environment are the same, but I don't need to include the -C 17 in my shell environment. So, not sure why my shell version seems to be able to auto detect but the sidero image version does not.
The text was updated successfully, but these errors were encountered:
On Intel S2600WF hardware with updated BMC et al:
Checking the documentation, these BMCs since 2016 require the "17" cipher.
Trying out the invocation in the pod without (fails) and with (succeeds).
The version of ipmitool in the sidero image and my shell environment are the same, but I don't need to include the -C 17 in my shell environment. So, not sure why my shell version seems to be able to auto detect but the sidero image version does not.
The text was updated successfully, but these errors were encountered: