Description of problem: in an IPv6 single-stack cluster, CNV can be deployed and used to spin up virtual machines successfully, but the consoles are not available Version-Release number of selected component (if applicable): OCP 4.4 How reproducible: Any OCP 4.4, single-stack IPv6 deployment will have this issue, consoles are not working when pods have IPv6 Steps to Reproduce: 1. deploy an OpenShift with IPv6 clusterNetwork 2. install CNV 3. spin up a VM and try to access the console through the openshift web UI Actual results: both types of console are unavailable Expected results: a graphical or serial console should be displayed Additional info:
Does it work with console on the cmd line? e.g. "virtctl vnc <vm name>"
Hi Tomas, no it does not work with virtctl.. I even tried to connect to the VNC port itself but while I'm used to VNC listening on port 59xx in this case it's using some kind of VNC socket.. anyway, no console whatsoever.. it took me a while to even confirm that a VM was running but I managed to ssh in there.. so VM 100% OK, no console serial or otherwise, from GUI or CLI
ok, thank you! So moving to virt for further investigation.
CNV 2.3 is not supported on IPv6 clusters. This bug should be closed. Support for IPv6 is planned to be introduced in CNV 2.4 (OCP 4.5).
As IPv6 support is feature we intend to implement, but have not yet, it makes sense to treat this as an RFE. Closing this issue as further progress will be tracked in Jira. Please re-open this BZ if you feel this action is in error.