-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No way to attach a disk to a Flatcar VM on Azure #1297
Comments
Hi @TimoKramer, can you share your Terraform config used to deploy this instance? |
|
Great thanks, can you share now your |
|
|
Did you try with the following: variant: flatcar
version: 1.0.0
storage:
disks:
- device: /dev/disk/azure/scsi1/lun10
partitions:
- label: odoo
filesystems:
- device: /dev/disk/by-partlabel/odoo
format: ext4
wipe_filesystem: true
label: odoo
... |
no, trying now |
It's failing unfortunately as well. I think I tried with |
Do you have access to the console to access the emergency target (and get some logs)? |
I activated the boot diagnostics and seeing this:
|
Here is some output from the serial console after a reboot:
|
Ah ok so it fails to fetch the config. Any chance to try with |
I am pretty sure I tried that already since I figured out that the instances are not recreated when using |
It fails and I can see in the serial console: It seems that the disk is not available during boot
EDIT: I can see it in azure portal though |
ok, so at least we have now something to debug on :D I guess the instance and the disk are created in parallel, then only the disk is attached and I think you're hitting this: hashicorp/terraform-provider-azurerm#6117 |
oh man, so I should try the |
@TimoKramer you can try with |
@TimoKramer if you get a chance to confirm that it works with |
@tormath1 I tried with |
I think this can be closed since it is an issue with terraform and when someone searches for this problem should find a closed one as well. |
Description
I tried every imaginable combination of configuration of storage/disks and storage/filesystems on a VM on Azure. It always fails to complete the creation. I don't know how to debug that and I don't know how to get a proper error message back unfortunately.
Impact
Not being able to easily mount and format a disk makes it impossible to use Flatcar right now. Maybe I can reliably script that.
Environment and steps to reproduce
a. Requested the start of a new VM with a disk attached
b. creation is looping for
b. virtual machine failing to be created
Expected behavior
I would like to have my Azure VM properly deployed with a disk attached, formatted and mounted
Additional information
Flatcar 3602.2.2
Using this for attaching the disk and tried like here without the disks part but it's the same. So I thought we have to provision the disk first like with fdisk so I added the disks part. Still no better.
The text was updated successfully, but these errors were encountered: