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
|
Links Hierarchy |
 Documentation
|
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
10d 6h | 1 | Mustapha Al-Hage | 23/Jun/25 11:40 AM | |||||
|
4s | 1 | Mustapha Al-Hage | 23/Jun/25 11:40 AM | |||||
|
33s | 1 | Mustapha Al-Hage | 23/Jun/25 11:41 AM | |||||
|
1h 4m | 1 | Khaled Khalil | 23/Jun/25 12:45 PM | |||||
|
1d 19h 32m | 1 | Indrasan Yadav | 25/Jun/25 8:17 AM | |||||
|
16s | 1 | Indrasan Yadav | 25/Jun/25 8:18 AM |
| Time Spent | 5 hours, 30 minutes [ 19800 ] | 6 hours, 30 minutes [ 23400 ] |
| Worklog Id | 280177 [ 280177 ] |
-
- 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.
| Time Spent | 4 hours, 30 minutes [ 16200 ] | 5 hours, 30 minutes [ 19800 ] |
| Worklog Id | 271210 [ 271210 ] |
-
- 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, 30 minutes [ 5400 ] | 4 hours, 30 minutes [ 16200 ] |
| Worklog Id | 270301 [ 270301 ] |
| Attachment | Snippet-4.png [ 111901 ] | |
| Attachment | Snippet-3.png [ 111902 ] | |
| Attachment | Snippet-2.png [ 111903 ] | |
| Attachment | Snippet-1.png [ 111904 ] |
| Status | QA In Progress [ 10015 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
| Status | Ready for QA [ 10023 ] | QA In Progress [ 10015 ] |
-
- 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.
| Status | To Be Released [ 10400 ] | Ready for QA [ 10023 ] |
| Assignee | Mustapha Al-Hage [ malhage ] | Indrasan Yadav [ iyadav ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
Dear @Indrasan Yadav,
The operator is not appearing in the NEP under the eNodeB report because the operator must be imported before importing the XML file.
- Import Operator using a CSV file:
- Import the XML file
Regards,
Mustapha
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Assignee | Khaled Khalil [ kkhalil ] | Mustapha Al-Hage [ malhage ] |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
| Time Spent | 1 hour [ 3600 ] | 1 hour, 30 minutes [ 5400 ] |
| Worklog Id | 269612 [ 269612 ] |
| Worklog Id | 269608 [ 269608 ] |
| Baseline Start | 2025-06-20 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2025-06-20 24:00 (set baseline based of initial work logging) |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour [ 3600 ] | |
| Worklog Id | 269608 [ 269608 ] |
| Attachment | server.log.2025-06-11 [ 111110 ] |
| Attachment | XML Snippet.png [ 111101 ] | |
| Attachment | eNodeB Report NEP Snippet.png [ 111102 ] | |
| Attachment | eNodeB CSV Snippet.png [ 111103 ] |
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2025-06-20 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2025-06-20 24:00 (milestone: set planned end date to due date) |
-
- Time Spent:
- 30 minutes
-
Updated and reverted on mail to NEP DEV team.
-
- 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.
Dear @Mustapha Al-Hage,
As discussed during our Teams call, I attempted to import operator details via CSV multiple times using the input data where the color was set to yellow. However, an error message appeared indicating that the same color already exists. I demonstrated this issue to you during the call.
Subsequently, I changed the color to blue and orange, but the same error persisted. I then left the color field blank, but another error was shown stating that the color cannot be blank.
Finally, I used the value “0_102_255”, which you shared as a reference from OmanTel. This time, the import was successful. I then imported the corresponding XML, and the data is now correctly appearing under the “eNodeB” report.
Conclusion:
The issue has been resolved successfully.
Thank you
Indrasan