Details
-
Type:
Bug
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain KSA 3.X
Description
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
++looping @Indrasan Yadav
Regards,
Khaled Khalil
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please delete it from your system and notify the sender immediately. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
________________________________________
From: build server <build-server@mobinets.com>
Sent: Monday, March 17, 2025 4:07 AM
To: Sandya.Sharma@mobinets.com <Sandya.Sharma@mobinets.com>; Hassan Abdine <hassan.abdine@nuiva.com>; Sandya Sharma <sandya.sharma@nuiva.com>; Integration India <Integration-India@mobinets.com>; L2_Team_Leb <L2_Team_Leb@mobinets.com>; support <support@mobinets.com>; Khaled Khalil <khaled.khalil@nuiva.com>
Subject: NEP_ZAIN_KSA_AI - Build 3.7.2.20 - Successful
Build SUCCESS
Project: NEP_ZAIN_KSA_AI
Release Version: 3.7.2.20
Build URL: http://ciserver.mobinets.local:8080/job/NEP_ZAIN_KSA_AI/25/
Date of build: Mon, 17 Mar 2025 10:06:02 +0200
Build duration: 1 min 32 sec
Changes
• 17 March 2025 09:01 AM Commit 133489 by Sandya Sharma: (fix issue for dummy value in board type)
• 17 March 2025 08:49 AM Commit 133488 by CI Server: (prior to build 3.7.2.20)
• 13 March 2025 04:50 PM Commit 133441 by CI Server: (prior to build 3.7.2.19)
Dear @ABHINAV PARASHAR,
Could you please deploy the mentioned patch on production & after deploying this patch please generate full XML & share with csv.
Thank you
Indrasan
Dear Indrasan,
Full XML generated on ZainKSA prod server after deploy latest AI patch.
NETWORKS TRANSFORMED
Abhinav Parashar| Sr. System Engineer
Mob: +91 9897473040
1102-1103, Tower C, Unitech Cyber Park, Gurgaon
abhinav.parashar@mobinets.com | www.mobinets.com
Now, I checked in latest XML which is available on production server and there is no any blank data is parsing in column "name" under "npsnodeb".
So, as per XML level it has been fixed once import will done on production need to validate the same. (As currently XML import is not happening on production due to some testing ongoing there)
After confirmation with @Bassem/@Ahad manually full XML import was done on production.
Then checked and found that now issue has been fix for Nokia NodeB(405) which has been now imported in NEP.
Dear @Bassem Sabbagh,
I have noticed that the Site ID is not parsing for NodeB (Nokia) in the XML, and the same issue is also present in NEP. It seems that the node name is not parsing, which is why it is not appearing, as it depends on the node name.
As I recall, I had shared a static sheet titled “RAN_Node Name_Matching” with #Juned to assist in parsing the node name for NodeB (Nokia).
@Sandya Sharma, could you please check and confirm whether the required static sheet (“RAN_Node Name_Matching”) is available in production before XML generation?
Thank you,
Indrasan