-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17
-
None
-
False
-
-
kubevirt, Don't break on hostname NodePort.Address
-
Bug Fix
-
In Progress
Description of problem:
When creating a kubevirt hosted cluster with the following apiserver publishing configuration - service: APIServer servicePublishingStrategy: type: NodePort nodePort: address: my.hostna.me port: 305030 Shows following error: "failed to reconcile virt launcher policy: could not determine if amy.hostna.me is an IPv4 or IPv6 address" And network policies and not propertly deployed at the virtual machine namespaces.
Version-Release number of selected component (if applicable):
4.17
How reproducible:
Always
Steps to Reproduce:
1.Create a kubevirt hosted cluster with apiserver nodeport publish with a hostname 2. Wait for hosted cluster creation.
Actual results:
Following error pops up and network policies are not created "failed to reconcile virt launcher policy: could not determine if amy.hostna.me is an IPv4 or IPv6 address"
Expected results:
No error pops ups and network policies are created.
Additional info:
This is where the error get originated -> https://github.com/openshift/hypershift/blob/ef8596d4d69a53eb60838ae45ffce2bca0bfa3b2/hypershift-operator/controllers/hostedcluster/network_policies.go#L644 That error should prevent network policies creation.
- clones
-
OCPBUGS-46660 [4.16] kubevirt hosted cluster with apiserver noderport using hostname ends without network policies
- New
- depends on
-
OCPBUGS-46660 [4.16] kubevirt hosted cluster with apiserver noderport using hostname ends without network policies
- New