Red Hat Bugzilla – Bug 972455
PRD33 - Select SPM as default host for new storage dialog
Last modified: 2016-04-18 02:53:07 EDT
Description of problem: When adding a new storage through the webadmin, the default host for the operation is selected randomly, this in some cases causes a performance flaw & bug prone behavior since the some of the operations are running on the HSM selected and the SPM operations are running on the SPM anyway so the default host selected should be the SPM in order to avoid this behavior Version-Release number of selected component (if applicable): RHEVM 3.2 How reproducible: 100% Steps to Reproduce: 1. In storage main tab click on "New Domain" 2. The "Use Host" box will contain a host chosen randomly 3. Actual results: The host selected is not always the SPM Expected results: The host selected should be the SPM Additional info:
No issues are found Verified, tested on RHEVM 3.3 - IS6 environment: RHEVM: rhevm-3.3.0-0.9.master.el6ev.noarch VDSM: vdsm-4.12.0-rc1.12.git8ee6885.el6.x86_64 LIBVIRT: libvirt-0.10.2-18.el6_4.9.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64 SANLOCK: sanlock-2.6-2.el6.x86_64
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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. http://rhn.redhat.com/errata/RHSA-2014-0038.html