Red Hat Bugzilla – Bug 1428284
[RFE] VMware VM Add Disk be able to specify controller type
Last modified: 2018-03-01 08:10:28 EST
https://github.com/ManageIQ/manageiq-providers-vmware/pull/117
New commit detected on ManageIQ/manageiq-providers-vmware/master: https://github.com/ManageIQ/manageiq-providers-vmware/commit/bf9e15582c19e34ae38b91fc9fda2e36c319011b commit bf9e15582c19e34ae38b91fc9fda2e36c319011b Author: Adam Grare <agrare@redhat.com> AuthorDate: Mon Oct 2 14:31:33 2017 -0400 Commit: Adam Grare <agrare@redhat.com> CommitDate: Mon Oct 2 14:31:33 2017 -0400 Allow type of controller to be passed in disk opts When adding a new disk when a new controller is needed we currently try to use the same type of controller that is already on the VM or we have a default that we use. If a user wants to specify specifically what type of controller they want there is no way to do that. This adds the option to the disk options hash to have the new scsi controller type explicitly defined by the user. https://bugzilla.redhat.com/show_bug.cgi?id=1428284 .../providers/vmware/infra_manager/vm/reconfigure.rb | 9 ++++++--- .../vmware/infra_manager/vm/reconfigure_spec.rb | 18 +++++++++++++++--- 2 files changed, 21 insertions(+), 6 deletions(-)
UI Pivotal story here: https://www.pivotaltracker.com/story/show/152116440
Valid options are: VirtualLsiLogicController, ParaVirtualSCSIController, VirtualBusLogicController, and VirtualLsiLogicSASController VirtualLsiLogicController should be the default.
https://github.com/ManageIQ/manageiq-providers-vmware/pull/126 https://github.com/ManageIQ/manageiq-ui-classic/pull/2494
In testing the new disk was added to the existing controller no matter what type was selected.
This only applies to the case when a new controller needs to be added so the 1st, 16th, etc.. disk
Thanks Adam.
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://access.redhat.com/errata/RHSA-2018:0380