Description of problem:
One of our Cu is trying to upgrade an RHOSP12 environment to RHOSP13.
It's a predeployed nodes environment, where the nodes itself get provisioned by the Customer.
When running the "openstack overcloud upgrade run --nodes ControllerDeployedServer" command, it fails.
The error is caused by a playbook trying to "Gather facts" from the Overcloud Nodes, in this case, the controllers. It fails with a connection issue, not being able to ssh into the machine.
We checked the logs on the overcloud nodes and found the try to login to the system. It was rejected due to an unknown ssh key was used.
We checked with the local key from the director node (the one in /home/stack/.ssh/id_rsa) and found it not matching the key which was used to access the node.
After some searching we found the key the director tried to use:
Its a separate key from mistral and not the stack's user key which is normally used by the director.
It seems to be related to validations, which we can't use on a pre-deployed nodes environment.
So we tried to re-run the upgrade with --skip-tags validation, but it failed with the same issue.
Version-Release number of selected component (if applicable):
$ rpm -qa | grep tripleo-heat-temp
Steps to Reproduce:
- Follow the official guide instructions to upgrade pre-deployed nodes.
- The upgrade is failing because it uses different ssh key
- The upgrade should be successful
We followed the steps as mentioned in our official document:
Seems like you're missing "Preparing for Pre-Provisioned Nodes Upgrade" part which enables ssh for those nodes for 'triplo-admin' user. I don't see those 13 upgrade docs though. Probably a docs bug.
I'm reducing the urgency/priority to high seeing as the customer issue has been resolved. I've also assigned the bug specifically to the docs folks who work with upgrades.