Impossible to use unbundled plugins #12715
Comments
|
@greg-hellings thanks for the detailed issued. This sounds like an unexpected bug for sure. Let me take a look at the provided info to see what I can figure out. |
|
Hi @greg-hellings thanks again for your detailed issue. It was helpful in tracking down what is happening. Now I just need to understand why. You are still seeing the bundled plugins warning referenced below because the build template is missing an entry for the virtualbox plugin. Oddly enough the plugin is not included in the outputted warning so you would not have any indication that it is the plugin causing the error. If you add the following required_plugin you will get rid of the bundle plugins warning entirely virtualbox = {
source = "github.com/hashicorp/virtualbox"
version = "~> 1"
}Regarding the unsupported attribute error for architecture. That error is misleading. The attribute is indeed supported the issue is that the variable If you change the name of the variable you will find things to work as expected. Please let me know if these two changes fix your issue. As for why virtualbox is not displayed within the bundled plugins warning. I am looking into that still. |
Okay so this is a bug in Packer. Virtualbox should be listed as a known bundled plugin but it is not. This is why it is not reported in the bundled plugin warning. |
It was found in #12715 that the bundled version of the Virtualbox plugin was not included in the bundled plugin warning. This miss lead to a user consistently receiving warning even when addressing the reported warning.
It was found in #12715 that the bundled version of the Virtualbox plugin was not included in the bundled plugin warning. This miss lead to a user consistently receiving warning even when addressing the reported warning.
|
This was exactly the issue, thanks for the quick turnaround! |
|
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. |
Community Note
Overview of the Issue
Since the arrival of the bundled plugins warnings in 1.9, I have included a required_plugins block in my template files. Before beginning work on a VM I run
packer init sources/from my project directory. Regardless of this, executing a build still gives me warnings that the bundled plugins will be used. At first this wasn't an issue, but I have since moved to using a newer feature in the Vagrant plugin that is not in step with the bundled version (architecture support) and now I'm getting an error when attempting to run because thearchitectureargument is not supported by the bundled Vagrant plugin.Reproduction Steps
packer init sourcespacker build -only=qemu.amd64 -var-file=./distros/ubuntu/20.04/amd64.pkrvars.hcl sources(as just one example, although the error works on building any VM)Packer version
Simplified Packer Template
https://github.com/greg-hellings/vms/tree/main/sources
Operating system and Environment details
NixOS
x86_64 system
Log Fragments and crash.log files
When I run with PACKER_LOG="1" set in my environment, it does show that all of the expected plugins are found. However, the validation error seems to be occurring before the plugins are all initialized based on the interleaving of outputs. Perhaps there is a race condition?
The text was updated successfully, but these errors were encountered: