Add network parameters to Agama installation #22220
Merged
Conversation
This file contains hidden or 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
czerw
approved these changes
Jun 2, 2025
jknphy
approved these changes
Jun 2, 2025
https://jira.suse.com/browse/AGM-147 A new Agama feature make our interfaces in openQA not to get an IP, therefore failing in most cases due to not resolving the network. To be consistent with the previous behavior, we need to add some new parameters in the boot process. Related: - https://trello.com/c/P6oGGmjH/4745-ui-handle-persistent-non-persistent-network-connections - Added NetworkManager config server as mandatory package for SLES and SLES SAP agama-project/agama#2279 - Added inst.copy_network to kernel cmdline and config server no-auto-default agama-project/agama#2291 - https://bugzilla.suse.com/show_bug.cgi?id=1241224
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
A new Agama feature make our interfaces in openQA not to get an IP, therefore failing in most cases due to not resolving the network.
To be consistent with the previous behavior, we need to add some new parameters in the boot process.
Related:
VR: hdd creation: https://openqa.suse.de/tests/17908933
child job: https://openqa.suse.de/tests/17908969