|Summary:||SNO with static IPv6 address becomes unreachable when upgrading from 4.9 to 4.10|
|Product:||OpenShift Container Platform||Reporter:||Marius Cornea <mcornea>|
|Component:||assisted-installer||Assignee:||Mat Kowalski <mko>|
|assisted-installer sub component:||assisted-service||QA Contact:||Yuri Obshansky <yobshans>|
|Status:||CLOSED CURRENTRELEASE||Docs Contact:|
|Priority:||unspecified||CC:||achernet, agurenko, aos-bugs, bjacot, mko, nshidlin, yshnaidm|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2022-04-14 20:52:45 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||2030289, 2049034|
Description Marius Cornea 2022-01-18 13:15:35 UTC
+++ This bug was initially created as a clone of Bug #2030289 +++ Description of problem: SNO with static IPv6 address becomes unreachable when upgrading from 4.9.15 to 4.10.0-fc.1. The issue seems to be caused by the same root cause as in BZ#2030289 which shows during intial deployment, specifically the nmconnection file exists in /etc/NetworkManager/system-connections but not under /etc/NetworkManager/system-connections-merged which is defined in /etc/NetworkManager/conf.d/01-ipv6.conf. How reproducible: 100% Steps to Reproduce: 1. Deploy 4.9 SNO with static IPv6 address 2. Upgrade SNO to 4.10: oc adm upgrade --allow-explicit-upgrade --to-image=registry.kni-qe-0.lab.eng.rdu2.redhat.com:5000/openshift-release-dev/ocp-release:4.10.0-fc.1-x86_64 --force Actual results: Node becomes unreachable over the network; the network interfaces don't have the IP address set. Expected results: Node connectivity and configuration is not affected by the upgrade process.
Comment 4 nshidlin 2022-01-27 14:31:36 UTC
Successfully upgraded ipv6 SNO cluster with static IP from 4.9.18 to 4.10.0-0.nightly-2022-01-26-234447. The node remains reachable on IP configured at installation.
Comment 6 Luke Meyer 2022-04-14 20:52:45 UTC
The MCO code change that fixed this bug was shipped with the OCP 4.10 GA release, but the bug itself was not. Closing now as it has been fixed all along.