Add known issue for #9815, update known issue for #9260

[tserong]

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 enp6s0f0 becomes enp6s0f0np0. 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

[github-actions]

Name	Link
🔨 Latest commit	f352649
😎 Deploy Preview	https://69782e064719a4ee6a13aa79--harvester-preview.netlify.app

[jillian-maroket]

Review done

[tserong]

Somehow the shell commands vanished when I applied the code review suggestions :-/ Anyway, I've hopefully fixed that properly now and sync'd the versioned docs.

[tserong]

Should I also add a note about the interface name change when upgrading to v1.7.0 in the "important" box up the top of the page, which already mentions the DHCP issue?

[jillian-maroket]

Somehow the shell commands vanished when I applied the code review suggestions :-/ Anyway, I've hopefully fixed that properly now and sync'd the versioned docs.

I checked the preview. The shell commands were rendered fine IMO.

Should I also add a note about the interface name change when upgrading to v1.7.0 in the "important" box up the top of the page, which already mentions the DHCP issue?

You can. Something like this?

Additionally, [persistent names of certain Intel network interfaces may change](#3-persistent-names-of-certain-network-interfaces-may-change-during-upgrade) during upgrades. This breaks connectivity on the host and requires manual remediation steps.

I did away with the "For details" part because the text is redundant.

[tserong]

Thanks @jillian-maroket, done.

[jillian-maroket]

Thanks!