Description of problem: When the config parameters in vdsm scsi_rescan_minimal_timeout or scsi_rescan_maximal_timeout are illegal, when used in forceIscsiScan will throw an unhandled exception. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.change scsi_rescan_minimal_timeout to -1 2.restart vdsm Actual results: Expected results: Additional info:
http://gerrit.ovirt.org/#/c/9690/
Merged I005f6343f2d8775dbf8406dffe04f6de93a81fce
No issues are found Steps for verification: 1) Add line: scsi_rescan_minimal_timeout = -1 to file : /etc/vdsm/vdsm.conf 2) Restart VDSM service service vdsmd stop && service vdsmd start 3) Create a Master DC in iSCSI DC environment Verified on RHEVM 3.2 - SF03 environment RHEVM: rhevm-3.2.0-4.el6ev.noarch VDSM: vdsm-4.10.2-3.0.el6ev.x86_64 LIBVIRT: libvirt-0.10.2-13.el6.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64 SANLOCK: sanlock-2.6-2.el6.x86_64
This bug is currently attached to errata RHBA-2012:14332. 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-2013-0886.html