Bug 2028325

Summary: disableDrain should be set automatically on SNO
Product: OpenShift Container Platform Reporter: browsell
Component: NetworkingAssignee: Sebastian Scheinkman <sscheink>
Networking sub component: SR-IOV QA Contact: yliu1
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: keyoung, trozet, yliu1, zshi
Version: 4.9   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: The sriov operator will mark the disableDrain in the sriovOperatorConfig as true when it gets installed on an SNO system automatically Reason: Before this change, the user needs to manually update the sriovOperatorConfig when installing on an SNO Result: the sriov operator works on SNO deployments out of the box no need for additional configurations
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:31:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 yliu1 2022-02-01 18:05:30 UTC
Verified passed with latest 4.9 ztp container image.

Comment 3 yliu1 2022-02-01 18:06:31 UTC
Revert state - previous comment is meant for a different bz.

Comment 4 yliu1 2022-02-01 18:11:05 UTC
Verified on 4.10 fc.2 using sriov operator from brew.

openshift-sriov-network-operator                   sriov-network-operator.4.10.0-202201310820   SR-IOV Network Operator                                  4.10.0-202201310820              Succeeded

 
[kni@ran-vcl01-installer ~]$ oc get sriovoperatorconfigs.sriovnetwork.openshift.io -A -o yaml |grep -i drain
    disableDrain: true

Comment 7 errata-xmlrpc 2022-03-10 16:31:35 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056