yahoo-eng-team team mailing list archive

[sean mooney <smooney@xxxxxxxxxx>]

marking as invalid as this is likely an issue wiht the ssh client you are using ro the ssh server in the guest.
the fact it works on linux but not windows/android suggest to me it might be related to the authentication methods
or encryption algothims and key types supproted in the client/server and is likely not related to openstack/nova

** Changed in: nova
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1802218

Title:
  An instance created by openstack rocky can't be remotely connected by
  xshell and putty, But SSH tools for Linux systems do. [server's host
  key did not match the signature supplied]

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  The mirror images adopted include:
  1. Use xshell, putty, JuiceSSH cannot connect [http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud-1805.qcow2]
  2. Cannot connect with xshell, putty and JuiceSSH [centos7.4 made by myself, no problem with Ocata version built before]
  3. With xshell, putty and JuiceSSH, you can connect [http://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img]
  After the failure, attempts were made to recreate the SSH keys in the system, but to no avail.

  The order is as follows:
  [root@host-192-168-1-10 ~]# rm -f /etc/ssh/ssh_host_*
  [root@host-192-168-1-10 ~]# systemctl restart sshd.service

  
  It environment
  [root@all-in-one-202 ~]# rpm -qa | grep rocky
  centos-release-openstack-rocky-1-1.el7.centos.noarch
  [root@all-in-one-202 ~]# 
  [root@all-in-one-202 ~]# rpm -qa | grep nova
  openstack-nova-conductor-18.0.2-1.el7.noarch
  openstack-nova-console-18.0.2-1.el7.noarch
  openstack-nova-api-18.0.2-1.el7.noarch
  python2-novaclient-11.0.0-1.el7.noarch
  openstack-nova-common-18.0.2-1.el7.noarch
  openstack-nova-placement-api-18.0.2-1.el7.noarch
  openstack-nova-compute-18.0.2-1.el7.noarch
  openstack-nova-novncproxy-18.0.2-1.el7.noarch
  openstack-nova-scheduler-18.0.2-1.el7.noarch
  python-nova-18.0.2-1.el7.noarch
  [root@all-in-one-202 ~]#
  [root@all-in-one-202 ~]# rpm -qa | egrep -i "libvirt|kvm"
  libvirt-daemon-driver-network-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-scsi-3.9.0-14.el7_5.8.x86_64
  libvirt-libs-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-disk-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-nwfilter-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-logical-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-nodedev-3.9.0-14.el7_5.8.x86_64
  qemu-kvm-common-ev-2.10.0-21.el7_5.7.1.x86_64
  libvirt-daemon-driver-storage-core-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-rbd-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-mpath-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-secret-3.9.0-14.el7_5.8.x86_64
  qemu-kvm-ev-2.10.0-21.el7_5.7.1.x86_64
  libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-interface-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-kvm-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-qemu-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-3.9.0-14.el7_5.8.x86_64
  libvirt-client-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-3.9.0-14.el7_5.8.x86_64
  libvirt-daemon-driver-storage-iscsi-3.9.0-14.el7_5.8.x86_64
  libvirt-python-3.9.0-1.el7.x86_64
  [root@all-in-one-202 ~]#
  [root@all-in-one-202 ~]# rpm -qa | grep neutron
  python2-neutron-lib-1.18.0-1.el7.noarch
  python2-neutronclient-6.9.1-1.el7.noarch
  openstack-neutron-common-13.0.1-2.el7.noarch
  openstack-neutron-ml2-13.0.1-2.el7.noarch
  openstack-neutron-13.0.1-2.el7.noarch
  python-neutron-13.0.1-2.el7.noarch
  openstack-neutron-linuxbridge-13.0.1-2.el7.noarch

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1802218/+subscriptions