Bug 2000499

Summary:	If export app toast is not cleared by the user and a new one is triggered then old toast download gives 404
Product:	OpenShift Container Platform	Reporter:	Jaivardhan Kumar <jakumar>
Component:	Dev Console	Assignee:	Jaivardhan Kumar <jakumar>
Status:	CLOSED ERRATA	QA Contact:	spathak <spathak>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.9	CC:	aos-bugs, mifiedle, nmukherj, sbudhwar, viraj
Target Milestone:	---
Target Release:	4.9.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:	2021-10-18 17:50:59 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 Jaivardhan Kumar 2021-09-02 09:31:53 UTC

Description of problem:  If export app toast is not cleared by the user and a new one is triggered then old toast download gives 404


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Install primer operator
2. create an ns and add a deployment
3. export app and wait for it to complete
4. export app again once step 2 is done but don't dismiss the final toast or click download


Actual results: can see multiple toast and old toast has download link which gives 404


Expected results: once export CR gets deleted then associated toast should get auto dismissed


Additional info:

Comment 3 Vikram Raj 2021-09-08 15:55:37 UTC

Verified it on 4.9.0-0.nightly-2021-09-06-055314. And it works as expected. Old toast get cleared when a new download CR gets created.

Comment 6 errata-xmlrpc 2021-10-18 17:50:59 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.9.0 bug fix and 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-2021:3759