Din Mušić comments

Results 113 comments of


                                            Din Mušić

Bug: terraform-provider-lxd provider fails to create the instance in the project not equal to "default" if image fingerprint assigned to `image` attribute instead of `image name

Thanks, I was able to reproduce the issue and will look into fixing it. My assumption is that we are not using a correct image server, which causes the image...

Bug: terraform-provider-lxd provider fails to create the instance in the project not equal to "default" if image fingerprint assigned to `image` attribute instead of `image name

> The first approach where `project` is set within a `provider "lxd"` block does not work because there is no such attribute. However, this seems like a validation issue that...

unable to run `kubitect apply --config ./kubitect.yaml --action upgrade`

Thanks for reporting this issue, will look into this and report back. It seems that allowed events for a specific actions need to be tweaked a bit.

unable to run `kubitect apply --config ./kubitect.yaml --action upgrade`

The `kubernetes.manager` field should be automatically detected. Can you try adding the following into your configuration? ```yaml kubernetes: manager: kubespray ``` Regarding the LB priority, can you share the LB...

Fix image not being transfered from the host when security.devlxd.images is enabled

Nice observation. Yes, I've tested this and when the instance is in non-default project, it always requests images from `default` project.

Ceph RBD driver might not wait for volume discovery

For Pure and PowerFlex we obtain a lock when mapping/unmapping a volume. Could it be that we do not do that for Ceph? Maybe a per-volume lock could be already...

vm import fails with no message if the size of the vm is bigger

The issue here is that when the volume is too small to accommodate the image, the error is not reported back to the client. However, this has been addressed as...

vm import fails with no message if the size of the vm is bigger

I will double check, but should be the same issue.

vm import fails with no message if the size of the vm is bigger

Hmm, can the older `lxd-migrate` reach the conversion API? I think the issue should be purely in migration API, but I may be missing something.

Rename lxd-migrate to lxd-convert

I like the change, but would suggest `lxd-import`. In all cases the instance is imported into LXD. However, conversion happens only in certain scenarios. For example, there is no conversion...