Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 958864

Summary: iscsi volumes not connected after reboot
Product: Red Hat Enterprise Linux 7 Reporter: michal novacek <mnovacek>
Component: iscsi-initiator-utilsAssignee: Chris Leech <cleech>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0CC: agrover
Target Milestone: rcKeywords: TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-02 14:58:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 883874, 1080147    

Description michal novacek 2013-05-02 14:43:46 UTC
Description of problem:
Iscsi  do not reconnect iscsi volumes after reboot even though they are marked
as active (running) by systemctl status.

Version-Release number of selected component (if applicable):
RHEL 7.0 Alpha3 (Maipo)
iscsi-initiator-utils-6.2.0.873-2.el7.x86_64

How reproducible: always

Steps to Reproduce:
1. iscsiadm -m discovery -t sendtargets -p IP
2. iscsiadm -m node --login
3. iscsiadm -m session -o show #volume seen connected
4. systemctl start iscsid iscsi
5. systemctl enable iscsid iscsi
6. reboot

Actual results: iscsi disk not connected after reboot

Expected results: iscsi disk connected after reboot

Additional info:
[...system rebooted with running iscsi, iscsid and connected iscsi drive]

# systemctl status iscsi
iscsi.service - LSB: Starts and stops login and scanning of iSCSI devices.
          Loaded: loaded (/etc/rc.d/init.d/iscsi)
          Active: active (exited) since Thu 2013-05-02 16:17:06 CEST; 16min ago
         Process: 2509 ExecStart=/etc/rc.d/init.d/iscsi start (code=exited, status=0/SUCCESS)

May 02 16:17:06 bucek-01.privatering3.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting LSB: Starts and stops login and scanning of iSCSI devices....
May 02 16:17:06 bucek-01.privatering3.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started LSB: Starts and stops login and scanning of iSCSI devices..

# systemctl status iscsid
iscsid.service - LSB: Starts and stops login iSCSI daemon.
          Loaded: loaded (/etc/rc.d/init.d/iscsid)
          Active: active (running) since Thu 2013-05-02 16:17:06 CEST; 16min ago
         Process: 2379 ExecStart=/etc/rc.d/init.d/iscsid start (code=exited, status=0/SUCCESS)
        Main PID: 2496 (iscsid)
          CGroup: name=systemd:/system/iscsid.service
                  ├─2491 iscsiuio
                  ├─2495 iscsid
                  └─2496 iscsid

May 02 16:17:05 bucek-01.privatering3.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Starting LSB: Starts and stops login iSCSI daemon....
May 02 16:17:06 bucek-01.privatering3.cluster-qe.lab.eng.brq.redhat.com iscsid[2379]: [34B blob data]
May 02 16:17:06 bucek-01.privatering3.cluster-qe.lab.eng.brq.redhat.com systemd[1]: Started LSB: Starts and stops login iSCSI daemon..
May 02 16:17:07 bucek-01.privatering3.cluster-qe.lab.eng.brq.redhat.com iscsid[2495]: iSCSI daemon with pid=2496 started!

# /etc/init.d/iscsi start
Starting iscsi (via systemctl):  [  OK  ]

# cat /proc/partitions 
major minor  #blocks  name

   8        0  292935982 sda
   8        1     512000 sda1
   8        2  292422656 sda2
  11        0    1048575 sr0
 253        0    4194304 dm-0
 253        1   52428800 dm-1
 253        2  235798528 dm-2

# iscsiadm -m node --login
Logging in to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.123715a987, portal: 172.17.4.7,3260] (multiple)
Login to [iface: default, target: iqn.1986-03.com.hp:storage.p2000g3.123715a987, portal: 172.17.4.7,3260] successful.

# cat /proc/partitions 
major minor  #blocks  name

   8        0  292935982 sda
   8        1     512000 sda1
   8        2  292422656 sda2
  11        0    1048575 sr0
 253        0    4194304 dm-0
 253        1   52428800 dm-1
 253        2  235798528 dm-2
   8       16  333984320 sdb

Comment 1 michal novacek 2013-05-02 14:58:32 UTC

*** This bug has been marked as a duplicate of bug 864036 ***