Description of problem: Although "node.startup = automatic" and "node.conn[0].startup = automatic" are configured in a specific portal to start automatically after reboot no login is done although iscsid is running. How reproducible: It happens always. Steps to Reproduce: 1. In /etc/iscsi/iscsi.conf the correct path for the iscsi daemon has to be specified. In mga6 the daemon (iscsid) if installed in /sbin. So, the part of the daemon configuration has to be adjusted: ###################### # iscsid daemon config ###################### # If you want iscsid to start the first time a iscsi tool # needs to access it, instead of starting it when the init # scripts run, set the iscsid startup command here. This # should normally only need to be done by distro package # maintainers. # # Default for Fedora and RHEL. (uncomment to activate). #iscsid.startup = /etc/rc.d/init.d/iscsid force-start # # Default for upstream open-iscsi scripts (uncomment to activate). iscsid.startup = /sbin/iscsid If this is not done iscsiadm cannot start the daemon: iscsiadm -m discovery -t st -p 192.168.10.10 sh: /etc/rc.d/init.d/iscsid: Datei oder Verzeichnis nicht gefunden iscsiadm: can not connect to iSCSI daemon (111)! sh: /etc/rc.d/init.d/iscsid: Datei oder Verzeichnis nicht gefunden iscsiadm: can not connect to iSCSI daemon (111)! iscsiadm: Cannot perform discovery. Initiatorname required. iscsiadm: Could not perform SendTargets discovery: could not connect to iscsid 2. start the daemon: systemctl start open-iscsi.service 3. configure nodes: iscsiadm -m discovery -t sendtargets -p 192.168.10.10:3260 4. login into specific portal: iscsiadm --mode node --targetname iqn.2010-08.eu.n-tec:icebox-rix6r-000905600:dev0.ctr1 --portal 192.168.10.10:3260 --login 5. After login the new device can be configured. I created a volume group and some logical volumes which have been formatted with xfs and can be mounted via an entry in /etc/fstab: ... /dev/vg_icebox/lv_projects /projects xfs _netdev,rw,inode64,logbufs=8 1 2 ... 6. logout of the portal: iscsiadm --mode node --targetname iqn.2010-08.eu.n-tec:icebox-rix6r-000905600:dev0.ctr1 --portal 192.168.10.10:3260 --logout 7. update iface parameters for automatic login: iscsiadm -m node -T iqn.2010-08.eu.n-tec:icebox-rix6r-000905600:dev0.ctr1 -p 192.168.10.10 --op update -n node.startup -v automatic iscsiadm -m node -T iqn.2010-08.eu.n-tec:icebox-rix6r-000905600:dev0.ctr1 -p 192.168.10.10 --op update -n node.conn[0].startup -v automatic 8. reboot the system
Assigning to the registered maintainer. This bug has status "NEW - FIXED", too, I don't know what's wrong with our Bugzilla :-( Also, the Assignee and CC fields no longer auto-complete when starting to write the name of a maintainer.
Assignee: bugsquad => lists.jjorgeCC: (none) => LpSolit, marja11, stormiSource RPM: (none) => open-iscsi
CC: LpSolit, stormi => (none)
This package had lost it's upstream site for long. But it seems it was revived in git hub : https://github.com/open-iscsi/open-iscsi Can you report there this bug, as this isn't clearly a packaging bug? Thanks.
It seems that the open-iscsi package in mga6 is missing an "iscsi login/logout" service. See issue "open-iscsi does not automatically login into portal" on https://github.com/open-iscsi/open-iscsi/issues/73
This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL). Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
CC: (none) => ouaurelienStatus: NEW => RESOLVEDResolution: (none) => OLD