Bug 1557425 - SSH connect failed: CTR mode needs counter parameter, not IV ssh_connect [OSP 9]
Summary: SSH connect failed: CTR mode needs counter parameter, not IV ssh_connect [OSP 9]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-paramiko
Version: 9.0 (Mitaka)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: async
: 9.0 (Mitaka)
Assignee: Jason Joyce
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks: 1557427 1557428
TreeView+ depends on / blocked
 
Reported: 2018-03-16 14:46 UTC by Jason Joyce
Modified: 2018-04-11 18:02 UTC (History)
5 users (show)

Fixed In Version: python-paramiko-1.15.1-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1557427 1557428 (view as bug list)
Environment:
Last Closed: 2018-04-11 18:01:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1115 0 None None None 2018-04-11 18:01:59 UTC

Description Jason Joyce 2018-03-16 14:46:38 UTC
Description of problem:
Overcloud deployments using pxe_ssh fail with error: 'CTR mode needs counter parameter, not IV ssh_connect' on RHEL 7.5

Version-Release number of selected component (if applicable):
python-paramiko-1.15.1-1.el7ost

How reproducible:
Always

Steps to Reproduce:
1. Deploy undercloud
2. Deploy Overcloud with pxe_ssh

Actual results:
Overcloud deployment succeeds.

Comment 4 Filip Hubík 2018-04-10 11:46:00 UTC
Vefified by CI as jobs are passing since fixed package present (python-paramiko-1.15.1-2.el7ost), from job https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/phase2-9_director-rhel-7.5-virthost-1cont_1comp-ipv4-vxlan-lvm-ssl/4/ above.

See package versions in attachment:

$ cat packages-paramiko-ospd9-undercloud.log | grep paramiko
python-paramiko.noarch           1.15.1-2.el7ost        @rhelosp-9.0-puddle

Comment 8 errata-xmlrpc 2018-04-11 18:01:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1115


Note You need to log in before you can comment on or make changes to this bug.