Hide Forgot
Description of problem: When using the wizard with template using data source the resulting vm use pvc source Version-Release number of selected component (if applicable): 4.10 How reproducible: Steps to Reproduce: 1. Use the wizard to create a virtual machine 2. Choose a template the uses datasource (for example rhel8) 3. create a VM without customizing the disks. Actual results: A vm is created with main disk source pointing to a pvc with name and namespaces matching the datasource from the template Expected results: A vm is created with main disk source pointing to a datasource with name and namespaces matching the datasource from the template Additional info:
Opening on 4.11, we will need to backport to 4.10 after a fix is verified on static plugin for 4.11 cc:// @tnisan @agilboa
blocker -, this is a bug for 4.10.z, it does not appear in the dynamic plugin for 4.11
Yaacov, any reason for needinfo on me?
no just cc' ing you and Tal
Raising severity. I believe that this bug practically debilitates CNV 4.10 crown-jewel feature (ever-updated boot source for new VMs).
Yaacov Zamir, if this bug is for 4.10.z (and does not reproduce in 4.11) why is the bug targeted to 4.11. We would like this fixed in 4.10.z ASAP.
> Yaacov Zamir, if this bug is for 4.10.z (and does not reproduce in 4.11) why is the bug targeted to 4.11. We would like this fixed in 4.10.z ASAP. Hi, this is an 4.10.z issue, the bug is for 4.11 is because of OCP CI process, we need to first have a fix for 4.11. otherwise a fix will not get merged to the 4.10 branch. The process in OCP is that we have to first fix in 4.11, verify the fix on 4.11 and then backport to 4.10, Git automation will not allow to merge a fix to the 4.10 branch without a verified bug on 4.11, AFKU this process will not slow down the fix because in most cases backpacking is automated (sometimes automated backporting is no possible due to conflicts, but usually automation just works)
Matan hi, This is a 4.10 bug, automatic back porting failed [1], please back port manually. I can help with the Bugzilla cloning if necessary. cc:// Tal [1] https://github.com/openshift/console/pull/11457#issuecomment-1124553856
verified on 4.11 master
(In reply to Yaacov Zamir from comment #11) > Matan hi, > This is a 4.10 bug, automatic back porting failed [1], please back port > manually. > I can help with the Bugzilla cloning if necessary. > > cc:// Tal > > [1] https://github.com/openshift/console/pull/11457#issuecomment-1124553856 Create a manual PR for 4.10 branch. Updated in the bug https://bugzilla.redhat.com/show_bug.cgi?id=2084489 https://github.com/openshift/console/pull/11485 @yzamir @tnisan @gouyang
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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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. https://access.redhat.com/errata/RHSA-2022:5069