SSH sudo issue with chef provisioner. Terrafrom version 0.11.11

[i255d]

#6967 (comment)

It would be nice if the link above referenced a version of Terraform that the above link refers to.
I see this a lot with the issues posted in Git Hub and the responses by Terraform. Often the responses lack context and or references.

module.vserver.azurerm_virtual_machine.vm (chef): Connecting to remote host via SSH...
module.vserver.azurerm_virtual_machine.vm (chef): Host: 10.210.0.5
module.vserver.azurerm_virtual_machine.vm (chef): User: hdiadmin
module.vserver.azurerm_virtual_machine.vm (chef): Password: true
module.vserver.azurerm_virtual_machine.vm (chef): Private key: false
module.vserver.azurerm_virtual_machine.vm (chef): SSH Agent: false
module.vserver.azurerm_virtual_machine.vm (chef): Checking Host Key: false
module.vserver.azurerm_virtual_machine.vm (chef): Connected!

module.vserver.azurerm_virtual_machine.vm (chef): We trust you have received the usual lecture from the local System
module.vserver.azurerm_virtual_machine.vm (chef): Administrator. It usually boils down to these three things:

module.vserver.azurerm_virtual_machine.vm (chef): #1) Respect the privacy of others.
module.vserver.azurerm_virtual_machine.vm (chef): #2) Think before you type.
module.vserver.azurerm_virtual_machine.vm (chef): #3) With great power comes great responsibility.

module.vserver.azurerm_virtual_machine.vm (chef): [sudo] password for User_admin:
module.vserver.azurerm_virtual_machine.vm: Still creating... (1m40s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (1m50s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (2m0s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (2m10s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (2m20s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (2m30s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (2m40s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (2m50s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (3m0s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (3m10s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (3m20s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (3m30s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (3m40s elapsed)
odule.vserver.azurerm_virtual_machine.vm: Still creating... (7m30s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (7m40s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (7m50s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (8m0s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (8m10s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (8m20s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (8m30s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (8m40s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (8m50s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (9m0s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (9m10s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (9m20s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (9m30s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (9m40s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (9m50s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (10m0s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (10m10s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (10m20s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (10m30s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (10m40s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (10m50s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (11m0s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (11m10s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (11m20s elapsed)
module.vserver.azurerm_virtual_machine.vm: Still creating... (11m30s elapsed)

module.vserver.azurerm_virtual_machine.vm (chef): WARNING: Failed to cleanup user key on new node: error executing "sudo rm -f /etc/chef/hdiadmin.pem": Process exited with status 1

Error: Error applying plan:

1 error(s) occurred:

• module.vserver.azurerm_virtual_machine.vm: error executing "sudo curl -LO https://omnitruck.chef.io/install.sh": Process exited with status 1

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

These commands work fine logging in with SSH to console.

Terraform Version

...

Terraform Configuration Files

...

Debug Output

Crash Output

Expected Behavior

Actual Behavior

Steps to Reproduce

Additional Context

References

[hashibot]

Hello! 🤖

This issue relates to an older version of Terraform that is no longer in active development, and because the area of Terraform it relates to has changed significantly since the issue was opened we suspect that the issue is either fixed or that the circumstances around it have changed enough that we'd need an updated issue report in order to reproduce and address it.

If you're still seeing this or a similar issue in the latest version of Terraform, please do feel free to open a new bug report! Please be sure to include all of the information requested in the template, even if it might seem redundant with the information already shared in this issue, because the internal details relating to this problem are likely to be different in the current version of Terraform.

Thanks!

[i255d]

Did you ignore the first sentence of my report? What version was it that was not working?

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.