Bug 1827644 - When user deletes a vm from all-namespace, the namespace is change to the one of the deleted VM
Summary: When user deletes a vm from all-namespace, the namespace is change to the one...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Yaacov Zamir
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-24 12:31 UTC by Radim Hrazdil
Modified: 2020-07-13 17:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:31:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:31:42 UTC

Description Radim Hrazdil 2020-04-24 12:31:54 UTC 
Description of problem:
When a user displys VMs in all-namespace, and deletes a VM that is for example in namespace default, then upon deletion of the VM, the namespace is switcher to default.

Tested on pods, where this doesn't happen.


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

How reproducible:
100%
Comment 1 Yaacov Zamir 2020-05-06 10:51:14 UTC 
submitted upstream:
https://github.com/openshift/console/pull/5303
Comment 2 Yaacov Zamir 2020-05-12 15:10:27 UTC 
merged upstream:
https://github.com/openshift/console/pull/5303
Comment 5 Radim Hrazdil 2020-05-20 11:54:57 UTC 
Verified in console release-4.5 branch commit: 5994c64ee529b650bae348ef78ebc23dca8db5c5
Comment 6 errata-xmlrpc 2020-07-13 17:31:25 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
Note You need to log in before you can comment on or make changes to this bug.