-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Azure: Problems with disk_additional_size on images containg already additional disks #7042
Comments
Based on the error message it looks like Packer is allowing a configuration that is not supported by Azure. @loibpet, is this your belief too, or do you think it should work and Packer is not sending the correct configuration to Azure? |
Being in the Azure portal (https://portal.azure.com/):
Therefore, my expectation is that packer is able to add as many new disks as needed in step 2. This is working fine if done manually through the Azure portal (I haven't tried so far through the command line). |
I'm running into what I think is the same thing. The base image I'm using has a data disk attached, and I need to create a VHD based image because that is what azure requires to sell VMs on the marketplace. Anyway, if I don't specify
and if I DO specify
It feels to me that one or the other should work. Also, FWIW it seems I can create a managed image based on the same base image, without issue. So it's just a VHD related error. |
This issue has been automatically migrated to hashicorp/packer-plugin-azure#18 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-azure#18. |
packer -v: 1.3.2
We are using for our images a "chained" process for on-premis and for all cloud providers, i.e. we create one basis containing all required hardening, company specific setup and cloud specific configuration. Then we use this basis in another step and create the intended image flavor. In step one, we create one additional disk to separate the /var/log tree to a separate disk (company way of doing things which cannot be changed). For certain use cases, we need to use one more data disk in the image (e.g. for local data storage).
Our templates look like this:
Step 1:
This works fine and the image is created as needed.
Step 2 - Version 1:
This one fails with:
==> azure-arm: ERROR: -> BadRequest
==> azure-arm: ERROR: -> InvalidParameter : Cannot specify user image overrides for a disk already defined in the specified image reference.
Step 2 - Version 2:
Adding the size of the user disk of step 1 fails as well:
==> azure-arm: ERROR: -> BadRequest
==> azure-arm: ERROR: -> InvalidParameter : Cannot specify user image overrides for a disk already defined in the specified image reference.
The text was updated successfully, but these errors were encountered: