Terraform provider release v0.37.0
Enables the secure boot parameter for the VM resource
Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
@joearnon Can you post logs of both backup instances (of the same job) that ran, see if they are different and in which way?
You can also try to reconfigure the back up job to only a single tag parameter to see if that is the issue.
Hi Pechkin000,
Try this :
npm install url-loader
yarn install v1.22.11
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info fsevents@2.3.2: The platform "linux" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.13: The platform "linux" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
[5/5] Building fresh packages...
Done in 22.66s.
Just a quick FYI, XOA means "Xen Orchestra virtual Appliance" and it's only available via https://xen-orchestra.com or auto deploy. That's the only one with pro support
Okay so it's indeed a certificate issue on your side. Double check your certs. Sometimes, you need to have a cert file with the intermediate authority.
@jmccoy555 I updated both the XO deployments to current code just now. Both were the same BTW before.
one still asks for the SR on every migration. One does not.
[info] Updating xen-orchestra from '4bed8eb86' to '175be4482'
I would REALLY like to figure this out. Annoying.
Thanks
Tim
@olivierlambert Ok cool, iSCSI is on its own Network on a Direct connection with Multipathing. In the past i have had problems with VMs going in Read Only Mode.
Thanks for your reply.
That's the issue. Why they don't have it is the problem/mystery.
Try to check if new replicated VMs got it. If not, I would check if you are correctly up to date.