-
Notifications
You must be signed in to change notification settings - Fork 529
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
[vstest]: report error when team kernel module is not available #994
Conversation
make explicit failure if team kernel module is not available on the system Signed-off-by: Guohan Lu <gulv@microsoft.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why explicitly check the 'team' module? what scenario did you encounter that is caused by this issue?
sometimes, the kernel driver package is splitted in base module and extra module packages, and team driver is in the extra package, and extra packet is not automatically installed. then, all lag related vs test will not pass. It is hard to debug that, therefore I am adding explicit check for this requirement. |
this happened on the worker-2, after I manually installed extra kernel module, everything works. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wondering do we want to have a controlled or defined environment setup for the server
yes, we want to have that control, but sometime, the server automatically upgrading their kernel controlled by azure. we need to disable it, but it is a separate issue. |
…c-net#994) make explicit failure if team kernel module is not available on the system Signed-off-by: Guohan Lu <gulv@microsoft.com>
…c-net#994) make explicit failure if team kernel module is not available on the system Signed-off-by: Guohan Lu <gulv@microsoft.com>
Instead of having multiple implementation of preparing a SWI image for secureboot, fast-reboot now reuses boot0. SWI images booting in regular mode will keep using the old behavior.
make explicit failure if team kernel module is not available on the system
Signed-off-by: Guohan Lu gulv@microsoft.com
What I did
Why I did it
How I verified it
Details if related