PlogServer Upgrade Paused Due to Node Restart During the Upgrade

Problem Symptom

A node is restarted during the PlogServer upgrade and the upgrade is paused. After the node is restarted, retry the PlogServer upgrade. However, the upgrade fails.

Problem Diagnosis

1. Confirm that a node has been restarted during the upgrade.

   

2. Check the /var/log/deploy/clouda/script/action.log log of the failed node. The last component that was being upgraded is PlogServer and the component was invoking the online command.

   

   ../Resource/public_sys-resources/note_en.png?v=20200527

   Atomic tasks during the PlogServer component upgrade:

   offline > stop > upgrade > start > check status > online

3. Run the cd /opt/fusionstorage/repository/deploymanager_pkg/micro/ && ll | grep plogclient command to check the PlogClient version on the failed node.

4. Run the ll command to check the RPM package in repo of the plogclient directory of a later version. The size of the RPM package is 0.

   

Causes

During the upgrade, the node is restarted. As a result, the decompressed PlogClient files are still in the cache and are not written to disks. After the node is restarted, the files are lost. As a result, the PlogServer fails to invoke related PlogClient files during the PlogServer upgrade, and the upgrade is paused.

Solution

1. Log in to the active management node.

2. Go to the /opt/fusionstorage/repository/data/plogclient/ directory, find the plogclient folder of the target version, and go to the folder corresponding to the platform type (aarch64 or x86_64) of the failed node.

3. Copy the .tar package from the preceding folder to the /opt/fusionstorage/repository/deploymanager_pkg/micro/ directory on the failed node.

4. Run the tar command to decompress the copied package on the failed node.

5. Copy the .FusionDeploy_Install_Info.ini file in the plogclient directory of the earlier version in the /opt/fusionstorage/repository/deploymanager_pkg/micro/ directory on the failed node to the preceding decompression directory.

6. Log in to DeviceManager and retry the upgrade.

Check After Recovery

N/A

Suggestion and Summary

N/A

Applicable Versions

OceanStor 100D 8.0.3; OceanStor Pacific series 8.1.0; OceanStor Atlantic series 8.1.0