During cluster upgrade from an old OpenSAF version which have not included the fix #2006 to one that have the fix in, if there is an code fault related to inconsistent in additionalText
and lengthAdditionalText
in NTF application, could lead to upgadate failed.
This ticket intends to add an workwround in NTFs, secretly adjust lengthAdditionalText
to correct one if NTFs find the mismatch, before NTFs sends write request to LOGsv. Doing this action to avoid NTFs crashed due to getting SA_AIS_ERR_INVALID_PARAM returned by LOGsv.
changeset: 8582:8bf021b169f3
tag: tip
parent: 8579:a39b16c96516
user: Canh Van Truong canh.v.truong@dektech.com.au
date: Sat Feb 11 03:51:36 2017 +0700
summary: ntf: workaround to fix failed upgrade [#2300]
changeset: 8581:e0b4efdf79af
branch: opensaf-5.1.x
parent: 8575:1473bf4b1214
user: Canh Van Truong canh.v.truong@dektech.com.au
date: Sat Feb 11 04:27:42 2017 +0700
summary: ntf: workaround to fix failed upgrade [#2300]
changeset: 8580:66ec2284f5d4
branch: opensaf-5.0.x
parent: 8574:8840a5cd12b8
user: Canh Van Truong canh.v.truong@dektech.com.au
date: Sat Feb 11 04:46:32 2017 +0700
summary: ntf: workaround to fix failed upgrade [#2300]
Related
Tickets:
#2300