+++ This bug was initially created as a clone of Bug #1912563 +++ Description of problem: p&f: clean up executing request on panic carry upstream PR: https://github.com/kubernetes/kubernetes/pull/97206
(don't see 4.8 yet)
sttts, I don't know what the process is here. The fix has already landed for 4.7, 4.6 and 4.5. This BZ does not apply to a future release 4.8. We can close it, rigt?
when 4.8 rebase is complete, qe needs to verify that there is no regression. The other alternative is we close this BZ
** WARNING ** This BZ claims that this bug is of urgent severity and priority. Note that urgent priority means that you just declared emergency within engineering. Engineers are asked to stop whatever they are doing, including putting important release work on hold, potentially risking the release of OCP while working on this case. Be prepared to have a good justification ready and your own and engineering management are aware and has approved this. Urgent bugs are very expensive and have maximal management visibility. NOTE: This bug was assigned to engineering manager with severity reset to *unspecified* until the emergency is vetted and confirmed. Please do not manually override the severity.
> I don't know what the process is here. The fix has already landed for 4.7, 4.6 and 4.5 From the past comment, looks like 4.5 already has the fix, this BZ was created to satisfy the dependency check when 4.8 did not show up in the BZ list. closing it now.