My context is one controller + compute node and two compute. all deploy by one packstack command line. I faced it on all role compute.
My first issue was the StrictHostKeyChecking and the SSH KEY indeed.
At this point I was able to run manually ssh as expect as "nova" user. But the issue was still here. As this point I understand, the user used to initiate the SSH session was not nova but nova_migration, so I should configure it as nova : access to the key and the .ssh/config.
Hi Javier, thanks for taking care of this.
My context is one controller + compute node and two compute. all deploy by one packstack command line. I faced it on all role compute.
My first issue was the StrictHostKeyCh ecking and the SSH KEY indeed.
At this point I was able to run manually ssh as expect as "nova" user. But the issue was still here. As this point I understand, the user used to initiate the SSH session was not nova but nova_migration, so I should configure it as nova : access to the key and the .ssh/config.
BR
Cyril