-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
ACM 2.8.Z
-
None
-
Submariner Sprint 2024-25
-
None
Description of problem:
ACM 2.8.7
Submariner 0.15.4
OCP 4.13 and OCP 4.12
Submariner fails to proceed discovery functionality.
The coredns configuration 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-22T10:57:08Z" 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: 8126f6fa-27d7-4819-9709-7f3f729696e7 resourceVersion: "9448" uid: fcc6e3ec-beac-4c3a-bc2a-694735db9dfb
The "submariner-operator" has the following DNS related error:
2024-07-22T12:40:53.444Z ERR ..oller/controller.go:329 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:79\"" ServiceDiscovery={"name":"service-discovery","namespace":"submariner-operator"} controller=servicediscovery-controller controllerGroup=submariner.io controllerKind=ServiceDiscovery name=service-discovery namespace=submariner-operator reconcileID=bca72137-8c2c-426c-b0f6-b8028d30e0c3
- links to
-
RHEA-2024:136707 RHEA: Submariner 0.15.5 - bug fix and enhancement update