Created attachment 1815125 [details] ip a and dmesg from all 5 nodes 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
Created attachment 1815127 [details] system2 ip a and dmesg Tested on another system and the same behavior is seen
@cvultur Which type of environment is it? Do you see it in test infra or anywhere else?
I am seeing it in the QE environment/libvirt in TLV lab
I see that the last message is 8 months old. Is it still observed with more recent versions? If may already be resolved by another change.
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-8946