Just to clarify, after getting the 'discard after delete not supported' error message, on the bottom of that window, did you un-checked the 'Discard After Delete' box and pressed ok?
Also, here's a 'how to fix' for a similar issue: https://access.redhat.com/solutions/3526901 *Regards,* *Shani Leviim* On Wed, Oct 31, 2018 at 4:19 PM Tryfon Farmakakis < farmakakistry...@gmail.com> wrote: > Screenshots and logs attached (I can't understand why am I getting the > "discard after delete not supported" error message since I have the > relevant checkbox unchecked) > No, the new storage domain is never created. Yes, the lun appears as > selectable. > > On Wed, Oct 31, 2018 at 11:51 AM Shani Leviim <slev...@redhat.com> wrote: > >> Hi, >> Can you please attach the engine.log? (and maybe some screenshots from >> the UI?) >> >> Also, when you're trying to re-create the storage domain, does that lun >> appear as selectable (which maybe indicates that the domain wasn't created), >> or the new storage domain appears on the storage domains list so it was >> created? >> >> >> *Regards,* >> >> *Shani Leviim* >> >> >> On Mon, Oct 29, 2018 at 6:12 PM Tryfon Farmakakis < >> farmakakistry...@gmail.com> wrote: >> >>> Hi, I have an oVirt 4.2.6.4 installation. I added a new Centos 7.5 host >>> and a new, still uninitialized Data Center with shared storage. I then try >>> to add a new iSCSI Data Storage Domain on this Data Center and I have >>> selected to use the only host I have where the iSCSI target also resides, >>> over a local device. command 'targetcli ls' outputs: >>> o- / >>> ......................................................................................................................... >>> [...] >>> o- backstores >>> .............................................................................................................. >>> [...] >>> | o- block >>> .................................................................................................. >>> [Storage Objects: 0] >>> | o- fileio >>> ................................................................................................. >>> [Storage Objects: 0] >>> | o- pscsi >>> .................................................................................................. >>> [Storage Objects: 1] >>> | | o- vicinityvolume >>> ........................................................................ >>> [/dev/iof/vicinityvolume activated] >>> | | o- alua >>> ................................................................................................... >>> [ALUA Groups: 0] >>> | o- ramdisk >>> ................................................................................................ >>> [Storage Objects: 0] >>> o- iscsi >>> ............................................................................................................ >>> [Targets: 1] >>> | o- iqn.2015-03.com.iofabric:vicinityvolume >>> ........................................................................... >>> [TPGs: 1] >>> | o- tpg1 >>> .................................................................................................. >>> [gen-acls, no-auth] >>> | o- acls >>> .......................................................................................................... >>> [ACLs: 0] >>> | o- luns >>> .......................................................................................................... >>> [LUNs: 1] >>> | | o- lun0 >>> .......................................................... >>> [pscsi/vicinityvolume (/dev/iof/vicinityvolume) (None)] >>> | o- portals >>> .................................................................................................... >>> [Portals: 1] >>> | o- 0.0.0.0:3260 >>> ..................................................................................................... >>> [OK] >>> o- loopback >>> ......................................................................................................... >>> [Targets: 0] >>> >>> iSCSI target is discovered successfully, login also works but then when >>> I click 'OK' button nothing happens. The iSCSI initiator seems to have been >>> created though. Command 'iscsiadm -m session' outputs: tcp: [1] >>> 44.128.20.202:3260,1 iqn.2015-03.com.iofabric:vicinityvolume (non-flash) >>> Command 'lsblk' outputs: >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>> sda 8:0 0 1,8T 0 disk >>> sdb 8:16 0 1,8T 0 disk >>> sdc 8:32 0 477G 0 disk >>> sdd 8:48 0 238,5G 0 disk >>> ├─sdd1 8:49 0 500M 0 part /boot >>> └─sdd2 8:50 0 238G 0 part >>> ├─centos-root 253:0 0 50G 0 lvm / >>> ├─centos-swap 253:1 0 15,7G 0 lvm [SWAP] >>> └─centos-home 253:2 0 172,2G 0 lvm /home >>> sde 8:64 0 3T 0 disk >>> sdf 8:80 0 3T 0 disk >>> sr0 11:0 1 1024M 0 rom >>> >>> The sde device is the original device to which the iSCSI target points >>> and sdf is the device created by the iSCSI initiator. >>> Any help would be appreciated. >>> _______________________________________________ >>> Users mailing list -- users@ovirt.org >>> To unsubscribe send an email to users-le...@ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/M5ZQQWCKIBX24R6K35TUREJXZJ7TMB2V/ >>> >>
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3QAKDNYXFANNRJOC375PUEPEDMJJ5EIP/
