Bug 1265081

Reporduction step

install RHEVH 3.5 7.2
systemctl status vdsmd reports failed
systemct status iscsid reports failed

Chris, is this intended change in iscsid? This does not look like an valid
behavior change in a minor release (7.2).

(In reply to Nir Soffer from comment #2)
> Chris, is this intended change in iscsid? This does not look like an valid
> behavior change in a minor release (7.2).

I'm not sure what exactly the behavior being seen is.  Can you elaborate?

The only observable difference from 7.1 to 7.2 in iscsid should be the safe logout option, which unless the iscsid.conf file is edited to enable will be off by default to match existing behavior.

Maybe referring to the conditions in the iscsi.service file for starting sessions?  That hasn't changed since 7.0.

If so, the explanation here is wrong.  There are two triggering conditions (the service is started if either are true with the =| assignment), so the iscsiadm command should be run if either there exist node records to check in /var/lib/iscsi/nodes or if there exist running sessions in /sys/class/iscsi_sessions (in order to make sure iscsid is running for session recovery)

If iscsid.service is reporting failed, what's the reported reason for failing?

iscsid reports that it fails to start due to unfulfilled conditions.
reported by systemctl status iscsid.

Tolik, can you please attach journalctl -b, journalctl -u iscsid ?

Also: This looks like it should happen on 3.6 as well, not?

Hi

some basic logs and i will attach a sosreport

[root@node1 ~]# systemctl status vdsmd
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: disabled)
   Active: inactive (dead)

Sep 24 12:22:38 node1 systemd[1]: Dependency failed for Virtual Desktop Server Manager.
Sep 24 12:22:38 node1 systemd[1]: Job vdsmd.service/start failed with result 'dependency'.

[root@node1 ~]# systemctl status iscsi
● iscsi.service - Login and scanning of iSCSI devices
   Loaded: loaded (/usr/lib/systemd/system/iscsi.service; enabled; vendor preset: disabled)
   Active: inactive (dead)
Condition: start condition failed at Thu 2015-09-24 12:22:01 UTC; 35min ago
     Docs: man:iscsid(8)
           man:iscsiadm(8)

Sep 24 12:22:01 localhost systemd[1]: Started Login and scanning of iSCSI devices.

● vdsm-network.service - Virtual Desktop Server Manager network restoration
   Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-09-24 12:22:38 UTC; 36min ago
  Process: 11982 ExecStartPre=/usr/bin/vdsm-tool --vvverbose --append --logfile=/var/log/vdsm/upgrade.log upgrade-unified-persistence (code=exited, status=1/FAILURE)

Sep 24 12:22:37 node1 vdsm-tool[11982]: File "/usr/lib/python2.7/site-packages/vdsm/ipwrapper.py", line 506, in routeShowGateways
Sep 24 12:22:37 node1 vdsm-tool[11982]: File "/usr/lib/python2.7/site-packages/vdsm/ipwrapper.py", line 490, in _execCmd
Sep 24 12:22:37 node1 vdsm-tool[11982]: File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 742, in execCmd
Sep 24 12:22:37 node1 vdsm-tool[11982]: File "/usr/lib64/python2.7/site-packages/cpopen/__init__.py", line 51, in __init__
Sep 24 12:22:37 node1 vdsm-tool[11982]: File "/usr/lib64/python2.7/subprocess.py", line 712, in __init__
Sep 24 12:22:37 node1 vdsm-tool[11982]: TypeError: _execute_child_v276() got an unexpected keyword argument 'restore_sigpipe'
Sep 24 12:22:38 node1 systemd[1]: vdsm-network.service: control process exited, code=exited status=1
Sep 24 12:22:38 node1 systemd[1]: Failed to start Virtual Desktop Server Manager network restoration.
Sep 24 12:22:38 node1 systemd[1]: Unit vdsm-network.service entered failed state.
Sep 24 12:22:38 node1 systemd[1]: vdsm-network.service failed.
And attaching sosreport in next somment

Created attachment 1076541 [details]
sosreport

This failure

Sep 24 12:22:37 node1 vdsm-tool[11982]: TypeError: _execute_child_v276() got an unexpected keyword argument 'restore_sigpipe'

is unrelated to iscsid not starting; it's another issue tracked in bug 1264667.

hi .
it seems there is no iscsi bug
only cpopen problem 

systemctl status iscsi should be systemctl status iscsi which is running

leaves with cp-open bug 
duplicate of 1264667

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