Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Version-Release number of selected component (if applicable): CFME-5.7.1.1.20170206165110_3c42361 & RHV-4.0.5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/13913
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/8fdeaad475143da463d3cb88097c09d78e7c3b49 commit 8fdeaad475143da463d3cb88097c09d78e7c3b49 Author: Moti Asayag <masayag> AuthorDate: Tue Feb 14 17:22:46 2017 +0200 Commit: Moti Asayag <masayag> CommitDate: Tue Feb 14 17:35:27 2017 +0200 Disks should be added as 'active' in RHV PR https://github.com/ManageIQ/manageiq/pull/13318 introduced a new class to handle disk attachments. A disk should be added to RHV as 'active' since there is no method to modify it afterward. DiskAttachmentBuilder class will set the 'active' as the default status of the new disk, so any scenario which adds disks (vm reconfigure, automation request, provision request) will share the same behavior. https://bugzilla.redhat.com/show_bug.cgi?id=1422145 .../providers/redhat/infra_manager/disk_attachment_builder.rb | 3 +-- .../providers/redhat/infra_manager/disk_attachment_builder_spec.rb | 4 ++-- .../manageiq/providers/redhat/infra_manager/provision/disk_spec.rb | 2 +- 3 files changed, 4 insertions(+), 5 deletions(-)
Verified on CFME-5.8.0.1/RHV-4.0.7 VM reconfigure-> Hot added disk to a VM that already had a bootable disk. The disk was added & activated as expected.