Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-17964

hypershift ovn-k control-plane vs worker config missmatch

    XMLWordPrintable

Details

    • Critical
    • No
    • Approved
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      Hypershift kubevirt provider hosted cluster cannot start up after activating ovn-k interconnect at hosted cluster.
      
      The issue is that ovn-k configurations missmatch:
      
      The cluster manager config in the hosted cluster namespace:
      
        ovnkube.conf: |-
          [default]
          mtu="8801"
          cluster-subnets="10.132.0.0/14/23"
          encap-port="9880"
          enable-lflow-cache=true
          lflow-cache-limit-kb=1048576
      
          [kubernetes]
          service-cidrs="172.31.0.0/16"
          ovn-config-namespace="openshift-ovn-kubernetes"
          cacert="/hosted-ca/ca.crt"
          apiserver="https://kube-apiserver:6443"
          host-network-namespace="openshift-host-network"
          platform-type="KubeVirt"
          dns-service-namespace="openshift-dns"
          dns-service-name="dns-default"
      
          [ovnkubernetesfeature]
          enable-egress-ip=true
          enable-egress-firewall=true
          enable-egress-qos=true
          enable-egress-service=true
          egressip-node-healthcheck-port=9107
      
          [gateway]
          mode=shared
          nodeport=true
          v4-join-subnet="100.65.0.0/16"
      
          [masterha]
          election-lease-duration=137
          election-renew-deadline=107
          election-retry-period=26
      
      The controller config in the hosted cluster
        ovnkube.conf: |-
          [default]
          mtu="8801"
          cluster-subnets="10.132.0.0/14/23"
          encap-port="9880"
          enable-lflow-cache=true
          lflow-cache-limit-kb=1048576
          enable-udp-aggregation=true
      
          [kubernetes]
          service-cidrs="172.31.0.0/16"
          ovn-config-namespace="openshift-ovn-kubernetes"
          apiserver="https://a392ee248c42a4ffca67f2909823466e-18e866c0f5fb5880.elb.us-west-2.amazonaws.com:6443"
          host-network-namespace="openshift-host-network"
          platform-type="KubeVirt"
          healthz-bind-address="0.0.0.0:10256"
          dns-service-namespace="openshift-dns"
          dns-service-name="dns-default"
      
          [ovnkubernetesfeature]
          enable-egress-ip=true
          enable-egress-firewall=true
          enable-egress-qos=true
          enable-egress-service=true
          egressip-node-healthcheck-port=9107
          enable-multi-network=true
      
          [gateway]
          mode=shared
          nodeport=true
      
          [masterha]
          election-lease-duration=137
          election-renew-deadline=107
          election-retry-period=26

      Version-Release number of selected component (if applicable):

      4.14

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy latest 4.14 ocp clustrer
      2. Install latest hypershift operator
      3. Deploy hosted cluster with latest 4.14 ocp release image
      

      Actual results:

      Hosted cluster get stuck at 
      
      network                                    4.14.0-0.ci-2023-08-20-221659   True        True          False      3h53m   DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready...

      Expected results:

      All the hosted clusters operators should be ok

      Additional info:

       

      Attachments

        Activity

          People

            ellorent Felix Enrique Llorente Pastora
            ellorent Felix Enrique Llorente Pastora
            Jean Chen Jean Chen
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: