Add known issue for #9815, update known issue for #9260 #962
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
Related-to: harvester/harvester#9815 Related-to: harvester/harvester#9802 Related-to: harvester/harvester#9260 Signed-off-by: Tim Serong <tserong@suse.com>
github-actions
bot
requested review from
akashraj4261,
dariavladykina and
jillian-maroket
|
This was referenced Jan 23, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
It's possible for updated NIC drivers to result in persistent network interface names changing after upgrade to Harvester v1.7.x, e.g. to add port numbers, so
enp6s0f0becomesenp6s0f0np0. This in turn breaks network configuration which is of course based on the original (pre-upgrade) interface names.Solution:
Document the workaround for upgrades from v1.6.x to v1.7.0. Mention that the workaround is applied automatically when upgrading from v1.6.x to v1.7.1.
Bonus: mention that the workaround for another known v1.7.x upgrade issue is also automatically applied when upgrading to v1.7.1.
Related Issue(s):
harvester/harvester#9815
harvester/harvester#9802
harvester/harvester#9260
Test plan:
N/A
Additional documentation or context