Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1808018

Summary: On Baremetal platform CRI-O often binds its streaming port on unsuitable addresses
Product: OpenShift Container Platform Reporter: Antoni Segura Puimedon <asegurap>
Component: Machine Config OperatorAssignee: Antoni Segura Puimedon <asegurap>
Status: CLOSED ERRATA QA Contact: Nataf Sharabi <nsharabi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Multiple available networks on worker nodes make it difficult to pick an address on the control plane for CRI-O. Consequence: CRI-O often binds to a non control plane interface Fix: Make CRI-O systemd service depend on a service that chooses the right interface and configures the CRI-O service. Result: CRI-O binds to an address in the control plane.
 Story Points: ---
Clone Of: 1807998 Environment:
Last Closed: 2020-07-13 17:21:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1807998    

Description Antoni Segura Puimedon 2020-02-27 16:23:45 UTC 
+++ 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
Comment 3 errata-xmlrpc 2020-07-13 17:21:52 UTC 
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