Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: None
-
Labels:
-
Customer:Ooreedo Tunisia
Description
Dear @Khaled Khalil,
Please assign NEP DEV resource to check why operator is not importing in
NEP under report eNodeB, while it is available in XML.
XML Import: 2025-06-04-11.48.54_Ooredoo_Tunisia (xml attached here)
Platform: Ooredoo Test .102
XML Import Date: 11-06-2025
XML Snippet: attached here.
NEP Snippet: attached here.
And there is no relevant error in an error report related to this.
Thank you
Indrasan
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 1 hour
-
Raised issue to @NEP DE team to check the same.
First it was created with OT-38 which was incorrect so deleted OT-38 and now created under L3 asLS-438.
-
- Time Spent:
- 30 minutes
-
Updated and reverted on mail to NEP DEV team.
-
- Time Spent:
- 3 hours
-
Followed the process to import operator via csv multiple times and troubleshoot & checked the same & taken a teams call with @Mustapha to check & fix the issue. finally issue has been fixed.
-
- Time Spent:
- 1 hour
-
After site id parsing for
OT-45, operator was again disappear, tried to import again manually but it was failed due to operator name was changed in xml, "OoredooTunisia" previous it was "Ooredoo_Tunisia". however it was not fixed and finally we got information from NEP DEV that they are going to clear all data on .102 except catalogue. so will check after this.
-
- Time Spent:
- 1 hour
-
It is again missing in NEP so tried to do the same as last time but it's needed XML import, so will check it later once XML import will done.
