Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Customer:Airtel India
Description
the route report count is not correct ,Ran source site showing as routed in RB and not showing in route report under custom reports. L
sample Site ID from DL prod 51908_DL
Please check the logic and data source used for route report .
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours
-
NEP_AIRTEL - Build 3.7.71.534 - Successful has been deployed on all test server .
-
- Time Spent:
- 3 hours
-
NEP_AIRTEL - Build 3.7.71.534 - Successful has been applied on all prod servers .
-
- Time Spent:
- 2 hours
-
NEP_AIRTEL - Build 3.7.71.534 - Successful has been applied on AP and DL prod.
-
- Time Spent:
- 1 hour
-
i have shared RB logs for delay import status in AP circle .
-
- Time Spent:
- 1 hour
-
i have shared DL circle logs to telco team .
-
- Time Spent:
- 30 minutes
-
Testing- test platform
-
- Time Spent:
- 2 hours
-
applied NEP_AIRTEL - Build 3.7.71.534 - Successful on DL and AP prod .
-
- Time Spent:
- 7 hours, 30 minutes
-
worked on triggering single rb for node debugged the code ..working correctly checked reports visible in reports..requested logs again and checking for any other excepltion found during apply circuit saving of relation not executed due to exception comparing logs and checking code doing the required changes after discussion with bessem releasing build after commit
-
- Time Spent:
- 2 hours
-
NEP_AIRTEL - Build 3.7.71.534 - Successful patch has been deployed on all test servers and DB configured .
-
- Time Spent:
- 1 hour
-
ONE MORE SAMPLE CASE REQUESTED FROM L3 FROM TEST SERVER .. SHARED SAME
-
- Time Spent:
- 1 hour
-
shared AS circle logs for Airtel_Route Report not showing all routed sites_Delhi Circle Prod
-
- Time Spent:
- 7 hours
-
checked the sample and debugged it as thinked relation not existing for sample hence not reflecting checking for validatiy wrt to circuits and ranlogical interface debugging the code and logs found exception during apply circuit routes checking that also..connecting dev to sample as circle ,facing gui problem fixed it triggered single rb for sample case relation build node correctly reflecting in routes report.
-
- Time Spent:
- 7 hours, 30 minutes
-
checked the logs requested ..rerequested rb logs checked it..shared script for checking traffic circuit relation data..low count ..checking the code..asked telco for sample from test..checking trafficcircuit relation with routes report.
-
- Time Spent:
- 1 hour
-
sample cases form test server shared with l3 team
-
- Time Spent:
- 1 hour
-
shared server logs from DL prod to priyasha for Airtel_Route Report not showing all routed sites_Delhi Circle Prod
-
- Time Spent:
- 30 minutes
-
data validation on prod after patch was applied and logs added .
-
- Time Spent:
- 5 hours
-
found traffic relation table with less records shared query checked the code added tracking logs for further test on PROD as issue not reproducable at test dev platform released patch
-
- Time Spent:
- 2 hours
-
Nep Build 3.7.71.522 has been deployed on 177 test and DL DB configured on .177
-
- Time Spent:
- 1 hour
-
Query executed on DL PROD DB — count from circuit service relation table for active version_id is 195.
-
- Time Spent:
- 5 hours
-
query returned records do have data in traffic circuit again checking the tables data and tryng to debug the code..reconnected to DL clone checked reports there routes coming proper checking data related in db for clone
-
- Time Spent:
- 7 hours, 12 minutes
-
checking the local code connecting to DEv to DL clone found circuit traffic table empty checking the code for same also the RB last run is on 26-10-25 checked and iscussed with integration some issue currently with db hence rb not executed also asked if rb deletion related script executed not sure putting a count of circuittraffic query on version basis to integration
-
- Time Spent:
- 1 hour
-
shared DL circle logs with dev team .
-
- Time Spent:
- 1 hour
-
i have shared logs from DL circle with dev team
-
- Time Spent:
- 6 hours, 30 minutes
-
checked the issue on jira..checked the related information on PROD application discussed with bessem checking and debugging code for route report at local