Autoyast based installation does not seem to respect defined udev rules. #1061
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Udev rules are not refreshed after writting
The InterfacesWriter did not refreshed the written udev rules in case of an autoinstallation as we can see here:
https://github.com/yast/yast-network/pull/1059/files#diff-48ec4731f89821c19dc203da64dc00a5L108
In case of the second stage, or, the first stage with the imported network configuration written before the proposal, then, a rename of the interfaces is needed. Thus, we should distinguish between being at the end of the installation (already chrooted) or not.
Solution
The problem with udev rules handling during installation was already fixed in #1059, as well as other issues. Thus, I have backported some of the commits, at least the relevants to SP2, and adapted the code where it was needed. We have to take into account that in SP3, the idea is to write the network configuration during the first stage by default.
Tests