Bug 1557427

Summary: SSH connect failed: CTR mode needs counter parameter, not IV ssh_connect [OSP 9]
Product: Red Hat OpenStack Reporter: Jason Joyce <jjoyce>
Component: python-paramikoAssignee: Jason Joyce <jjoyce>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: cstratak, fhubik, jjoyce, python-maint, skatlapa, srevivo, torsava
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 8.0 (Liberty)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-paramiko-1.15.1-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1557425 Environment:
Last Closed: 2018-04-11 18:01:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1557425, 1557428    
Bug Blocks:    

Description Jason Joyce 2018-03-16 14:47:27 UTC 
+++ This bug was initially created as a clone of Bug #1557425 +++

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:39:21 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/phase1-8_director-rhel-7.5-virthost-1cont_1comp_1ceph-ipv4-vxlan-ceph/8/ above.

See package versions in attachment:

$ cat packages-paramiko-ospd8.log | grep paramiko
python-paramiko.noarch           1.15.1-2.el7ost         @rhos-8.0-signed
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