© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The issue is present with build:20190602T
The workflow to reproduce this issue is:
1. Swact to controller-1
2. lock controller-0
3. unlock controller-0
This reboots the node
4. Try to login.
This is what we see when we try to login:
```
ssh 192.168.200.82
Warning: Permanently added '192.168.200.82' (ECDSA) to the list of known hosts.
Release 19.01
-------
W A R N I N G *** W A R N I N G *** W A R N I N G *** W A R N I N G ***
-------
THIS IS A PRIVATE COMPUTER SYSTEM.
This computer system including all related equipment, network devices
(specifically including Internet access), are provided only for authorized use.
All computer systems may be monitored for all lawful purposes, including to
ensure that their use is authorized, for management of the system, to
facilitate protection against unauthorized access, and to verify security
procedures, survivability and operational security. Monitoring includes active
attacks by authorized personnel and their entities to test or verify the
security of the system. During monitoring, information may be examined,
recorded, copied and used for authorized purposes. All information including
personal information, placed on or sent over this system may be monitored. Uses
of this system, authorized or unauthorized, constitutes consent to monitoring
of this system. Unauthorized use may subject you to criminal prosecution.
Evidence of any such unauthorized use collected during monitoring may be used
for administrative, criminal or other adverse action. Use of this system
constitutes consent to monitoring for these purposes.
wrsroot@
Last login: Tue Jun 4 10:57:40 2019 from 192.168.200.3
/etc/motd.
WARNING: Unauthorized access to this system is forbidden and will be
prosecuted by law. By accessing this system, you agree that your
actions may be monitored if unauthorized usage is suspected.
```
As you can see above, we are able to open the SSH connection, and also, we are able to put the password, but, that's it. There is no shell, nor error message.
As Erich pointed out, with `ssh 192.168.200.82 -t bash` we can login into the system, but mysql has a huge CPU usage. I attached the output of top.