Misunderstanding Audit Status ERROR
Published: September 11, 2024 - 3:59 PM
Hello,
We've been testing WAPT within our company for a while now to see if we can use it to manage our software.
My goal is to enable the deployment of our core software through the tool, so that we can then maintain updates.
I initially spent a good amount of time creating packages to have a package for each application I need to deploy in our private repository. For this part, I deployed the packages using PyScripter Runs.
Now, I've set up a test machine to deploy the various packages I created via the WAPT console, but I'm encountering several problems that I don't understand.
Specifically, if an error occurs during package deployment, it generates warnings and errors ("NEED-UPGRADE", "ERROR"...) in the "Package Status Summary"; The "Status" and "Machine Audit Status" then show an error.
From this point on, there's no way to return to an OK state, despite removing the problematic package from the machine package's dependencies and uninstalling the software in question.
To summarize, the package that generated the error during deployment is no longer listed in the machine package's dependencies or conflicts; there's no trace of the corresponding software on the machine. I've restarted the machine several times and run a package audit and refresh in the WAPT console for this machine, and the machine still shows an error. In the package status summary for this machine, I still see a NEED-UPGRADE and ERROR message for the package in question, even though it no longer exists in my private repository.
We've been testing WAPT within our company for a while now to see if we can use it to manage our software.
My goal is to enable the deployment of our core software through the tool, so that we can then maintain updates.
I initially spent a good amount of time creating packages to have a package for each application I need to deploy in our private repository. For this part, I deployed the packages using PyScripter Runs.
Now, I've set up a test machine to deploy the various packages I created via the WAPT console, but I'm encountering several problems that I don't understand.
Specifically, if an error occurs during package deployment, it generates warnings and errors ("NEED-UPGRADE", "ERROR"...) in the "Package Status Summary"; The "Status" and "Machine Audit Status" then show an error.
From this point on, there's no way to return to an OK state, despite removing the problematic package from the machine package's dependencies and uninstalling the software in question.
To summarize, the package that generated the error during deployment is no longer listed in the machine package's dependencies or conflicts; there's no trace of the corresponding software on the machine. I've restarted the machine several times and run a package audit and refresh in the WAPT console for this machine, and the machine still shows an error. In the package status summary for this machine, I still see a NEED-UPGRADE and ERROR message for the package in question, even though it no longer exists in my private repository.

