Skip to content
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

Merged
merged 1 commit into from Nov 12, 2016

Conversation

dLobatog
Copy link
Member

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.

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.
@dLobatog dLobatog merged commit d48167c into theforeman:master Nov 12, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant