Your message dated Mon, 05 Nov 2012 07:17:33 +0000
with message-id <[email protected]>
and subject line Bug#691805: fixed in xcp-storage-managers 0.1.1-3
has caused the Debian Bug report #691805,
regarding xcp-storage-managers: Wrong path in iSCSI storage driver script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
691805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691805
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xcp-storage-managers
Version: 0.1.1-2
Severity: important

Dear Maintainer,

I can not create an iSCSI storage resource using the following command:

xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over 
iSCSI SR"> shared=true device-config:target=192.168.10.100 
device-config:targetIQN=<here-target-iqn> device-config:SCSIid=<my-scsi-id> 
type=lvhdoiscsi

(Note that I created a symlink 
  ln -s /usr/lib/xcp/sm/LVHDoISCSISR.py /usr/lib/xcp/sm/LVHDoISCSISR
so the driver 'lvhdoiscsi' could be recognised.)

This command should print the UUID of the new SR in STDOUT if it has created 
the SR successfully, but It failed with these messages, among others:

There was an SR backend failure.
status: non-zero exit
stdout: 
stderr: Traceback (most recent call last):
  File "/usr/lib/xcp/sm/LVHDoISCSISR", line 384, in <module>
    SRCommand.run(LVHDoISCSISR, DRIVER_INFO)
  File "/usr/lib/xcp/sm/SRCommand.py", line 261, in run
    sr = driver(cmd, cmd.sr_uuid)
  File "/usr/lib/xcp/sm/SR.py", line 136, in __init__
    self.load(sr_uuid)
  File "/usr/lib/xcp/sm/LVHDoISCSISR", line 153, in load
    self._LUNprint(sr_uuid)
  File "/usr/lib/xcp/sm/LVHDoISCSISR", line 183, in _LUNprint
    self.iscsi.attach(sr_uuid)
  File "/usr/lib/xcp/sm/ISCSISR.py", line 274, in attach
    iscsilib.ensure_daemon_running_ok(self.localIQN)
  File "/usr/lib/xcp/sm/iscsilib.py", line 315, in ensure_daemon_running_ok
    if not is_iscsi_daemon_running():
File "/usr/lib/xcp/sm/iscsilib.py", line 198, in is_iscsi_daemon_running
    (rc,stdout,stderr) = util.doexec(cmd)
  File "/usr/lib/xcp/sm/util.py", line 129, in doexec
    proc = 
subprocess.Popen(args,stdin=subprocess.PIPE,stdout=subprocess.PIPE,stderr=subprocess.PIPE,close_fds=True)
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory


So I figured out that the SR creator script was trying to execute some binary 
using a wrongpath.

Comparing the /usr/lib/xcp/sm/iscsilib.py script from the xcp-storage-managers 
Debian package with its equivalent script shipped with XCP CentOS-based distro 
I could confirm that they are the same.

What I did was to alter line 198 of the /usr/lib/xcp/sm/iscsilib.py file from 
  cmd = ["/sbin/pidof", "-s", "/sbin/iscsid"]
to
  cmd = ["/bin/pidof", "-s", "/usr/sbin/iscsid"]
to reflect the actual path of the 'iscsid' binary in Debian.

However, I think it's more 'debianistic' to get this path each time the script 
runs (something like 'which iscsid') or make it configurable by some variable 
or config file.

Thanks in advance!


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xcp-storage-managers depends on:
ii  blktap-utils    2.0.90-1
ii  libc6           2.13-35
ii  libxenstore3.0  4.1.3-2
ii  python          2.7.3~rc2-1
ii  python2.7       2.7.3~rc2-2.1
ii  uuid-runtime    2.20.1-5.2

Versions of packages xcp-storage-managers recommends:
ii  lvm2        2.02.95-4
ii  nfs-common  1:1.2.6-3

xcp-storage-managers suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: xcp-storage-managers
Source-Version: 0.1.1-3

We believe that the bug you reported is fixed in the latest version of
xcp-storage-managers, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated xcp-storage-managers 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 04 Nov 2012 18:54:52 +0000
Source: xcp-storage-managers
Binary: xcp-storage-managers
Architecture: source amd64
Version: 0.1.1-3
Distribution: unstable
Urgency: low
Maintainer: PKG-Xen Devel <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Description: 
 xcp-storage-managers - storage backends for XCP
Closes: 687319 691805 691806 691808
Changes: 
 xcp-storage-managers (0.1.1-3) unstable; urgency=low
 .
   * Added missing dependency on sg3-utils and open-iscsi (Closes: #691806).
   * Fixes path to iscsid in iscsilib.py (Closes: #691805).
   * Fixes path to scsi_id in scsiutil.py, removes unknown --master parameter in
   lvutil.py (Closes: #691808).
   * Fix CDROM guest hotplug bug (LP: #1045739) (Closes: #687319).
   * Added a watch file.
   * Build-Conflicts: xcp-storage-managers, since that's just what happened to
   me at the dh_python2 stage.
Checksums-Sha1: 
 8b0519f8e3914ec6269b39341b4f7ddec15c392a 1579 xcp-storage-managers_0.1.1-3.dsc
 b5ecbfc87e1d2485d635d857e9675b134012f5cb 17766 
xcp-storage-managers_0.1.1-3.debian.tar.gz
 dfb50ae4185d5f5dabf1f0c36abe59ae2cac39bb 212800 
xcp-storage-managers_0.1.1-3_amd64.deb
Checksums-Sha256: 
 c7b6bf00922641fff48b93e9e49f5930e1dbd3f2eb67f65d290184f004c82e44 1579 
xcp-storage-managers_0.1.1-3.dsc
 23e09669334344f9ea6f372ac766c699606ac877ee9212bda7b27b7945d73652 17766 
xcp-storage-managers_0.1.1-3.debian.tar.gz
 e1c4c78a59d74ead19711997dc4d494846c028f68132d07f20ebbebbca803c87 212800 
xcp-storage-managers_0.1.1-3_amd64.deb
Files: 
 ca1f65d6552adb0c874fdb5451e829d7 1579 libs extra 
xcp-storage-managers_0.1.1-3.dsc
 6887febef7949845370de9bc32bb22fd 17766 libs extra 
xcp-storage-managers_0.1.1-3.debian.tar.gz
 f64d4232ccba0f3a8f8677ed6355406f 212800 libs extra 
xcp-storage-managers_0.1.1-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlCXcmUACgkQl4M9yZjvmkkklQCg1PMUiBRfI71rc68SEjx/XcAz
t+AAoLRbIXApC7bvyrv2ELQYFETXJ4Hp
=FSJC
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to