+++ This bug was initially created as a clone of Bug #1807998 +++ Description of problem: On Baremetal, and specially on IPv6 deploymnets, CRI-O's default setting of stream-address="" makes it bind to whichever address. That means that it can easily end up on the provisioning network. How reproducible: Often Steps to Reproduce: 1. Trigger a baremetal deployment 2. ssh to the different nodes 3. sudo ss -lptn | grep crio Actual results: Binds to provisioning network or some address not in the control plane. Expected results: Should be bound to a non VIP address on the control plane network (non-deprecated, non-link-local IPv6 address when IPv6 deployment). Additional info: You can check if crio got a stream address specified with a short command like in this example: [core@master-0 ~]$ cat "/proc/$(pgrep crio)/cmdline" | xargs -0 echo /usr/bin/crio --stream-address=fd2e:6f44:5dd8:c956::14 --enable-metrics=true --metrics-port=9537
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409