Dear maintainer(s),

With a recent upload of paramiko the autopkgtest of libcloud fails in
testing when that autopkgtest is run with the binary packages of
paramiko from unstable. It passes when run with only packages from
testing. In tabular form:

                        pass            fail
paramiko               from testing    2.10.3-1
libcloud               from testing    3.4.1-2
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of paramiko to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=paramiko

https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcloud/21182944/log.gz


=================================== FAILURES
===================================
                           expected_msg, mock.connect)

test/compute/test_ssh_client.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/libcloud/utils/py3.py:145: in
assertRaisesRegex
     return getattr(self, 'assertRaisesRegex')(*args, **kwargs)
E   AssertionError: SSHException not raised by connect
------------------------------ Captured log call 
-------------------------------
DEBUG    libcloud.compute.ssh:ssh.py:365 Connecting to server

Looks like it's a change in paramiko triggering this, that needs work
in libcloud (and possibly others) to restore compatibility.

See these upstream issues:
https://github.com/paramiko/paramiko/issues/1961
https://github.com/apache/libcloud/pull/1685

PR #1685 was included in upstream 'trunk' today. I cherry-picked the
patches but the test still fail.

It's correct that there is some compatibility issue with paramiko >=
2.9.0 but this test failure doesn't capture that. It's actually supposed
to be skipped.

If you look at the previous CI logs [1] this is correctly recognized and
skipped, this was with the version string '2.8.3'. The current version,
'2.10.4' is actually less than '2.7.0'.

Since the test isn't supposed to be executed, we could just patch it
out.


Håvard


[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libcloud/20809243/log.gz

We believe that the bug you reported is fixed in the latest version of
libcloud, 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 1010214@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Håvard F. Aasen <havard.f.aasen@pfft.no> (supplier of updated libcloud 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 15 May 2022 07:37:29 +0000
Source: libcloud
Architecture: source
Version: 3.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Håvard F. Aasen <havard.f.aasen@pfft.no>
Closes: 1010214 1010891
Changes:
 libcloud (3.4.1-3) unstable; urgency=medium
 .
   * Team upload.
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster:
     + Build-Depends: Drop versioned constraint on python3-lockfile and
       python3-mock.
     + python3-libcloud: Drop versioned constraint on python3-lockfile in
       Depends.
 .
   [ Håvard F. Aasen ]
   * Add patch to fix test failure on big-endian architectures. Closes: #1010891
   * Add patch to compare Paramiko versions. Closes: #1010214
 .
   [ Jeroen Ploemen ]
   * Control: bump Standards-Version to 4.6.1 (from 4.6.0; no further
     changes).
Checksums-Sha1:
 3c3047ea8b8611225bb422e9ec285f3520881396 2401 libcloud_3.4.1-3.dsc
 b318e7596661a186d7b2ac24fffdc7725210ceb5 18240 libcloud_3.4.1-3.debian.tar.xz
 10c5dbe2c58234a6afb3159510df9261648025e0 8613 libcloud_3.4.1-3_source.buildinfo
Checksums-Sha256:
 722529867dedf3cdc88a0fc42a79fcfcced7e32a2b22cb2c990a47050f7035d8 2401 libcloud_3.4.1-3.dsc
 04d5157fc20eb6869eba2828108075d6a9706eb04610fd61bf9ef6370dd2fdc8 18240 libcloud_3.4.1-3.debian.tar.xz
 0f26c4f0067858454619801e8eebffad30f38aa64121140624c9192ff59fce89 8613 libcloud_3.4.1-3_source.buildinfo
Files:
 14d52d15763351d328131e5ddf7d78ce 2401 python optional libcloud_3.4.1-3.dsc
 0ebdefade5b7dcb9674edeb0028bda19 18240 python optional libcloud_3.4.1-3.debian.tar.xz
 9c06dd62b24e1cbb5289560c61c35db5 8613 python optional libcloud_3.4.1-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmKArd0ACgkQQoMEoXSN
zHqUlxAAoBxXwEBQYEnwFhsqDaTOOkZGitWPOUx6qrNVvF2lb8hXmXyk360dL1+w
KzHslYGG8d2TjDPUMvmIk4OuBY5ltdTbVvhBSKfNRjkiC7kUontICv4zmyu8hY8I
Q2vPAxY5tuw68Oo4Fyp4XAv3DVI1pbLg6KgtO8CSKAMotD0wKT0GfK19WA+Z1LYW
Mp86p3HKFWjSphdI72GlWIbV7GpUWPY4vOG0PM5iGgNCNtJhrmE5Xbo65vZXN/A4
Ee0RH75kn08t6uUd5Cf1m4VNpQUxZnYbXfZnTCqQ50CB6oHF0ddCB6pOq0eHASf7
XdkQK/y2wV7jJSbMPjVGbfIbzZbpIyvlNbGB5KLHdeUIFZvBxdZodYo5DS0c3ZVj
5bkEL5mbFQI1GpVeqjDp0SOocN6jogmDGSM7a5EfkXwjlIf159rZrBUQ2rNgRlKB
ZoMW/yUBcMGt88dcgG5NT6YyHubS+PBTRV6CJRxe+PTjPVRWryEkQSCSSDv/o2KN
7cNCnDHej/EUjc/gIk9qxWz0IpQ/vNMaSaZUixlyAUknj2YQiylRJSembFNFJF82
MBti2kaOS917iiIy9+sAxd67ik4GgBc/OFoytuYvELTTPBZfRv1wadmdRJyPpQBm
0+BTO1MFov8hJFwaEv8sVIVlh7GV8i7dEQHrwhdfoJFvEsquyug=
=LH07
-----END PGP SIGNATURE-----