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

Bug 1829069

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: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: aconstan, btofel
Version: 4.5   
Target Milestone: ---   
Target Release: ---   
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-05-07 13:14:46 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:15:21 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 network team:

1) release-openshift-ocp-installer-e2e-aws-proxy-*
Comment 1 Brett Tofel 2020-04-30 14:10:18 UTC 
From Build Cop duty as well:

Here is another job saying same:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-release-openshift-origin-installer-e2e-aws-4.5-cnv/75
Comment 2 Alexander Constantinescu 2020-05-07 13:14:46 UTC 
Don't know what this is doing in networkings corner. But I found this bug which details the same problem so I am closing this as a dupe:

*** This bug has been marked as a duplicate of bug 1828401 ***