@ykashtan What are the next steps here? Is this a fix we can absorb? /KenY
I think there's already a BZ on OCP to utilize this new behavior. I also think this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1946079 (among others) and I believe the right solution would be to augment installer/MCO so that node will wait for either ipv4 or ipv6 based on cluster IPs (ie if api ip is ipv4, wait for ipv4, if it's ipv6 wait for ipv6)
@ykashtan, > I think there's already a BZ on OCP to utilize this new behavior. Do you have a specific one we should track? > I also think this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1946079 (among others) We should track this one? > and I believe the right solution would be to augment installer/MCO so that node will wait for either ipv4 or ipv6 based on cluster IPs (ie if api ip is ipv4, wait for ipv4, if it's ipv6 wait for ipv6) How do we promote this as the right solution? What do we do with this bug in the meantime? /KenY
Closing. OCP engineering has requested we use an alternative method for trackers.