Closed jbolthouse closed 1 year ago
This has already been fixed in #206, but there has not been a release since.
Until that is released, you can
stable
channelDuplicate of #204
@ddelnano Can we do a release soon?
@4censord thanks for linking the previous issue. I'm trying to get a release out today or tomorrow.
Sorry I didn't make the connnection between these. Makes sense now.
On Tue, Jul 26, 2022 at 9:01 AM Dom Del Nano @.***> wrote:
@4censord https://github.com/4censord thanks for linking the previous issue. I'm trying to get a release out today or tomorrow.
— Reply to this email directly, view it on GitHub https://github.com/terra-farm/terraform-provider-xenorchestra/issues/207#issuecomment-1195673701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACKXZAM2FYQMX5PY454KLTVWADUTANCNFSM54WJZNOQ . You are receiving this because you authored the thread.Message ID: @.*** com>
-- John Bolthouse https://www.linkedin.com/in/johnbolthouse https://www.linkedin.com/in/johnbolthouse May all our earnest efforts to accomplish anything find themselves seasoned with salt.
This will be fixed in v0.23.3 which will be released within the next hour.
Following the guidance in the docs, I attempted to pass a cloud config as a part of initializing a VM and have run aground a Go error:
I have tried various forms of the cloud config and tried the last few releases of this provider and am seeing it happening consistently. Here is my config, with privacy redactions.
I have also tried both loading the cloud config from file and inserting it as you see below. I have also tried only passing hostname as the cloud config, in case any of the parameters were causing the issue.
Terraform validates the config, and I have verified that the connection to our XO is solid.
I dug around in the code for a bit to try to find the offending line, but I can't seem to make the location/stack emit with:
export TF_LOG=TRACE && export TF_LOG_PATH=$(pwd)/err.log && terraform apply
-- Is there a way to trace back??Also -- the nmcli config is there only because I failed to notice that a network config could be passed as well, and I hadn't changed that yet. It was a desperate attempt to get everything working in one config.
Here are the errata from the log which may be pertinent: