Bug 1829068

Summary: misconfigured prow jobs lead to failure with text step needs a lease but no lease client provided
Product: OpenShift Container Platform Reporter: Gabe Montero <gmontero>
Component: InstallerAssignee: Abhinav Dahiya <adahiya>
Installer sub component: openshift-installer QA Contact: Yunfei Jiang <yunjiang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: bleanhar
Version: 4.5   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:32:29 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:

Description Gabe Montero 2020-04-28 20:09:41 UTC 
From buildcop duty

See https://search.svc.ci.openshift.org/?search=step+needs+a+lease+but+no+lease+client+provided&maxAge=48h&context=1&type=junit&name=&maxMatches=5&maxBytes=20971520&groupBy=job

for list of tests with the bad openshift/release config

See https://bugzilla.redhat.com/show_bug.cgi?id=1828401#c2 for instructions from Steve K. on recommendations to fix your prow jobs so they can acquire leases

tl;dr discussion in https://coreos.slack.com/archives/CEKNRGF25/p1588098415417500

Jobs which were deemed to go to install team:

1) release-openshift-ocp-e2e-aws-scaleup-rhel7-*
2) release-openshift-ocp-installer-e2e-aws-upi-*
Comment 1 Abhinav Dahiya 2020-05-11 16:56:21 UTC 
This is a CI only fix, and the fix was done thanks to bparees.. https://github.com/openshift/release/pull/8977
Comment 2 Gabe Montero 2020-05-19 12:39:24 UTC 
The search CI query I noted in my description no longer turns up hits like it did when I opened this during build cop duty.

And the prow history for the jobs I noted in the description have lots of clean runs.

As this bz's creator I'm marking this verified.
Comment 4 errata-xmlrpc 2020-07-13 17:32:29 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