Description of problem: Need additional Login Username and Password Fields for Chap Authentication for ExtremeIO. Currently only Authentication Username and Password fields exist Version-Release number of selected component (if applicable): rhevm-3.6.0-0.11.master.el6.noarch - running on Rhel6.7 vdsm-4.17.2-1.el7ev.noarch - running on Rhel7.2 How reproducible: 100% Steps to Reproduce: 1. Via the ExtremeIO server set and Authentication username and password as well as a Login username and password 2. Via Webadmin -> Add new Storage Domain -> Scsci Domain -> Enter the IP of the ExtremeIO server. 3. Check the User Authentication option ->>>>> Only a password and username field for Authentication is displayed. Enter the Authenticaion username and password and press Discover. 4. We need and addtional username and password field for Login. In the case of the ExtremeIO server we have seperate Authetication and Login usernames and passwords. A TEMPORARY WORK AROUND IS TO CHANGE THE USER NAME AND PASSWORD BETWEEN THE DISCOVERY OPERATION AND THE LOGING OPERATION Actual results: We are missing Login username and password for Login into the storage server Expected results: We should have 2 userame and password fields for Chap Authentication: One for the Discovery operation and another for the Login operation Additional info: See Screen shot
Adding log reference to loging failure: -------------------------------------------------------- 2015-08-23 12:14:21,848 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-11) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM level1_vm01 command failed: Failed discovery of iSCSI targets: "portal=IscsiPortal(hostname=u'10.35.146.129', port=3260), err=(24, [], ['iscsiadm: Login failed to authenticate with target ', 'iscsiadm: discovery login to 10.35.146.129 rejected: initiator failed authorization', '', 'iscsiadm: Could not perform SendTargets discovery: iSCSI login failed due to authorization failure'])" 2015-08-23 12:14:21,848 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] (ajp-/127.0.0.1:8702-11) [] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand' return value 'IQNListReturnForXmlRpc:{status='StatusForXmlRpc [code=475, message=Failed discovery of iSCSI targets: "portal=IscsiPortal(hostname=u'10.35.146.129', port=3260), err=(24, [], ['iscsiadm: Login failed to authenticate with target ', 'iscsiadm: discovery login to 10.35.146.129 rejected: initiator failed authorization', '', 'iscsiadm: Could not perform SendTargets discovery: iSCSI login failed due to authorization failure'])"]'}' 2015-08-23 12:14:21,848 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] (ajp-/127.0.0.1:8702-11) [] HostName = level1_vm01 2015-08-23 12:14:21,848 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] (ajp-/127.0.0.1:8702-11) [] Command 'DiscoverSendTargetsVDSCommand(HostName = level1_vm01, DiscoverSendTargetsVDSCommandParameters:{runAsync='true', hostId='22e9edd5-fa6a-49b0-b875-625143058955', connection='StorageServerConnections:{id='null', connection='10.35.146.129', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}'})' execution failed: VDSGenericException: VDSErrorException: Failed in vdscommand to DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets: "portal=IscsiPortal(hostname=u'10.35.146.129', port=3260), err=(24, [], ['iscsiadm: Login failed to authenticate with target ', 'iscsiadm: discovery login to 10.35.146.129 rejected: initiator failed authorization', '', 'iscsiadm: Could not perform SendTargets discovery: iSCSI login failed due to authorization failure'])" 2015-08-23 12:14:21,848 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] (ajp-/127.0.0.1:8702-11) [] FINISH, DiscoverSendTargetsVDSCommand, log id: 6038305f 2015-08-23 12:14:21,849 ERROR [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery] (ajp-/127.0.0.1:8702-11) [] Query 'DiscoverSendTargetsQuery' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets: "portal=IscsiPortal(hostname=u'10.35.146.129', port=3260), err=(24, [], ['iscsiadm: Login failed to authenticate with target ', 'iscsiadm: discovery login to 10.35.146.129 rejected: initiator failed authorization', '', 'iscsiadm: Could not perform SendTargets discovery: iSCSI login failed due to authorization failure'])" (Failed with error iSCSIDiscoveryError and code 475) 2015-08-23 12:14:21,849 ERROR [org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery] (ajp-/127.0.0.1:8702-11) [] Exception: org.ovirt.engine.core.common.errors.EngineException: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed in vdscommand to DiscoverSendTargetsVDS, error = Failed discovery of iSCSI targets: "portal=IscsiPortal(hostname=u'10.35.146.129', port=3260), err=(24, [], ['iscsiadm: Login failed to authenticate with target ', 'iscsiadm: discovery login to 10.35.146.129 rejected: initiator failed authorization', '', 'iscsiadm: Could not perform SendTargets discovery: iSCSI login failed due to authorization failure'])" (Failed with error iSCSIDiscoveryError and code 475) at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:112) [bll.jar:] at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33) [bll.jar:] at org.ovirt.engine.core.bll.storage.DiscoverSendTargetsQuery.executeQueryCommand(DiscoverSendTargetsQuery.java:16) [bll.jar:] at org.ovirt.engine.core.bll.QueriesCommandBase.executeCommand(QueriesCommandBase.java:82) [bll.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33) [dal.jar:] at org.ovirt.engine.core.bll.Backend.runQueryImpl(Backend.java:537) [bll.jar:] at org.ovirt.engine.core.bll.Backend.runQuery(Backend.java:511) [bll.jar:] at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) [:1.8.0_51] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_51] at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_51]
Created attachment 1066039 [details] engine, vdsm, server logs, screen shots Added logs and sceen shots
If we want to support Xtreme-IO in a sensible manner we definitely need this, but it may be relevant to other storage vendors too. Regardless, we had this issue since RHEVM 3.1, and changing the way the dialog is laid out is something I'm too enthusiastic to do at this point in time. Yaniv, this sounds like more of an RFE than a bug to me. Your two cents?
Indeed a RFE. Tal, can you add the workaround for this?
Workaround is as follows: -In webadmin go to Storage -> New Domain -> iSCSI -In the discovery window enter the address and the credentials and click 'Discover' -Log into the relevant targets and select the desired LUNs -Before clicking on 'OK', change the credentials in the discovery window to the login credentials and click 'OK'
Can you please make sure this gets documented in a KBase for using Xtreme-IO in RHEV?
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
For now it doesn't seem like we're planning a refactor of the new block storage domain dialog plus a workaround exists, if somehow it's really important for someone please reopen.