#2012 clm: inconsistant additionalText and lengthAdditionalText in notification construction

[Vu Minh Nguyen]

According to NTF AIS, additionalText must be consistent with lengthAdditionalText.

In current code, CLM always set an hard-code ADDITION_TEXT_LENGTH to lengthAdditionalText regardless of what additionalText is.

[Mathi Naickan]

changeset: 8043:4a8a00097561
branch: opensaf-4.7.x
parent: 8023:eef3593c3597
user: mathi.naickan@oracle.com
date: Fri Sep 09 18:14:01 2016 +0530
summary: clm: make values of additionalText and lengthAdditionalText the same [#2012]

changeset: 8044:233ed6d2e3c9
branch: opensaf-5.0.x
parent: 8038:bc1bac48177a
user: mathi.naickan@oracle.com
date: Fri Sep 09 18:14:01 2016 +0530
summary: clm: make values of additionalText and lengthAdditionalText the same [#2012]

changeset: 8045:d466bf0ab8d5
branch: opensaf-5.1.x
parent: 8041:5ced31149915
user: mathi.naickan@oracle.com
date: Fri Sep 09 18:14:01 2016 +0530
summary: clm: make values of additionalText and lengthAdditionalText the same [#2012]

changeset: 8046:879868aeeb5d
tag: tip
parent: 8042:48dfff49010e
user: mathi.naickan@oracle.com
date: Fri Sep 09 18:14:01 2016 +0530
summary: clm: make values of additionalText and lengthAdditionalText the same [#2012]

[Mathi Naickan]

Forgot to change the name to Vu. The author of the patch is Vu, sorry about that.

[Vu Minh Nguyen]

Thanks Mathi for pushing.

I detected this issue when implementing the fix for the ticket [#2006].
To reproduce the problem, apply [#2006]'s patch, then start the cluster. We will see the cluster gets failed to start up.