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

Discovery agent IPv6 api/ingress duplicate address messages in dmesg

    • Quality / Stability / Reliability
    • None
    • None
    • None
    • Low
    • None
    • Unspecified
    • None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None
    • None
    • None
    • None
    • None

      Description of problem:
      On a IPv4 environment, discovery agent

      Version-Release number of selected component (if applicable):
      "release_tag":"v1.0.24.2",
      "versions":{
      "assisted-installer":"registry-proxy.engineering.redhat.com/rh-osbs/openshift4-assisted-installer-rhel8:v1.0.0-81",
      "assisted-installer-controller":"registry-proxy.engineering.redhat.com/rh-osbs/openshift4-assisted-installer-reporter-rhel8:v1.0.0-82",
      "assisted-installer-service":"quay.io/app-sre/assisted-service:7c32a07","discovery-agent":"registry-proxy.engineering.redhat.com/rh-osbs/openshift4-assisted-installer-agent-rhel8:v1.0.0-54"

      How reproducible:

      Steps to Reproduce:
      1. Create a cluster and boot up the nodes
      2. Wait 30-40 minutes without starting the installation
      3. Check the dmesg on the nodes

      Actual results:
      All nodes have messaged related to IPv6 api/ingress duplicate address.
      Same ipv6 address/ mac address is on all the nodes.

      [ 5780.807469] IPv6: api: IPv6 duplicate address fe80::21a:4aff:fe9e:5045 used by 00:1a:4a:9e:50:45 detected!
      [ 6326.810152] IPv6: ingress: IPv6 duplicate address fe80::21a:4aff:fec7:ae99 used by 00:1a:4a:c7:ae:99 detected!

      Expected results:
      no duplicate address messages

      Additional info:
      Attached is the output of ip a and last 10 lines of dmesg from all the nodes

              rh-ee-vemporop Vitaliy Emporopulo
              cvultur@redhat.com Constantin Daniel Vultur
              None
              None
              Yuri Obshansky Yuri Obshansky
              None
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: