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

Make sure NetworkManager is running #1

Open
todoleza opened this issue Mar 31, 2021 · 0 comments
Open

Make sure NetworkManager is running #1

todoleza opened this issue Mar 31, 2021 · 0 comments
Assignees

Comments

@todoleza
Copy link
Collaborator

Currently the code ignores NetworkManager state completely. This is not expected default environment and should be asserted and fixed before finishing fwdSetup.
Possible solutions:

  1. only log beakerlib warning
  2. fail in setup if NM is not running -> cause test overall Warn state
  3. any of the above and start NM prior finishing fwdSetup

After considering the above, it'd be best to assert that NetworkManager is running in setup phase and if not, start it and keep it running after fwdCleanup as well. This should be possible to tune via environment variables that would allow to:

  • ignore NM state altogether (only report to log)
  • actively disable NM (and restore to previous state if above variable was set as well)
@todoleza todoleza self-assigned this Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant