Bug 2072038

Summary: Missing SNO leadership election optimizations in 4.10 sriov network operator
Product: OpenShift Container Platform Reporter: browsell
Component: NetworkingAssignee: Ehila <ehila>
Networking sub component: SR-IOV QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: dosmith, ehila, keyoung, zzhao
Version: 4.10   
Target Milestone: ---   
Target Release: 4.10.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: sriov-network-operator-container-v4.10.0-202205110238.p0.g9d06eb1.assembly.stream Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-23 13:25:10 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:
Bug Depends On: 2075562    
Bug Blocks:    

Comment 4 Ehila 2022-05-11 17:52:34 UTC
Sure @zzhao, the way to verify that this worked as intended if you run the below command, you should see 270 being returned and not 15

oc get leases a56def2a.openshift.io -n openshift-sriov-network-operator -ojsonpath='{.spec.leaseDurationSeconds}{"\n"}'

Comment 7 zhaozhanqi 2022-05-17 01:54:59 UTC
Thank you @ehila 

Verified this bug on 4.10.0-202205161346

# oc get csv
NAME                                         DISPLAY                   VERSION               REPLACES                                     PHASE
sriov-network-operator.4.10.0-202205161346   SR-IOV Network Operator   4.10.0-202205161346   sriov-network-operator.4.10.0-202204291519   Succeeded


# oc get leases a56def2a.openshift.io -n openshift-sriov-network-operator -ojsonpath='{.spec.leaseDurationSeconds}{"\n"}'
270

Comment 9 errata-xmlrpc 2022-05-23 13:25:10 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 (OpenShift Container Platform 4.10.15 bug fix 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/RHBA-2022:2258