[ZKU-232] Need To Implement Rule For Duplicate Node With Different Model_Huawei Created: 02/Jan/25 Updated: 10/Jan/25 Due: 06/Jan/25 |
|
| Status: | Done |
| Project: | Zain KSA upgradation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | Indrasan Yadav | Assignee: | Indrasan Yadav |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | AI_All_incidents, ZAINKSAAUDIT, ZAINKSAUAT | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day, 7 hours | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
Need To Implement Rule For Duplicate Node With Different Model_Huawei __ ZKU-232 __.msg
|
||||||||
| Issue Links: |
|
||||||||
| Customer: |
Zain KSA 3.X
|
||||||||
| Planned Start: | |||||||||
| Planned End: | |||||||||
| Actual Start: | |||||||||
| Date of Baselining: | |||||||||
| Description |
|
Dear @Bassem Sabbagh, As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below: Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference). Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900". Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900". Best regards, |
| Comments |
| Comment by Bassem Sabbagh [ 02/Jan/25 ] |
|
Assigned to Sandhya to define the WL |
| Comment by Sandya Sharma [ 08/Jan/25 ] |
|
WL is one day. |
| Comment by Bassem Sabbagh [ 08/Jan/25 ] |
|
to be started and delivered by 9-1 |
| Comment by Indrasan Yadav [ 10/Jan/25 ] |
|
Dear @Sandya, please commit the code for same as now issue has been fixed in shared XML (2025-01-09-05.30.41_ZainKsa) |
| Comment by Sandya Sharma [ 10/Jan/25 ] |
|
commit done. |
| Comment by Indrasan Yadav [ 10/Jan/25 ] |
|
We are now closing this child JIRA as it pertains to an individual issue. As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA. |