WILL UPDATE THE DETAILS AFTER ANALYSIS

Dear Priyasha,
As discussed earlier regarding the radio bandwidth relationship between role4G and cell, we require some additional information related to this data.
Could you please share the relevant details.
Alternatively, if it’s more convenient, kindly arrange a meeting so we can discuss this further.

Dear Priyasha,
After analyzing this issue, we found that the problem is occurring due to missing data in xml as observed Role4G entries that are not updating have a cell radiobandwidth value of 15 in the XML, which does not correspond to any of the supported bandwidths defined in the XML for parent role4g.
I am attaching a sample case for reference: sranbs: RJ-NLBHL253-1_RJ-NLBHL253-1.

For other sample cases that are updating correctly, the cell bandwidth value is always in correspondence with the supported bandwidths of the 4G node in the XML. To validate this, we manually updated the XML by adding 15 to the supported bandwidths for the 4G node. After making this change, the nodes started updating correctly.
Attaching the screenshots for the same.
Kindly have a look at this and check accordingly.

Sharing one sample HP-NLBDUN01-1 , here we can see that the node bandwidth and radio bandwidth are same still the role 4G node is not getting updated please check this sample specifically , on .37 test HP DB is connected ,..

The shared case issue is different and is caused by old cell bandwidth being checked in the validation while updating...3.7.71.542 is released with changes for bandwidth validation