Rollback Script from R46 to R45 Stopped after Network Conversion and did not Display the Expected “Upgrade action completed successfully” Message

Asset ID:	1-71-2149062.1
Update Date:	2016-06-15
Keywords:

Solution Type Technical Instruction Sure

Solution 2149062.1 : Rollback Script from R46 to R45 Stopped after Network Conversion and did not Display the Expected “Upgrade action completed successfully” Message

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 45.0 and later
Information in this document applies to any platform.

Goal

The Rollback script got hung at some point and did not display the expected “Upgrade action completed successfully” message, even though all cards had been converted and were running the correct GPL.
For which reason ?

Solution

- This is a known bug : BUG 19109184 - [233525] Upgrade stuck in Upg Phase 2.
Fix is available in R45.0.1-64.70.33 and later.

- This bug is about a conflict of process between the STP conversion and the measurements.

- In reality the conversion of all cards did happen. Running one more time the “upgrade” command led the Eagle to display the 3 expected completion messages :

> ACT-UPGRADE:ACTION=CONVERTSTP:SRC=FIXED:THRES=75

eagle 16-05-19 14:13:40 MST EAGLE5 45.0.0-64.70.31 Upg Phase 3
ACT-UPGRADE: Network conversion complete
;
eagle 16-05-19 14:13:40 MST EAGLE5 45.0.0-64.70.31 Upg Phase 3
ACT-UPGRADE: Network upgrade complete
;
eagle 16-05-19 14:13:40 MST EAGLE5 45.0.0-64.70.31 Upg Phase 3
Command Complete : Upgrade action completed successfully

Reseating the active MASP allowed the exit of the Phase 3 display and returned to the normal release display :

> login:uid=eagle

eagle 16-05-19 14:23:36 MST EAGLE5 45.0.0-64.70.31
login:uid=eagle
Command entered at terminal #3.

- Now regarding the fact that this rollback failure is blocking the upgrade, it should not because :

The problem was observed only during rollback to 45.0.0.
There is a workaround available which allows to complete rollback without any other issue.
This problem was observed only during the network conversion part of rollback to 45.0.0-64.70.31, that means the OAM was running R45.0.0-64.70.31 software during the time of the issue.
The problem is during the rollback while the system is running source release. You cannot get the fix without performing an upgrade in any case

References

<BUG:22137660> - UPG_MGR.C, DBCD_UTL.C, AND SCM_HWVF.C TROUBLE GENERATED DURING UPGRADE.
<BUG:19109184> - [233525]UPGRADE STRUCK IN UPG PHASE 2

Attachments

This solution has no attachment