Customer has 2 interfaces defined on their application node: bond0 used for node based backups. This is an unroutable interface that only connects to their SAN for backups. bond1 primary interface. Used for actual network traffic both to the node and for connecting to the SDN in OpenShift. Ideally, when a container is created, it should receive the IP information of the bond1 (routable) interface for its /etc/resolv.conf file. When this happens, things work as expected. There are certain times, as yet undefined, where the /etc/resolv.conf contains information from the bond0 (unroutable) interface which breaks SDN connectivity. We need a way to blacklist an interface to prevent it from being used during container creation. Customer case: https://access.redhat.com/support/cases/#/case/02402537
Chuck, is https://bugzilla.redhat.com/show_bug.cgi?id=1680059 the same?
Hi, Dan Looks very similar. We do see a lot of the same issues as noted in that one. Very likely this is a duplicate.