Bug 2024535 - hotplug disk missing OwnerReference
Summary: hotplug disk missing OwnerReference
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Aviv Turgeman
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-18 09:43 UTC by Aviv Turgeman
Modified: 2022-03-10 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:29:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10505 0 None open Bug 2024535: hotplug disk missing OwnerReference 2021-11-18 10:27:37 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:29:38 UTC

Description Aviv Turgeman 2021-11-18 09:43:08 UTC
Description of problem:
hotplug DataVolume is missing VM OwnerReference when created on UI.

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

How reproducible:

Steps to Reproduce:
1. create a hotplug disk via disk modal on UI (with an option that creates PVC)
2. click the action kebab and delete the hotplug
3. click on PersistentVolumeClaims nav on the right.
4. see PVC created for hotplug still exist


1. create a hotplug disk via disk modal on UI (with an option that creates PVC)
2. click on created PVC and move to PVC detail page
3. click on the DV owner of the PVC and move to DV detail page
4. visit DV YAML file and see no `OwnerReferences` field existing 
   see on DV detail page that the owner field is empty.

Comment 2 Guohua Ouyang 2021-11-25 04:38:49 UTC
verified on master

Comment 6 errata-xmlrpc 2022-03-10 16:29:22 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.10.3 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.


Note You need to log in before you can comment on or make changes to this bug.