terra-farm / terraform-provider-virtualbox

VirtualBox provider for Terraform
https://terra-farm.github.io/provider-virtualbox/
MIT License
323 stars 134 forks source link

Error using provided example #1

Closed ghost closed 5 years ago

ghost commented 8 years ago

Using the provided example, I get the following output using Terraform 0.6.6 and the current compiled version of terraform-provider-virtualbox

virtualbox_vm.node.0: Creating...
  cpus:                                     "" => "2"
  image:                                    "" => "~/ubuntu-15.04.tar.xz"
  memory:                                   "" => "512mib"
  name:                                     "" => "node-01"
  network_adapter.#:                        "" => "2"
  network_adapter.0.device:                 "" => "IntelPro1000MTServer"
  network_adapter.0.ipv4_address:           "" => "<computed>"
  network_adapter.0.ipv4_address_available: "" => "<computed>"
  network_adapter.0.mac_address:            "" => "<computed>"
  network_adapter.0.status:                 "" => "<computed>"
  network_adapter.0.type:                   "" => "nat"
  network_adapter.1.device:                 "" => "IntelPro1000MTServer"
  network_adapter.1.host_interface:         "" => "en0"
  network_adapter.1.ipv4_address:           "" => "<computed>"
  network_adapter.1.ipv4_address_available: "" => "<computed>"
  network_adapter.1.mac_address:            "" => "<computed>"
  network_adapter.1.status:                 "" => "<computed>"
  network_adapter.1.type:                   "" => "bridged"
  status:                                   "" => "running"
virtualbox_vm.node.1: Creating...
  cpus:                                     "" => "2"
  image:                                    "" => "~/ubuntu-15.04.tar.xz"
  memory:                                   "" => "512mib"
  name:                                     "" => "node-02"
  network_adapter.#:                        "" => "2"
  network_adapter.0.device:                 "" => "IntelPro1000MTServer"
  network_adapter.0.ipv4_address:           "" => "<computed>"
  network_adapter.0.ipv4_address_available: "" => "<computed>"
  network_adapter.0.mac_address:            "" => "<computed>"
  network_adapter.0.status:                 "" => "<computed>"
  network_adapter.0.type:                   "" => "nat"
  network_adapter.1.device:                 "" => "IntelPro1000MTServer"
  network_adapter.1.host_interface:         "" => "en0"
  network_adapter.1.ipv4_address:           "" => "<computed>"
  network_adapter.1.ipv4_address_available: "" => "<computed>"
  network_adapter.1.mac_address:            "" => "<computed>"
  network_adapter.1.status:                 "" => "<computed>"
  network_adapter.1.type:                   "" => "bridged"
  status:                                   "" => "running"
Error applying plan:

2 error(s) occurred:

* virtualbox_vm.node.0: user: Current not implemented on linux/amd64
* virtualbox_vm.node.1: user: Current not implemented on linux/amd64

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.
jzohrab commented 8 years ago

Did you use the supplied image file? https://github.com/ccll/terraform-provider-virtualbox-images/releases/tag/ubuntu-15.04

I'm not the maintainer, but a posting of the TF log would probably help him. Ref https://www.terraform.io/docs/internals/debugging.html, eg:

export TF_LOG=DEBUG
export TF_LOG_PATH=~/Documents/tflog.log
terraform apply yourplan.tfplan
jtyr commented 8 years ago

I got the same error. This is the part of the log showing the first error:

2016/04/19 22:45:11 [DEBUG] apply: virtualbox_vm.node.0: executing Apply
2016/04/19 22:45:11 [DEBUG] terraform-provider-virtualbox: pid-24620-resource_vm.go:130: [ERROR] Get current user: user: Current not implemented on linux/amd64
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalWriteState
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalApplyProvisioners
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalIf
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalWriteDiff
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalIf
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalWriteState
2016/04/19 22:45:11 [DEBUG] root: eval: *terraform.EvalApplyPost
2016/04/19 22:45:11 [ERROR] root: eval: *terraform.EvalApplyPost, err: 1 error(s) occurred:

* virtualbox_vm.node.0: user: Current not implemented on linux/amd64
2016/04/19 22:45:11 [ERROR] root: eval: *terraform.EvalSequence, err: 1 error(s) occurred:

* virtualbox_vm.node.0: user: Current not implemented on linux/amd64
2016/04/19 22:45:11 [ERROR] root: eval: *terraform.EvalOpFilter, err: 1 error(s) occurred:

* virtualbox_vm.node.0: user: Current not implemented on linux/amd64
2016/04/19 22:45:11 [ERROR] root: eval: *terraform.EvalSequence, err: 1 error(s) occurred:

* virtualbox_vm.node.0: user: Current not implemented on linux/amd64
2016/04/19 22:45:11 [TRACE] [walkApply] Exiting eval tree: virtualbox_vm.node #0
VoyTechnology commented 5 years ago

@jtyr @jzohrab I am looking over old issues to see are they still valid or can I close them. If you are using the package still, can you confirm is this still an issue? If you are not using it any more I will just close.

jzohrab commented 5 years ago

Hello, thanks. I’m not using this any more. Cheers!

On Mon, Jul 22, 2019 at 3:30 AM Wojtek Bednarzak notifications@github.com wrote:

@jtyr https://github.com/jtyr @jzohrab https://github.com/jzohrab I am looking over old issues to see are they still valid or can I close them. If you are using the package still, can you confirm is this still an issue? If you are not using it any more I will just close.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/terra-farm/terraform-provider-virtualbox/issues/1?email_source=notifications&email_token=AAMPWDNKIZ64WTCDZCHCIALQAWD5LA5CNFSM4BUB546KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PP5MQ#issuecomment-513736370, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMPWDJH3HNCEX6N5YTGH5DQAWD5LANCNFSM4BUB546A .

VoyTechnology commented 5 years ago

Closing. Feel free to reopen or create a new issue if this issue is still happening.