You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer I would like to have test coverage to insure that no regressions are made around kargs.
So that new feature development can happen with the assurance of CI verifying that no regressions have taken place around the kargs functionality.
This stems from an issue where a user
Installed bootstrap-in-place cluster
Appended kernel arguments (Ip/namespace in this case)
Then found after booting the server was still using a dhcp ip
As a developer I would like to have test coverage to insure that no regressions are made around kargs.
So that new feature development can happen with the assurance of CI verifying that no regressions have taken place around the kargs functionality.
This stems from an issue where a user
Installed bootstrap-in-place cluster
Appended kernel arguments (Ip/namespace in this case)
Then found after booting the server was still using a dhcp ip
This was later fixed by the MR
Lets add some test coverage to insure that the kargs are functioning as expected.
The text was updated successfully, but these errors were encountered: