QRadar — Applications Issues:
stuck install task state

1. Identify the symptom

In QRadar Console, open Admin → Extensions Management and attempt the required application or content-pack operation. The operation is rejected with an error similar to:

Another preview/install/uninstall task is currently in progress. Please try again later.

The message can remain even when the UI does not show an active preview, install, or uninstall operation. IBM documents this failure pattern when a previous app or content-pack install/removal failed and left a conflicting entry in the content-management database.

2. Why QRadar blocks the next operation

Extension Management checks the current records in the content_package table before starting another operation. A previously failed or interrupted task can leave a row in a state that QRadar treats as conflicting. The result is a stale task-state blocker rather than necessarily an app process that is still visibly running.

Do not assume a specific status from the error text alone. Inspect the current records and compare the state with the QRadar status lookup table before making a change.

3. Find the conflicting content-package records

SSH to the QRadar Console as root through your approved administration path. Run IBM's diagnostic query to return entries whose status is not one of the usual terminal states:

psql -U qradar -c "SELECT hub_id, content_status, id
FROM content_package
WHERE content_status NOT IN (3, 6, 9);"

Review every returned row, especially the hub_id, numeric status, and record id. More than one record can block the next operation; record each candidate ID and confirm that it belongs to a failed or abandoned task before resetting anything.

To view the status names configured on the appliance, run:

psql -U qradar -c "SELECT * FROM content_status;"

4. Interpret the status values correctly

The status codes matter here: 5 and 6 do not mean “In Progress” and “Failed.” In IBM's documented lookup, 5 is INSTALL_FAILED and 6 is UNINSTALLED.

Use the results from your own system as the source of truth if the status lookup differs by release. Do not change rows that represent a legitimate operation in progress.

5. Back up the content-package table

Before running an update, create the backup directory and export the table. Confirm that /store has enough space and that the resulting backup file exists.

mkdir -p /store/IBM_Support/

pg_dump -U qradar -t content_package --inserts \
  -f "/store/IBM_Support/content_package.sql-$(date +%F)"

Check the command's exit status and inspect the backup file before proceeding. If the backup fails or storage is low, stop and resolve that issue first.

6. Reset only the confirmed stale record

IBM's documented recovery sets the specific conflicting record's content_status to 6 (UNINSTALLED). Replace APP_ID with the ID you identified from the diagnostic query. This is a targeted database correction, not a general-purpose way to repair arbitrary app statuses.

psql -U qradar -c "UPDATE content_package
SET content_status = 6
WHERE id = 'APP_ID';"

For example, if IBM's diagnostic identifies the confirmed stale record with ID 601, the update is:

psql -U qradar -c "UPDATE content_package
SET content_status = 6
WHERE id = '601';"

7. Verify the state and retry the operation

Repeat the diagnostic query:

psql -U qradar -c "SELECT hub_id, content_status, id
FROM content_package
WHERE content_status NOT IN (3, 6, 9);"

For the documented issue, no rows should remain that block the operation. If other rows are returned, inspect them individually rather than resetting them automatically.

1. Clear the browser cache or open a fresh private browser session.
2. Return to Admin → Extensions Management.
3. Retry the required install or uninstall operation.
4. Confirm that the operation finishes, then check the package/app state and relevant logs. A successful database update alone does not prove the application itself is healthy.

If the error persists, preserve the query output and backup file details, collect the relevant QRadar logs, and open or continue an IBM Support case. Avoid repeating status changes without confirming the remaining blocker.

8. IBM references

• IBM Support — Installation or removal blocked by another preview/install/uninstall task
• IBM Support — Troubleshooting QRadar apps in ERROR state or missing from the UI
• IBM Support — Managing QRadar app operations with the API or qappmanager

This article summarizes the documented status-table recovery for a specific Extension Management error. Direct database edits should be performed only after a successful backup, confirmation of stale records, and approval under your organization's change process.