Bulk Update does not report all jobs at Sucessful

Symptoms

When triggering a bulk update campaign, or after a Comet-Hosted upgrade, while the update installs correctly, the job gets stuck in a running state. 

Cause

Device will update successfully, but the job gets stuck in a running state. The update job does not send a "completed" signal to the management console.

This is a Comet Backup bug with ID COMET-60096.

Resolution

Comet version 26.7.1 Janus contains the fix for this logging bug. The issue happens before the fix is installed, so it happens one last time.

Lingering "running" update jobs can be force cancelled from the management console.

  1. Open job logs.
  2. Search for running update jobs.
     

     
  3. Select all jobs.
  4. From "bulk actions", choose "Cancel (force)".
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.