OPERATIONAL DEFECT DATABASE
...
...
For any HPE platforms running VMware ESXi 8.0 or 9.0, when using iSUT, any component firmware updates may remain at a pending state in the HPE Integrated Lights-Out (iLO) installation queue. Additionally, iSUT may be unable to reboot the platform after performing the firmware update. As a result, the firmware update will not complete. When iSUT is running in auto-modes, the ramdisk (sut-tmp) will reach full capacity, even though iSUT is not used in deploying firmware or drivers. When this issue occurs, the hostd.log will display the following message: The ramdisk 'sut-tmp' is full. As a result, the /opt/sut/tmp/libhpsrv.debug_1.log file cannot be written. Additionally, the vmkernel.log will display the following messages: Cannot extend visorfs file /opt/sut/tmp/libhpsrv.debug_1.log because its ramdisk (sut-tmp) is full. Admission failure in path: host/system/visorfs/ramdisks/sut-tmp:sut-tmp Note: When using iSUT 6.1.0 and running in any auto-modes, it will fill up the /opt/sut/ directory even if not performing any updates.
In the scenario described above, any HPE platforms running VMware ESXi 8.0 or 9.0, and using iSUT 6.1.0.
To avoid this issue, install iSUT 6.2.0 (or later). If this issue has already occurred, perform either of the following and retry the firmware update: Manually reboot the affected platform. OR SSH into the OS and execute the commands shown below. 1. sut -stop 2. rm /opt/sut/tmp/libhpsrv.debug_1.log 3. sut -start Revision History Document Version Release Date Details 2 August 18, 2025 The Resolution section has been updated with the software version containing the solution. 1 August 05, 2025 Original Document Release.
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
