This repository has been archived by the owner on Oct 18, 2019. It is now read-only.
Fixes #17323 - Allow SSH provisioning with CR cert #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
SSH provisioning does not work. Only PXE provisioning is possible
through smart proxies in an Azure network.
The reason is that the setSSHWaitForResponse does not come with support
for using keys other than the foreman user ones.
Solution:
The certificate passed on to the Azure compute resource can be used to
SSH provision these machines as soon as they get a public IP.
The vm_user attribute that's passed on to Azure via fog will be the
username, and sudo is allowed in most Azure images.