Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-3487

[release-4.11]: CNO in HyperShift management cluster is reconciling ovn-kubemaster in Hosted Control Plane namespace.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • None
    • OVN Kubernetes
    • False
    • None
    • False
    • Hide
      • Install hypershift running on a cluster using OVNKubernetes as its SDN.
      • Create a HostedCluster on that management cluster.
      • Observe the logs of the CNO of the management cluster.
      Show
      Install hypershift running on a cluster using OVNKubernetes as its SDN. Create a HostedCluster on that management cluster. Observe the logs of the CNO of the management cluster.
    • ---
    • 0
    • 0

      In a HyperShift management cluster, the cluster's CNO should only manage the networking components that belong to the management cluster. CNO's running as pods in hosted control plane namespaces own the management of the networking components for their respective hosted clusters.

      Based on the logs of the CNO of a management cluster, it seems that the operator is incorrectly attempting to reconcile the ovnkube-master deployment inside a hosted cluster control plane namespace:

      network-operator-c65867784-s6ph9 network-operator I0828 14:30:50.541952 1 pod_watcher.go:124] Operand /, Kind= ocm-jdzon-1u9o7iloec6vgbieph3jsrh77hmc41ns-jdzon-1/ovnkube-master updated, re-generating status

            pdiak@redhat.com Patryk Diak
            cewong@redhat.com Cesar Wong
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: