Bug 1827688

Summary: URL k8s/<namespace>/virtualmachines should be disabled or point to k8s/<namespace>/virtualization
Product: OpenShift Container Platform Reporter: Radim Hrazdil <rhrazdil>
Component: Console Kubevirt PluginAssignee: Yaacov Zamir <yzamir>
Status: CLOSED ERRATA QA Contact: Nelly Credi <ncredi>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, fkrepins, yzamir
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:31:25 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 Radim Hrazdil 2020-04-24 14:29:11 UTC 
Description of problem:
After changing the Virtualization structure, when a user navigates to 
k8s/<namespace>/virtualmachines
There is list of virtual machines, which displays only some VM attributes and does't allow all actions from the kebab menu.

Since it looks quite similar to the current list view at
k8s<namespace>/virtualization, I think we should either display the same content of disable the k8s<namespace>/virtualmachines url so that user cannot get confused whu some of the functionality is suddenly not available.



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

How reproducible:
100%

Steps to Reproduce:
1. Create some VM in <namespace>
2. Navigate to k8s<namespace>/virtualmachines
3.

Actual results:
VM is displayed, but with limited functionality in the kebab menu and some attributes not being displayed

Expected results:
user should be presented with the same page as at k8s<namespace>/virtualization or redirected there
Comment 1 Yaacov Zamir 2020-05-05 07:00:32 UTC 
*** Bug 1825293 has been marked as a duplicate of this bug. ***
Comment 4 Radim Hrazdil 2020-05-14 11:42:30 UTC 
Verified 4.5.0-0.nightly-2020-05-12-065413
Comment 5 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