Multiple OptiX OSN 1800V are upgraded to R21C10SPC300+SPH315 with patches.
The SPH315 patch is selected for the upgrade project. However, after the upgrade, some devices are actually installed with the SPH311 patch and others are installed with the SPH315 patch.

Handling Process
1. The project information shows that the patch version is SPH315, which is normal.

2. After the upgrade is complete, the patch version is SPH311.

3. Run the patchpkg-get-pkginfo:all command to check whether the version is SPH311.

4. Review the upgrade process again.
a. Create an upgrade project. Initially, select V100R0021C10SPC300+SPH311 as the target version.
b. Create an upgrade task and select the NEs to be upgraded.
c. Upload the SPH315 patch to NCE.
d. Modify the software information of the upgrade project and perform the upgrade.

Compared with the NEs with the SPH315 and SPH311 patches after the upgrade, the differences are as follows:
a. For NEs with the SPH315 patch after the upgrade, the upgrade task is created only after the upgrade software is modified.
b. For NEs with the SPH311 patch installed after the upgrade, the upgrade task is created before the step of modifying the upgrade software.

Confirmed:
The modified upgrade items take effect only for the NEs in the subsequent upgrade tasks, and it does not take effect for the NEs in the created upgrade project.

Root cause
The upgrade task is not re-created after the software version information of the upgrade project is modified.

Solution
After modifying the software version information of an upgrade project, we must create a new upgrade task again. Otherwise, the system still uses the old software version information for upgrades.