PASW upgrade failure "healthcheck.exe: Access is denied"
Article ID: 298008
Updated On:
Products
VMware Tanzu Application Service for VMs
Issue/Introduction
When upgrading PASW tile, you receive the following error:
Task 6690775 | 21:27:19 | Error: Action Failed get_task: Task 28cdab68-2462-40a6-54a5-bc05262ac9a7 result: Applying: Keeping only needed packages: Uninstalling package bundle: remove /var/vcap/data/packages/healthcheck_windows/6c0340cc8a8fc87b60ed79494380f336495e3fe0\internal\healthcheck.exe: Access is denied
During the upgrade process, Windows Diego Cell enters evacuation mode. If there is not enough resource available on the other Windows Diego Cell to run the app instances, the evacuation step will fail. For more information, refer to the following documentation: You may review the available resources for all Windows Diego Cell by running the command cfdot cell-states | grep windows from diego_brain VM.
Environment
Product Version: 2.7
Resolution
When adding a new Windows Diego Cell instance, BOSH is adding it at the end of the deployment. This means this new Windows Diego Cell won't run any app instance before the end of the deployment.
Follow the procedure below for adding a new Windows Diego Cell:
1. BOSH ignores all of the current Windows Diego Cells. BOSH won’t try to evacuate the app instances during the next Apply Changes:
2. Increase the Windows Diego Cell instance under resource tab in the PASW tile, then Apply Changes.
BOSH won't update the current Windows Diego Cell and will create the new Windows Diego Cell.
3. BOSH unignore all of the Windows Diego Cells ignored step 1:
4. Apply Changes - Now BOSH will be able to evacuate the app instance to the new Windows Diego Cell created in step 2 and perform the upgrade.
To prevent this issue in the future, we recommend monitoring the Key Capacity Scaling Indicator. For more information, refer to the following documentation:
Follow the procedure below for adding a new Windows Diego Cell:
1. BOSH ignores all of the current Windows Diego Cells. BOSH won’t try to evacuate the app instances during the next Apply Changes:
bosh -d <pas-windows-deployment> ignore windows_diego_cell/<ID>
2. Increase the Windows Diego Cell instance under resource tab in the PASW tile, then Apply Changes.
BOSH won't update the current Windows Diego Cell and will create the new Windows Diego Cell.
3. BOSH unignore all of the Windows Diego Cells ignored step 1:
bosh -d <pas-windows-deployment> unignore windows_diego_cell/<ID>
4. Apply Changes - Now BOSH will be able to evacuate the app instance to the new Windows Diego Cell created in step 2 and perform the upgrade.
To prevent this issue in the future, we recommend monitoring the Key Capacity Scaling Indicator. For more information, refer to the following documentation:
Feedback
Yes
No
Powered by
