Bulk deployments stuck in a Processing loop if deleted manually
During a bulk application deployment, if an instance fails to pass the NMaaS readiness check (e.g., due to a misconfiguration of the base app name, or too strict readiness probes), it will remain in a Processing state on the Bulk Deployments page. If the user in the meantime manually goes to the application details and clicks "Undeploy", the application will successfully be undeployed, but the bulk application deployment mechanism will not be made aware of the change, and the status will remain "Processing". Additionally, the NMaaS Platform continues to probe the status of the now non-existent deployment.
2023-08-21 16:07:36,679 [skExecutor-4989] INFO ortal.service.impl.BulkApplicationServiceImpl: 209 - Status update for deployment adf2f614-57bc-44d2-9cfc-849af3f7a080
2023-08-21 16:07:51,691 [skExecutor-5002] INFO ortal.service.impl.BulkApplicationServiceImpl: 209 - Status update for deployment adf2f614-57bc-44d2-9cfc-849af3f7a080
2023-08-21 16:08:06,708 [skExecutor-5009] INFO ortal.service.impl.BulkApplicationServiceImpl: 209 - Status update for deployment adf2f614-57bc-44d2-9cfc-849af3f7a080
2023-08-21 16:08:21,721 [skExecutor-5067] INFO ortal.service.impl.BulkApplicationServiceImpl: 209 - Status update for deployment adf2f614-57bc-44d2-9cfc-849af3f7a080