-
Bug
-
Resolution: Done
-
Critical
-
None
-
ACM 2.7.Z
-
None
-
False
-
None
-
False
-
-
-
Critical
-
None
Description of problem:
ACM 2.7.14
Submariner 0.14.8
OCP 4.13 and OCP 4.12
Submariner fails to proceed discovery functionality.
The coredns configration has not been configured:
apiVersion: v1 data: Corefile: | .:5353 { bufsize 512 errors log . { class error } health { lameduck 20s } ready kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure fallthrough in-addr.arpa ip6.arpa } prometheus 127.0.0.1:9153 forward . /etc/resolv.conf { policy sequential } cache 900 { denial 9984 30 } reload } hostname.bind:5353 { chaos } kind: ConfigMap metadata: creationTimestamp: "2024-07-23T13:22:06Z" labels: dns.operator.openshift.io/owning-dns: default name: dns-default namespace: openshift-dns ownerReferences: - apiVersion: operator.openshift.io/v1 controller: true kind: DNS name: default uid: 49b9ceb2-fad5-438f-9236-3c9d0529f537 resourceVersion: "8084" uid: 20df23ae-ae3e-4717-92e3-86147940d5db
The "submariner-operator" has the following DNS related error:
2024-07-24T12:45:49.326Z ERR ..oller/controller.go:326 Reconciler error error="error updating Openshift DNS operator: no kind is registered for the type v1.DNS in scheme \"k8s.io/client-go/kubernetes/scheme/register.go:75\"" controller=servicediscovery-controller controllerGroup=submariner.io controllerKind=ServiceDiscovery name=service-discovery namespace=submariner-operator reconcileID=8f3205df-3097-4161-ae33-2df4841f373b serviceDiscovery={"name":"service-discovery","namespace":"submariner-operator"}
- links to
-
RHBA-2024:136935 RHEA: Submariner 0.14.9 - bug fix and enhancement update