-
Notifications
You must be signed in to change notification settings - Fork 335
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
SSH key not added to created VM when ssh_key
parameter is set
#1734
Labels
bug
Something isn't working
has_pr
PR fixes have been made
medium_priority
Medium priority
work in
In trying to solve, or in working with contributors
Comments
TheSpy0
changed the title
SSH key not added to create VM
SSH key not added to created VM when Sep 30, 2024
ssh_key
parameter is set
Fred-sun
added
work in
In trying to solve, or in working with contributors
bug
Something isn't working
labels
Oct 8, 2024
sample as:
|
@Fred-sun Thank you. To be able to test this parameter, I just need to clone your repository in the project directory and use the |
Yes! Please! |
It works for me when using your updated collection. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
has_pr
PR fixes have been made
medium_priority
Medium priority
work in
In trying to solve, or in working with contributors
SUMMARY
When creating a virtual machine inside a DevTest Lab, an SSH public key is not added to the
authorized_keys
file when thessh_key
parameter is set using either a path to the public key, the contents of the key (have tried as a string and using a file lookup), or the name of an SSH key stored in Azure. The module documentation was not clear on how it is supposed to be set.ISSUE TYPE
COMPONENT NAME
azure_rm_devtestlabvirtualmachine
moduleANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Fedora release 39 (Thirty Nine)
STEPS TO REPRODUCE
Run a playbook with the task below defined, using either the contents of the SSH key, or a lookup plugin with the file path to the key.
EXPECTED RESULTS
Expecting there to be a public key in
~/.ssh/authorized_keys
file.ACTUAL RESULTS
The
~/.ssh/authorized_keys
file is present but empty.The text was updated successfully, but these errors were encountered: