Skip to content
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

[12.0 stable] Wait for wwan to apply latest config before testing connectivity #4059

Merged
merged 1 commit into from
Jul 7, 2024

Conversation

milan-zededa
Copy link
Contributor

When cellular network config changes, it may take few seconds for the wwan microservice and the modem to apply the new config. NIM microservice should wait for the wwan config to be fully applied when cellular connectivity is used for management and ethernet is not available. Otherwise, it may determine the connectivity as not working and failover to the previous config too fast, not giving the modem the chance to connect with the latest config.

Also fixed in this commit is the Equal() method for CellularAccessPoint. It used to compare also timestamp inside ErrorAndTime which may change even if there is no actual config change. As a result, wwan microservice would trigger re-connection even when there was no config change to apply. This fix is in pillar and will be propagated into wwan/mmagent in the next commit (with "go get") once this one is merged.

(cherry picked from commit f208c67)

When cellular network config changes, it may take few seconds for the
wwan microservice and the modem to apply the new config.
NIM microservice should wait for the wwan config to be fully applied
when cellular connectivity is used for management and ethernet is not
available. Otherwise, it may determine the connectivity as not working
and failover to the previous config too fast, not giving the modem the
chance to connect with the latest config.

Also fixed in this commit is the Equal() method for CellularAccessPoint.
It used to compare also timestamp inside ErrorAndTime which may change
even if there is no actual config change. As a result, wwan microservice
would trigger re-connection even when there was no config change to
apply. This fix is in pillar and will be propagated into wwan/mmagent
in the next commit (with "go get") once this one is merged.

Signed-off-by: Milan Lenco <milan@zededa.com>
(cherry picked from commit f208c67)
@milan-zededa milan-zededa merged commit e6f9597 into lf-edge:12.0-stable Jul 7, 2024
21 of 31 checks passed
@jsfakian jsfakian added the stable Should be backported to stable release(s) label Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stable Should be backported to stable release(s)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants