Description of problem: All types of events can display on the new GUI including DataVolume. Other events can be filtered except DataVolume. Screenshot attached. Version-Release number of selected component (if applicable): openshift v3.11.43 CNV v1.3.0 brew-pulp cnv-tech-preview/kubevirt-web-ui:v1.3.0-4 How reproducible: Always Steps to Reproduce: 1. Create a VM 2. Check Event/Status on the new GUI 3. Filter different types on the new GUI Actual results: As description. Expected results: Events about DataVolume can be filtered. Additional info:
Created attachment 1507356 [details] DataVolume-Events
Created attachment 1507357 [details] All-Types-Events
Created attachment 1507358 [details] PVC-Events
Created attachment 1507359 [details] DataVolume-Status
Created attachment 1507360 [details] All-Types-Status
*** Bug 1651470 has been marked as a duplicate of this bug. ***
That is a core functionality of the openshift. It lists all the PVCs as the entities according to which you can filter and than if you pick one, it tries to filter according to "involved object->kind". Can you please provide the "oc describe event <the event you think should show up>"?
The entire events are: [cloud-user@cnv-executor-qwang-master1 ~]$ oc get events LAST SEEN FIRST SEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE 26m 26m 1 localregistry-import-vm-apb-wldlc.156966691f9d2ec6 ServiceInstance Normal Provisioning service-catalog-controller-manager The instance is being provisioned asynchronously 26m 26m 4 localregistry-import-vm-apb-wldlc.156966695b9b8a46 ServiceInstance Normal Provisioning service-catalog-controller-manager The instance is being provisioned asynchronously (action started) 26m 26m 1 qwang-1-cirros.1569666ffc772a66 VirtualMachine Normal SuccessfulDataVolumeCreate virtualmachine-controller Created DataVolume vm-qwang-1-cirros-dv-01 26m 26m 1 localregistry-import-vm-apb-wldlc.156966705c379713 ServiceInstance Normal ProvisionedSuccessfully service-catalog-controller-manager The instance was provisioned successfully 26m 26m 1 importer-vm-qwang-1-cirros-dv-01-jc6pw.15696675dedf6582 Pod Normal Scheduled default-scheduler Successfully assigned qwang-1/importer-vm-qwang-1-cirros-dv-01-jc6pw to cnv-executor-qwang-node1.example.com 26m 26m 1 vm-qwang-1-cirros-dv-01.15696675e566fe8e DataVolume Normal ImportScheduled datavolume-controller Import into vm-qwang-1-cirros-dv-01 scheduled 26m 26m 1 vm-qwang-1-cirros-dv-01.15696675da251e66 PersistentVolumeClaim Normal ProvisioningSucceeded persistentvolume-controller Successfully provisioned volume pvc-7933a97b-ee34-11e8-9ce1-fa163e1aff1b using kubernetes.io/glusterfs 26m 26m 15 importer-vm-qwang-1-cirros-dv-01-jc6pw.1569666fbbb5b3fb Pod Warning FailedScheduling default-scheduler pod has unbound PersistentVolumeClaims (repeated 2 times) 25m 25m 1 importer-vm-qwang-1-cirros-dv-01-jc6pw.15696676741252b3 Pod spec.containers{importer} Normal Pulling kubelet, cnv-executor-qwang-node1.example.com pulling image "cnv-tech-preview/virt-cdi-importer:v1.3.0" 25m 25m 1 importer-vm-qwang-1-cirros-dv-01-jc6pw.15696677c0013598 Pod spec.containers{importer} Normal Started kubelet, cnv-executor-qwang-node1.example.com Started container 25m 25m 1 importer-vm-qwang-1-cirros-dv-01-jc6pw.15696677bc7457e7 Pod spec.containers{importer} Normal Created kubelet, cnv-executor-qwang-node1.example.com Created container 25m 25m 1 importer-vm-qwang-1-cirros-dv-01-jc6pw.15696677ae843406 Pod spec.containers{importer} Normal Pulled kubelet, cnv-executor-qwang-node1.example.com Successfully pulled image "cnv-tech-preview/virt-cdi-importer:v1.3.0" 25m 25m 1 vm-qwang-1-cirros-dv-01.15696677e0c8d89a DataVolume Normal ImportInProgress datavolume-controller Import into vm-qwang-1-cirros-dv-01 in progress 22m 22m 1 importer-vm-qwang-1-cirros-dv-01-jc6pw.156966a3449833de Pod spec.containers{importer} Normal Killing kubelet, cnv-executor-qwang-node1.example.com Killing container with id cri-o://importer:Need to kill Pod 22m 22m 1 vm-qwang-1-cirros-dv-01.156966a342bff5a5 DataVolume Normal ImportSucceded datavolume-controller Successfully imported into PVC vm-qwang-1-cirros-dv-01 13m 26m 13 vm-qwang-1-cirros-dv-01.1569666fbf436265 DataVolume Normal Synced datavolume-controller DataVolume synced successfully 9m 9m 1 vm-qwang-1-cirros-dv-01.156967624b0d65b3 DataVolume Normal Synced datavolume-controller DataVolume synced successfully I want to show a DataVolume event: [cloud-user@cnv-executor-qwang-master1 ~]$ oc describe event vm-qwang-1-cirros-dv-01.156966a342bff5a5 Name: vm-qwang-1-cirros-dv-01.156966a342bff5a5 Namespace: qwang-1 Labels: <none> Annotations: <none> API Version: v1 Count: 1 Event Time: <nil> First Timestamp: 2018-11-22T08:59:58Z Involved Object: API Version: cdi.kubevirt.io Kind: DataVolume Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10445 UID: 7930bee4-ee34-11e8-9ce1-fa163e1aff1b Kind: Event Last Timestamp: 2018-11-22T08:59:58Z Message: Successfully imported into PVC vm-qwang-1-cirros-dv-01 Metadata: Creation Timestamp: 2018-11-22T08:59:58Z Resource Version: 10956 Self Link: /api/v1/namespaces/qwang-1/events/vm-qwang-1-cirros-dv-01.156966a342bff5a5 UID: fd161d01-ee34-11e8-9ce1-fa163e1aff1b Reason: ImportSucceded Reporting Component: Reporting Instance: Source: Component: datavolume-controller Type: Normal Events: <none> To compare, I want to show a PVC event: [cloud-user@cnv-executor-qwang-master1 ~]$ oc describe event vm-qwang-1-cirros-dv-01.15696675da251e66 Name: vm-qwang-1-cirros-dv-01.15696675da251e66 Namespace: qwang-1 Labels: <none> Annotations: <none> API Version: v1 Count: 1 Event Time: <nil> First Timestamp: 2018-11-22T08:56:43Z Involved Object: API Version: v1 Kind: PersistentVolumeClaim Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10266 UID: 7933a97b-ee34-11e8-9ce1-fa163e1aff1b Kind: Event Last Timestamp: 2018-11-22T08:56:43Z Message: Successfully provisioned volume pvc-7933a97b-ee34-11e8-9ce1-fa163e1aff1b using kubernetes.io/glusterfs Metadata: Creation Timestamp: 2018-11-22T08:56:43Z Resource Version: 10403 Self Link: /api/v1/namespaces/qwang-1/events/vm-qwang-1-cirros-dv-01.15696675da251e66 UID: 88e3bd28-ee34-11e8-9ce1-fa163e1aff1b Reason: ProvisioningSucceeded Reporting Component: Reporting Instance: Source: Component: persistentvolume-controller Type: Normal Events: <none> The entire event: [cloud-user@cnv-executor-qwang-master1 ~]$ oc describe event | grep -A6 Involved Involved Object: API Version: v1 Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10268 UID: 7936ac5e-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: v1 Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10271 UID: 7936ac5e-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: v1 Field Path: spec.containers{importer} Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10406 -- Involved Object: API Version: v1 Field Path: spec.containers{importer} Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10406 -- Involved Object: API Version: v1 Field Path: spec.containers{importer} Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10406 -- Involved Object: API Version: v1 Field Path: spec.containers{importer} Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10406 -- Involved Object: API Version: v1 Field Path: spec.containers{importer} Kind: Pod Name: importer-vm-qwang-1-cirros-dv-01-jc6pw Namespace: qwang-1 Resource Version: 10406 -- Involved Object: API Version: servicecatalog.k8s.io/v1beta1 Kind: ServiceInstance Name: localregistry-import-vm-apb-wldlc Namespace: qwang-1 Resource Version: 10124 UID: 67eb709e-ee34-11e8-b288-0a580a800012 -- Involved Object: API Version: servicecatalog.k8s.io/v1beta1 Kind: ServiceInstance Name: localregistry-import-vm-apb-wldlc Namespace: qwang-1 Resource Version: 10128 UID: 67eb709e-ee34-11e8-b288-0a580a800012 -- Involved Object: API Version: servicecatalog.k8s.io/v1beta1 Kind: ServiceInstance Name: localregistry-import-vm-apb-wldlc Namespace: qwang-1 Resource Version: 10180 UID: 67eb709e-ee34-11e8-b288-0a580a800012 -- Involved Object: API Version: kubevirt.io/v1alpha2 Kind: VirtualMachine Name: qwang-1-cirros Namespace: qwang-1 Resource Version: 10260 UID: 792ec7d4-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: cdi.kubevirt.io Kind: DataVolume Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10261 UID: 7930bee4-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: v1 Kind: PersistentVolumeClaim Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10266 UID: 7933a97b-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: cdi.kubevirt.io Kind: DataVolume Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10264 UID: 7930bee4-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: cdi.kubevirt.io Kind: DataVolume Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10410 UID: 7930bee4-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: cdi.kubevirt.io Kind: DataVolume Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10445 UID: 7930bee4-ee34-11e8-9ce1-fa163e1aff1b -- Involved Object: API Version: cdi.kubevirt.io/v1alpha1 Kind: DataVolume Name: vm-qwang-1-cirros-dv-01 Namespace: qwang-1 Resource Version: 10954 UID: 7930bee4-ee34-11e8-9ce1-fa163e1aff1b
Thank you for the data. Patch posted: https://github.com/kubevirt/web-ui/pull/118
Created attachment 1524147 [details] dataVolume Attach a new screenshot to show that the dataVolume is filtered in events page.
verified on 1.4.0-10.