-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Platform] Use the correct SSH user for doing on-prem node preflight checks #7268
Comments
Yugaware onprem provider configuration LOG yugaware add instances LOG yugaware create universe LOG |
OS: oracle enterprise linux 7.7 with compatible kernel. When setup the provider with "centos" user, I can create a universe without issue. |
yugaware + replicated |
Summary: The preflight checks are always using "centos" for the ssh_user because it is not being passed down properly. Note that this already works for manual provisioning because we always specify ssh user in the script. Test Plan: Create instance, add a new ssh-able sudo user, remove ssh access to centos. Create universe and see if precheck passes the "SSH Connection" task. Reviewers: sanketh, arnav, daniel, sb-yb, spotachev Reviewed By: spotachev Subscribers: jenkins-bot, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D10650
…node preflight checks Summary: The preflight checks are always using "centos" for the ssh_user because it is not being passed down properly. Note that this already works for manual provisioning because we always specify ssh user in the script. Test Plan: Create instance, add a new ssh-able sudo user, remove ssh access to centos. Create universe and see if precheck passes the "SSH Connection" task. Reviewers: sanketh, arnav, daniel, sb-yb, spotachev Reviewed By: spotachev Subscribers: yugaware, jenkins-bot Differential Revision: https://phabricator.dev.yugabyte.com/D10651
…ecks Summary: The preflight checks are always using "centos" for the ssh_user because it is not being passed down properly. Note that this already works for manual provisioning because we always specify ssh user in the script. Test Plan: Create instance, add a new ssh-able sudo user, remove ssh access to centos. Create universe and see if precheck passes the "SSH Connection" task. Reviewers: sanketh, arnav, daniel, sb-yb, spotachev Reviewed By: spotachev Subscribers: jenkins-bot, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D10650
However, the manual provisioning step failed if I don't give
|
Currently onprem preflight checks are always using centos user. This should be changed to whatever is configured in the OnpremProvider configuration.
The text was updated successfully, but these errors were encountered: