-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[subscriberdb] Subscribers not showing up after IMSI deconcealing fix (12567) #13036
Comments
On latest master code base, we have added a new subscriber(IMSI001010000000004) through swagger API and it is getting reflected only after 5 minutes in the subscriberdb. Please refer attached log file and snapshots. |
I see the error on my laptop as well and I'm not sure it's caused by the changes from #12567. It seems like it's somewhere in the orc8r, and the PR mostly touched agw code. The orc8r subscriberdb panics because of a nil pointer access in this line:
|
Okay, the nil check is broken there, you have to do the type conversion before the check. Will add a PR to fix that so subscriberdb returns an error instead of panicking.
See #13065. |
Closing the ticket with reference to #13081 |
Your Environment
Describe the Issue
Possibly related commit: #12567
After adding a new subscriber via swagger and running subscriber_cli.py list on the gateway VM returns no subscribers. The debug logs indicate the following error:
ERROR:root:Fetch suci profiles error! [StatusCode.UNKNOWN] handler panic: runtime error: invalid memory address or nil pointer dereference;
To Reproduce
subscriber_cli.py list
sudo journalctl -u magma@subscriberdb
to see the logsExpected behavior
IMSI of the added subscriber shows up.
Screenshots
GET shows that IMSI has been added.
subscriber_cli.py list
does not print any IMSIsError message shows up: fetch suci profiles error!
The text was updated successfully, but these errors were encountered: