[devops][2.9] BadHostKeyException when time-sync because of paramiko update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Critical
|
Dennis Dmitriev |
Bug Description
Used devops version: git+git:
Detailed bug description:
Changes introduced in paramiko==2.2.0
https:/
cause time-sync fail when trying connect to slave node:
self.
File "/home/
self.
File "/home/
new_time = sync_time(
File "/home/
return func(*args, **kwargs)
File "/home/
with GroupNtpSync(env, node_names) as g_ntp:
File "/home/
remote = get_node_
File "/home/
keys=
File "/home/
auth=auth)
File "/home/
self.
File "/home/
return func(*args, **kwargs)
File "/home/
log=True)
File "/home/
client.
File "/home/
raise BadHostKeyExcep
BadHostKeyExcep
Steps to reproduce:
dos.py time-sync envname
dos.py revert-resume envname snapshotname also affected
slaves (not admin) with installed system must be exists in env
Reproducibility: 100%
Workaround: Use paramiko==2.1.2
summary: |
- [devops] BadHostKeyException when time-sync because of paramiko update + [devops][2.9] BadHostKeyException when time-sync because of paramiko + update |
Changed in fuel: | |
assignee: | nobody → Fuel DevOps (fuel-devops) |
importance: | Undecided → Critical |
Changed in fuel: | |
milestone: | none → 9.x-updates |
tags: | added: blocker-for-qa |
Fix proposed to branch: release/2.9 /review. openstack. org/474182
Review: https:/