hashicorp / hashicorp/packer-plugin-azure
[Azure] WinRM timeout with Windows 2016-Datacenter Marketplace Image
- Dominant language
- Go
- Stars
- 63
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
_This issue was originally opened by @Dilergore as hashicorp/packer#8658. It was migrated here as a result of the [Packer plugin split](https://github.com/hashicorp/packer/issues/8610#issuecomment-770034737). The original body of the issue is below._
Please refer the end of this thread to see other users complaining that this is not working.
https://github.com/MicrosoftDocs/azure-docs/issues/31188
### Issue:
Started: December, 2019.
Packer cannot connect with WinRM to machines provisioned from Windows 2016 (2016-Datacenter) Marketplace image in Azure.
### Further details:
WinRM timeout increase is not working. It seems the last image working is version: "14393.3326.1911120150" (Released 12th of Nov). It stopped working with "14393.3384.1912042333" (Released 10th of Dec).
This issue is only impacting 2016-Datacenter. 2019 is working properly.
### To get image Details for a Region:
az vm image list --location northeurope --offer WindowsServer --publisher MicrosoftWindowsServer --sku 2016-Datacenter --all
### URL to the Last Working Image:
https://support.microsoft.com/en-us/help/4525236/windows-10-update-kb4525236
### URL to the Image where something went wrong:
https://support.microsoft.com/en-us/help/4530689/windows-10-update-kb4530689
### Notes:
This is currently applying to North EU. I had no time to investigate in other regions but I believe the same images getting distributed to every region.
**I am opening a Microsoft case and planning to update the thread with the progress.**
Contributor guide
Research direction
Start by running the provided az vm image list command for the affected region and comparing the last working and failing Windows 2016-Datacenter image versions. Review the linked Azure documentation issue and the comment thread for evidence of the WinRM failure; done would require identifying a concrete plugin-side change or confirming that the problem is external to Packer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100