Bug 1841154

Summary: Cannot add Attach Disk to Virtual Machine Template because of disabled PVC select dropdown
Product: OpenShift Container Platform Reporter: Radim Hrazdil <rhrazdil>
Component: Console Kubevirt PluginAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, fkrepins, tjelinek
Target Milestone: ---Keywords: UpcomingSprint
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause and Consequence: It was not possible to Attach Disk to Virtual Machine Template Fix and Result: It is possible to Attach Disk to Virtual Machine Template
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:42:41 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:

Description Radim Hrazdil 2020-05-28 13:42:52 UTC
Description of problem:
When user attempts to Attach disk to a VM Template, the PVC selector is disabled, and a PVC then cannot be selected.
The same flow works as expected with a Virtual Machine.

apiVersion: cdi.kubevirt.io/v1alpha1
kind: DataVolume
  name: example-import-dv
      - ReadWriteOnce
        storage: 500Mi
      url: >-

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

Steps to Reproduce:
1. Create example Template
2. Create a DV, example given above
3. Try to add attach disk to the VM Template

Actual results:
PVC Selector is disabled, so the dialog cannot be submitted

Comment 1 Tomas Jelinek 2020-05-29 08:24:52 UTC
working on it now

Comment 4 Radim Hrazdil 2020-06-01 07:41:44 UTC
Verified on release-4.5
Attaching a disk works as expected, deleting a VMT with attached disk doesn't delete the attached disk

Comment 5 errata-xmlrpc 2020-07-13 17:42:41 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.