Red Hat Bugzilla – Bug 856272
PRD34 -[RFE] Adding Disk to a VM which is not down adds a Disk that is not activated
Last modified: 2014-09-18 08:24:28 EDT
Created attachment 611823 [details]
engine log with the problem
Description of problem:
Run A VM with operating system installed and then try to add a Virtual Disk to VM. The disk will be added as deactivated
Steps to Reproduce:
1. Run a VM with operating system
2. Add a Virtual Disk to it
Disk is added as inactive
Disk should be activated when added
When performing attach disk - the disk is added as activated
iirc, that's the behavior in 3.1, which can be improved in a future version (adding a checkbox to the dialog about for 'activate').
(In reply to comment #1)
> iirc, that's the behavior in 3.1, which can be improved in a future version
> (adding a checkbox to the dialog about for 'activate').
what's the different between network and disk in this matter ? since for network object it works as expected.
(In reply to comment #2)
> (In reply to comment #1)
> > iirc, that's the behavior in 3.1, which can be improved in a future version
> > (adding a checkbox to the dialog about for 'activate').
> what's the different between network and disk in this matter ? since for
> network object it works as expected.
The difference that in network it is just 2 actions: attach and plug
For disk it is 'create, attach and plug'
The activation can be done in the endAction of the command.
Need to think whether we want to just change the behaviour, or leave it as a non-default option so it won't break customer's pre-existing automated flows (e.g., REST, automated tests, etc.)
ovirt 3.4.0 alpha has been released
*** Bug 1053887 has been marked as a duplicate of this bug. ***
*** Bug 1047273 has been marked as a duplicate of this bug. ***
Verified using 3.4 av2 (with RHEL guest)
TCMS run - https://tcms.engineering.redhat.com/run/119325/
please be aware to bug https://bugzilla.redhat.com/show_bug.cgi?id=1055403
(in case that Vm state is not up, the disk will be created and attached but won't be activated - audit logs appears)
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.