How to Clear Deployment Alerts in FMC v. 6.4.0.7

[MSpalding]

I recently upgraded to version 6.4.0.7 for the FMC, and when I went to deploy the config to my sensors, a few of them came back with timeout errors after about 20 minutes of trying to update.  I redeployed the config to those devices again, and my task list shows that they deployed successfully, but the alerts are still showing in the Deployment menu.  Is there any way to clear these alerts from the deployment menu via the webUI?

[Francesco Molino]

Hi
If they're old alerts they should disappear.
If you go to tasks and click remove completed tasks, it should also help to remove history and so remove the alert.
You also have an alert on your health. If you to health and click on the alert itself, it brings you to another page when you can click the button run all modules to force a recheck.

[Marius Gunnerud]

The failed Deployment should be removed automatically once a successful deployment is completed.  In the Tasks tab you can either remove it by clicking the "Remove all completed tasks" or located the failed task and remove it by clicking the "x" next to the time it took to complete the task.

[MSpalding]

Thanks for the responses.  I appreciate the feedback.

The Tasks list did not show any of the failed attempts, it was only showing the successful ones. However, I cleared out the messages pertaining to the deployments, but that did not clear the failed messages.

The 2 items in the Health tab are not related to the deployment errors, they are associated with another issue I am working on, so there is nothing to clear out there that will resolve this issue.

For context, I had rerun the deployment after the initial failed notices, and in the Tasks tab it showed that the deployments had succeeded.  However, the Deployment tab did not update with those successes.  I checked the Deploy section, and there were no out of date deployments at the time I wrote my original post, so it appeared that everything was up to date.  However, when I checked the Deploy section this morning, the two devices were showing as out of date.  So, I will redeploy the policy again tomorrow and see if that resolves the issue.  I'm not sure what the delay in the Deploy section was due to, but it looks like the alerts are now at least justified.

[Marius Gunnerud]

If you are still seeing a failed deployment after your next attempt tomorrow, click on "Show History" under the Deployments tab, select the most recent deployment and then click on the View Transcript button (it shows as a down arrow).  You should be able to see where the fail is happening in there.

If that shows all successes through the deployment, but the Deployment tab shows failed, I would suggest opening a TAC case to drill down into the issue.