Review the active process list via your system administration console.
In automated environments (e.g., Ansible playbooks, Terraform, or custom Python scripts using Redfish), implement a to ensure only one firmware operation runs against a given iDRAC at any time. For example:
The SUP0108 error — “A deployment or update operation is already in progress” — is a protective mechanism in Dell iDRAC and Lifecycle Controller that prevents concurrent firmware operations from corrupting your server’s configuration. While frustrating, it is almost always resolvable by clearing the job queue via RACADM or the Redfish API.
racadm jobqueue delete -i JID_CLEARALL_FORCE
to:
The underlying architecture of Dell iDRAC and the Lifecycle Controller relies on sequential processing. To protect the server's motherboard and components from catastrophic failure during a firmware write, the system creates lockfiles and sets tasks into a job queue.
When this issue strikes, it completely blocks subsequent firmware installations, updates, or driver mounts, leaving IT environments vulnerable to missing vital system optimization and safety patches. Why the SUP0108 Error Occurs
Sometimes, the system just needs 15–30 minutes to realize a process has stalled and auto-terminate the lock.
Do you have to the underlying database? Share public link Review the active process list via your system
Log into the iDRAC web interface and navigate to: (or Configuration → Job Queue depending on your iDRAC version). Review the list of jobs. If you find a job stuck in a “Pending” or “Running” state, cancel it directly from the GUI. Once the queue is clear, retry your update.
Do not attempt random fixes. Follow the sequence: Verify → Wait → Inspect → Resolve → Validate.
A previous firmware update failed or timed out during package transfer, leaving a phantom task active in the iDRAC database.
Unplug from the server's Power Supply Units (PSUs). While frustrating, it is almost always resolvable by
A corrupted WSUS database often causes ghost operations. Run the cleanup of ConfigMgr.
If the error persists due to a stuck lockfile on the RAM drive, a full power cycle (unplugging the server for 30 seconds) will force a clean state.
Wait 15 to 30 minutes if you suspect a large package is genuinely processing. 2. Clear the System Cache and Lock State