Symptom
The following issue might happen when using the Threat Defense Upgrade wizard (Devices > Upgrade > Threat Defense Upgrade):
- On the 2nd step of the wizard where it says X devices are ready for compatibility and readiness checks, right after performing Run Readiness Check, some devices might disappear from the 2nd step for a short period of time while readiness check is running. The reason is because those devices are incorrectly marked as "missing the upgrade package" and they get moved back to the 1st step of wizard.
The issue could happen in both manual and unattended modes of the upgrade workflow.
In unattended mode there is a chance that unattended mode will fail if all devices of the 2nd step are incorrectly marked as "missing the upgrade package". And in that case, the user may see the following error message in Unattended Mode's View Status modal:
- Cannot start. No devices have the upgrade package.
Conditions
The issue happens when FTD runs into a race condition between Readiness Check and the code that checks device status (whether the device has the upgrade package or not).
There is a small chance for FTD to run into that race condition, especially when FTD is an HA pair or a cluster.
Workaround
For workflow in manual mode, the user will just need to give it some time. Within a couple of minutes after readiness check is completed, the devices should correctly move back to the 2nd step of the wizard.
For workflow in unattended mode, rerunning unattended mode after seeing this failure should resolve the issue, although there is a chance that the user may run into this same issue again.
Further Problem Description
Due to Readiness Check making some temporary changes to upgrade package names, the FTDs (mostly in HA/Cluster, but not limited to that) can report back to the FMC that they do not have the upgrade package while readiness checks are running. This causes the upgrade wizard on FMC to mark the devices as "missing the upgrade package", and move them to the 1st step of the wizard.
This issue can affect upgrade target versions as far back as 7.0.x.
