Problem Symptom
When rolling back the system from FusionStorage 8.0.1.SPH302 or SPH303 to 8.0.1.SPH301 or earlier, FSM rollback is suspended or FSM rollback confirmation fails.
Problem Diagnosis
If the FSM rollback is suspended:
1. Log in to the FSM node where the rollback is paused.
2. Run the tailf /var/log/omm/oms/catalina.log command to check whether abnormal records are printed, resulting in repeated Tomcat restart.
If the FSM rollback confirmation fails:
1. Log in to DeviceManage and choose Monitor > Alarms and Events > Events. Check whether there are frequent active/standby switchover events reported.
Causes
In 8.0.1 SPH302 and later versions, the encryption key policy is updated. As a result, the encryption key policy used by 8.0.1.SPH301 and earlier versions is different from that used by 8.0.1 SPH302 and later versions. During the rollback, the rollback adaptation script cannot be modified and the rollback fails.
Solution
Use PuTTY to log in to the active FSM node and switch to user root.
Run the following command on both FSM nodes:
Command 1: sed -i s/ssl.self.cert.passwd=.*/ssl.self.cert.passwd=283A56f7D319FeDEtpf8PZM7LGaX7f8eZyYgWg==/g /opt/omm/oms/workspace/webapps/dsware/WEB-INF/dsware-api.properties
Command 2: sed -i s/ssl.trust.ks.passwd=.*/ssl.trust.ks.passwd=283A56f7D319FeDEtpf8PZM7LGaX7f8eZyYgWg==/g /opt/omm/oms/workspace/webapps/dsware/WEB-INF/dsware-api.properties
Command 3: sed -i s/api.content=.*/api.content=53BE639E41BB8CFDE15B247F5CFE1CC779CE89568F80E4CE9DC42348C887EC6924A7820CE050A5B33FF57B3CB7C588F97F84BF14758F09E971760B016C8B0D58E5544E039CE718A3009AD60220B83A1E/g /opt/omm/oms/workspace/webapps/dsware/WEB-INF/dsware-api.properties
Command 4: sed -i '/^api.key=.*/d' /opt/omm/oms/workspace/webapps/dsware/WEB-INF/manager-ssl.properties
Command 5: sed -i '1i\api.key=TmnK3IOZsqsCge6GuJtCFVTm6xOq3Edr' /opt/omm/oms/workspace/webapps/dsware/WEB-INF/manager-ssl.properties
Wait until the FSM rollback is complete or the rollback confirmation is successful.
