...
...
...
...
...
...
...
...
Highlights of the week 2nd Aug`22 from Pruthvi:
- As part of MOCN-GW design:
- Added design for handling failure scenarios for S1 setup, Initial attach, Idle mode and Reset procedures
- Modified handling of S1 setup procedure between MOCN-GW and MME. Updated the design to use preconfigured enb-id(per MME) at MOCN-GW instead of same Id for all MMEs
- Working on the design of HO scenarios
- IPv6 data test cases in PR https://github.com/magma/magma/pull/12646 are not working on master code. IPv6 data TC works if iperf is run between dev vm and trf vm on eth3 interface address prior to running the s1ap ipv6 test. The static ipv6 addresses configured on eth3 interfaces of dev and trf server vms become reachable when iperf is run between the 2 vms. Due to this ipv6 data test works if executed after running iperf. Trying to analyze why eth3 interface ipv6 addresses are not reachable if iperf is not run.
- Reviewed PRs: https://github.com/magma/magma/pull/13318, https://github.com/magma/magma/pull/13332
Highlights of the week 1st Aug`22 from Rashmi:
- Incorporated review comments on PR, https://github.com/magma/magma/pull/13335
- Locally brought up the Orc8r based subscriber DB. Issue was reported that on execution of basic attach detach test case from s1ap tester was resulting into Authentication Failure with emm_cause "sync failure"
But in my setup authentication is successful, but mobilityd is not able allocate UE ip address because subscriber is not configured. Checking the dependency of mobilityd on subscriber for IP allocation - As part of c++ migration, ported all c files to cpp for sgw_s8 module.
Highlights of the week 1st Aug`22 from Ankit Kumar Aman:
- Follow up with the CI Issues document https://docs.google.com/document/d/1eGPuYqQBqxn8TBH_pPSVGg77kzuUrKokgfi_CYOgYeE/edit?usp=sharing
- Analyzed for recent CI issues and updated CI issues doc with latest major CI issues
- Monitored CI reports and followed up in slack channel on log artifacts not reported to CI. Debugged and found the issue with the status update for failing executions
- Raised PRhttps://github.com/magma/magma/pull/13423 for enhancing debugging in CI by fetching more logs from vms
- PR reviews and follow-ups: https://github.com/magma/magma/pull/12646
- Meeting and Discussion Involvements: Attended Monday Testing Weekly Meeting, Attended Monday Magma Weekly TSC Meeting and Attended Wednesday 1.8 Release Meeting
...
Highlights of the week 26th July`22 from Pruthvi:
...
- Follow up with the CI Issues document https://docs.google.com/document/d/1eGPuYqQBqxn8TBH_pPSVGg77kzuUrKokgfi_CYOgYeE/edit?usp=sharing
- Debugged on Router Advertisement Issue for IPv6 testcases and OVS api call key error issue. Trying to get more logs for debugging.
- Found Issue with S1APTester that the attach retry was integrity protected and causing the test case failure with assertion. Raised Github Issue https://github.com/magma/S1APTester/issues/85
- Fixed CI issue with attach accept and TAU Accept for all the test cases and updated the PR https://github.com/magma/magma/pull/13139 (Merged)
- Addressed review comments over active PRshttps://github.com/magma/magma/pull/13138,https://github.com/magma/magma/pull/13295 andhttps://github.com/magma/S1APTester/pull/82
- Raised PRhttps://github.com/magma/magma/pull/13323 for reducing the overall sanity execution for failure scenarios
- PR reviews and follow-ups: https://github.com/magma/magma/pull/13060
- Meeting and Discussion Involvements: Attended Wednesday DevOps Meeting and followed up on Release 1.8 meeting notes https://wiki.magmacore.org/x/MwG7
...