For me, The problem has been solved by giving Contributor access to the service principal.
On Tuesday, June 26, 2018 at 7:33:51 AM UTC+5:30, Nate B wrote: > > // , It looks like the Packer API has moved on a bit since the last time > there were any serious updates to the Terraform module for Azure Vault: > > > https://github.com/hashicorp/terraform-azurerm-vault/blame/master/examples/vault-consul-image/vault-consul.json > > I just started using Packer today, and ran into the following error: > > $ packer build vault-consul.json > azure-arm output will be in this color. > > > ==> azure-arm: Running builder ... > azure-arm: Creating Azure Resource Manager (ARM) client ... > ==> azure-arm: ERROR: -> ResourceNotFound : The Resource > 'Microsoft.Compute/images/vault-consul-ubuntu-2018-06-26-012357' under > resource group 'packerresourcegroup' was not found. > ==> azure-arm: > ==> azure-arm: resources.GroupsClient#CheckExistence: Failure responding > to request: StatusCode=403 -- Original Error: autorest/azure: error > response cannot be parsed: "" error: EOF > Build 'azure-arm' errored: resources.GroupsClient#CheckExistence: Failure > responding to request: StatusCode=403 -- Original Error: autorest/azure: > error response cannot be parsed: "" error: EOF > > > ==> Some builds didn't complete successfully and had errors: > --> azure-arm: resources.GroupsClient#CheckExistence: Failure responding > to request: StatusCode=403 -- Original Error: autorest/azure: error > response cannot be parsed: "" error: EOF > > > ==> Builds finished but no artifacts were created. > l-sfo01ehtdd-m:vault-consul-image nbasane$ packer build vault-consul.json > azure-arm output will be in this color. > > > ==> azure-arm: Running builder ... > azure-arm: Creating Azure Resource Manager (ARM) client ... > ==> azure-arm: ERROR: -> ResourceNotFound : The Resource 'Microsoft. > Compute/images/vault-consul-ubuntu-2018-06-26-014346' under resource > group 'packerresourcegroup' was not found. > ==> azure-arm: > ==> azure-arm: resources.GroupsClient#CheckExistence: Failure responding > to request: StatusCode=403 -- Original Error: autorest/azure: error > response cannot be parsed: "" error: EOF > Build 'azure-arm' errored: resources.GroupsClient#CheckExistence: Failure > responding to request: StatusCode=403 -- Original Error: autorest/azure: > error response cannot be parsed: "" error: EOF > > > ==> Some builds didn't complete successfully and had errors: > --> azure-arm: resources.GroupsClient#CheckExistence: Failure responding > to request: StatusCode=403 -- Original Error: autorest/azure: error > response cannot be parsed: "" error: EOF > > > ==> Builds finished but no artifacts were created. > > > I'm trying to get the examples working from here: > > > https://github.com/hashicorp/terraform-azurerm-vault/tree/master/examples/vault-consul-image > > But I'm wondering how I would tell whether I've run into some kind of a > bug in the module, in my Azure configuration, or in Packer's Azure Builder > itself. > > The service provider which I'm using for this has owner permissions on the > resource group with the super creative name *packerresourcegroup*. > Which means it's unlikely that it's a permissions issue, unless the > underlying Builder is generating an incorrect Resource Name to send to the > ARM endpoint. > > Anyway, I wonder if anyone else has run into similar issues with Packer's > Azure Builder, and if you have any ideas I can use to investigate further? > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/4e5c991a-eeb1-4527-9919-133a61f34c12%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
