si-upd-0803 Azure refused the new version for a SecurityInsight job, so the update was rolled back
What it means
The update built the new version, but Azure refused to put it on one or more SecurityInsight jobs. Usually Azure could not reach your container registry at that moment. Every job that had already changed was put back on the version it ran before, so your install keeps working on its current version and no data was lost. The update is tried again.
| Code | si-upd-0803 |
|---|---|
| Who acts | Invardia support |
| Action | Invardia support helps: open a ticket and quote the code, or follow the steps below. |
What to do
- Invardia support: Check the update log: every job reads back its previous image and the installed version did not move. Read the 400's details: a registry network answer (connection refused, i/o timeout) is transient -- start the same update again. An image that does not exist or a registry that refuses the identity is not -- fix that first.
Written by the SecurityInsight team; Invardia publishes it. Quote the code when you contact support@invardia.com. · All SecurityInsight error codes