Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #319326 > unrolled thread

Bug#1010214: paramiko breaks libcloud autopkgtest: SSHException not raised by connect

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1010214: paramiko breaks libcloud autopkgtest: SSHException not raised by connect Paul Gevers <elbrus@debian.org> - 2022-04-26 17:10 +0200
    Processed: paramiko breaks libcloud autopkgtest: SSHException not  raised by connect "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-04-26 17:10 +0200
    Bug#1010214: 1010214 Jeroen Ploemen <jcfp@debian.org> - 2022-05-09 19:30 +0200
      Bug#1010214: paramiko breaks libcloud autopkgtest: SSHException not raised by connect Håvard F. Aasen <havard.f.aasen@pfft.no> - 2022-05-14 20:20 +0200
    Bug#1010214: marked as done (paramiko breaks libcloud  autopkgtest: SSHException not raised by connect) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-05-15 12:40 +0200

#319326 — Bug#1010214: paramiko breaks libcloud autopkgtest: SSHException not raised by connect

[Multipart message — attachments visible in raw view] — view raw

Source: paramiko, libcloud
Control: found -1 paramiko/2.10.3-1
Control: found -1 libcloud/3.4.1-2
Severity: serious
Tags: sid bookworm
User: debian-ci@lists.debian.org
Usertags: breaks needs-update

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 
===================================
__________ ParamikoSSHClientTests.test_key_file_non_pem_format_error 
___________

self = <test.compute.test_ssh_client.ParamikoSSHClientTests 
testMethod=test_key_file_non_pem_format_error>

     @patch('paramiko.SSHClient', Mock)
     @unittest.skipIf(paramiko_version >= '2.7.0',
                      'New versions of paramiko support OPENSSH key format')
     def test_key_file_non_pem_format_error(self):
         path = os.path.join(os.path.dirname(__file__),
                             'fixtures', 'misc',
                             'test_rsa_non_pem_format.key')
             # Supplied as key_material
         with open(path, 'r') as fp:
             private_key = fp.read()
             conn_params = {'hostname': 'dummy.host.org',
                        'username': 'ubuntu',
                        'key_material': private_key}
             mock = ParamikoSSHClient(**conn_params)
             expected_msg = 'Invalid or unsupported key type'
>       assertRaisesRegex(self, paramiko.ssh_exception.SSHException,
                           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

[toc] | [next] | [standalone]

#319329 — Processed: paramiko breaks libcloud autopkgtest: SSHException not raised by connect

Processing control commands:

> found -1 paramiko/2.10.3-1
Bug #1010214 [src:paramiko, src:libcloud] paramiko breaks libcloud autopkgtest: SSHException not raised by connect
Marked as found in versions paramiko/2.10.3-1.
> found -1 libcloud/3.4.1-2
Bug #1010214 [src:paramiko, src:libcloud] paramiko breaks libcloud autopkgtest: SSHException not raised by connect
Marked as found in versions libcloud/3.4.1-2.

-- 
1010214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#319741 — Bug#1010214: 1010214

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#319938

> 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.

> @unittest.skipIf(paramiko_version >= '2.7.0',

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

[toc] | [prev] | [next] | [standalone]

#319951 — Bug#1010214: marked as done (paramiko breaks libcloud autopkgtest: SSHException not raised by connect)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 15 May 2022 10:35:06 +0000
with message-id <E1nqBac-000Blf-Kt@fasolo.debian.org>
and subject line Bug#1010214: fixed in libcloud 3.4.1-3
has caused the Debian Bug report #1010214,
regarding paramiko breaks libcloud autopkgtest: SSHException not raised by connect
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 owner@bugs.debian.org
immediately.)


-- 
1010214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010214
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web