Red Hat Bugzilla – Bug 1070823
PRD35 - [RFE] Wipe after Delete flag modification while VM is Up
Last modified: 2016-02-10 15:24:44 EST
Description of problem: In RHEV 3.3 the "Wipe after Delete" option is not greyed out, however when attempting to modify the setting, an error pops out. The setting should be modifiable on live VMs. Version-Release number of selected component (if applicable): RHEV-M 3.3.0 How reproducible: iSCSI storage domains Steps to Reproduce: 1. start VM 2. press "Edit" on the disk 3. enable "Wipe after Delete" (this option is not grayed out) Actual results: Following error is displayed "Cannot edit Virtual Machine Disk. At least one of the VMs is not down." Expected results: New setting is applied successfully
it's not going to be modifiable until BZ 922377 gets in ATM it should be grayed out
eh, actually, you don't just want to apply it after shutdown, you want it to be immediately effective, right? Then it just needs to be declared in the code as such
Hi, First of all, I am unsure if it is possible or not to set "Wipe after Delete" while the VM is up, but it should not affect any runtime operations: the wipe is triggered only on disk/snapshot removal. This is the initial goal of the BZ. Second, at the moment in RHEV 3.3 this option is not greyed out for some reason, however any changes of the field produce an error. So for now, the option must be greyed out, but in the future I'd like to see a possibility to add the flag on the fly.
(In reply to Michal Skrivanek from comment #1) > it's not going to be modifiable until BZ 922377 gets in > ATM it should be grayed out Setting target release based on this comment.
(In reply to Allon Mureinik from comment #4) > (In reply to Michal Skrivanek from comment #1) > > it's not going to be modifiable until BZ 922377 gets in > > ATM it should be grayed out > Setting target release based on this comment. Actually, this is a /disk/ property, not a /vm/ property, which is only used when the disk/vm is removed, so I'm not sure why this is true. Michal - can you elaborate?
it is not, see my next comment 2 correcting this:) it should be doable, you just need to change the code to allow it, IMO
(In reply to Michal Skrivanek from comment #7) > it is not, see my next comment 2 correcting this:) > > it should be doable, you just need to change the code to allow it, IMO Hmm... missed that. Thanks!
https://tcms.engineering.redhat.com/run/163706 please be aware to depend on bugs
using vt3.1 , looks like the "wipe after delete" flag is greyed out. not sure what changed but it was working and passed tests and now it is not.
Was broken by Ib8b9f2860fd186651311814d0087c47f4083c863.
this bug was moved to MODIFIED before vt4 build date thus moving to ON_QA. if you belive this bug isn't in vt4, please report to rhev-integ@redhat.com
verified on vt4
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://rhn.redhat.com/errata/RHSA-2015-0158.html