Found in the lab run: pve-redfish runs with ProtectSystem=strict, so it could not write its firmware state and dropped the reset request that applies a staged BIOS. Tested end to end on the lab: iDRAC profile multipart BMC update, iLO profile pull of BMC and BIOS through rack controller pxe-rack2 with -reboot, model check and -force, resume of a running update across a region restart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
23 lines
539 B
Desktop File
23 lines
539 B
Desktop File
[Unit]
|
|
Description=pve-redfish Redfish service for Proxmox VM %i (lab BMC driver tests)
|
|
After=network-online.target pve-vbmc-addrs.service
|
|
Wants=network-online.target
|
|
Requires=pve-vbmc-addrs.service
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStart=/usr/local/bin/pve_redfish.py --config /etc/pve-vbmc/config.json --vmid %i
|
|
Restart=always
|
|
RestartSec=3
|
|
AmbientCapabilities=CAP_NET_BIND_SERVICE
|
|
User=pve-vbmc
|
|
StateDirectory=pve-vbmc
|
|
Group=pve-vbmc
|
|
NoNewPrivileges=yes
|
|
ProtectSystem=strict
|
|
ProtectHome=yes
|
|
PrivateTmp=yes
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|