• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • rhos-18.0.14 FR 4
    • ovn-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-connectivity-neutron
    • None
    • Approved
    • Critical

      It was catched in uni jobs as described in the linked CIX ticket https://issues.redhat.com/browse/OSPCIX-1089. Also got reproducible even in component job with job tweak(scale out OVN NB/SB DBs from 1 to 3 replicas) https://sf.apps.int.gpc.ocp-hub.prod.psi.redhat.com/zuul/t/components-integration/build/2385c3ee78fb4ca59ee8651c9594c4b0

       
      The behavior is like:- * MinorUpdateOVNControlplane finished(i.e OVN Controllers on OCP workers updated)

      • MinorUpdateOVNDataplane finished(i.e OVN Controllers on EDPM nodes updated)
      • MinorUpdateControlplane stuck(In this stage all the pods are updated except ovn controllers, i.e ovsdbserver NB and SB get's updated too), a few ovn-controller pods are stuck into not ready[1] because of [2]

       
      If we restart/delete these stuck pods, these pods recovers
      Also touching external-ids:ovn-remote (added dummy address) also make it work as get's connected[3]Also have reproducer env if you can check that[1]
       

      [1]

      $ oc get pods -l service=ovn-controller
      NAME READY STATUS RESTARTS AGE
      ovn-controller-7dnl5 0/1 Running 0 105m
      ovn-controller-jdb9x 0/1 Running 0 104m
      ovn-controller-jw226 0/1 Running 0 106m
      
      $ oc describe pod ovn-controller-7dnl5|tail -1
      Warning Unhealthy 13s (x1289 over 101m) kubelet Readiness probe failed: ERROR - ovn-controller connection status is 'not connected', expecting 'connected' status

       
      [2]

      2025-10-27T11:37:08Z|00105|stream_ssl|ERR|ssl:ovsdbserver-sb-2.openstack.svc.cluster.local:6642: connect: Address family not supported by protocol 2025-10-27T11:37:16Z|00106|stream_ssl|ERR|ssl:ovsdbserver-sb-1.openstack.svc.cluster.local:6642: connect: Address family not supported by protocol 2025-10-27T11:37:24Z|00107|stream_ssl|ERR|ssl:ovsdbserver-sb-0.openstack.svc.cluster.local:6642: connect: Address family not supported by protocol

       
      [3]

      2025-10-27T13:33:37Z|02060|stream_ssl|ERR|ssl:ovsdbserver-sb-0.openstack.svc.cluster.local:6642: connect: Address family not supported by protocol 2025-10-27T13:33:45Z|02061|stream_ssl|ERR|ssl:ovsdbserver-sb-2.openstack.svc.cluster.local:6642: connect: Address family not supported by protocol 2025-10-27T13:33:46Z|02062|stream_ssl|ERR|ssl:ovsdbserver-sb-1.openstack.svc.cluster.local:6642: connect: Address family not supported by protocol 2025-10-27T13:33:46Z|02063|reconnect|INFO|ssl:ovsdbserver-sb-1.openstack.svc.cluster.local:6642: connecting...
      2025-10-27T13:33:46Z|02064|reconnect|INFO|ssl:ovsdbserver-sb-1.openstack.svc.cluster.local:6642: connection attempt failed (Address family not supported by protocol) 2025-10-27T13:33:46Z|02065|reconnect|INFO|ssl:ovsdbserver-sb-2.openstack.svc.cluster.local:6643: connecting...
      2025-10-27T13:33:47Z|02066|reconnect|INFO|ssl:ovsdbserver-sb-2.openstack.svc.cluster.local:6643: connection attempt timed out
      2025-10-27T13:33:47Z|02067|reconnect|INFO|ssl:ovsdbserver-sb-0.openstack.svc.cluster.local:6642: connecting...
      2025-10-27T13:33:47Z|02068|reconnect|INFO|ssl:ovsdbserver-sb-0.openstack.svc.cluster.local:6642: connected
       

              ykarel@redhat.com Yatin Karel
              ykarel@redhat.com Yatin Karel
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: