Yongxiang Gao

@jacobweinstock thanks for your explanation. Do you plan to make the change so we can get consistent experience with HookOS and later the OS installed on the disk w.r.t /dev...

Look like it's related to MetalLB

@mitalipaygude I just try to use 1 more machine (1 existing host + 2 idle hosts), same issue shows: ``` 2024-04-14T08:59:52.814Z V6 Executing command {"cmd": "/usr/bin/docker exec -i eksa_1713084293614893292 kubectl...

@ndeksa sorry, I should have used "spare" instead of "idle".

And I'm able to confirm this(new partition is not created) with following command: `printf "n\np\n3\n\n+10G\np" | fdisk /dev/sda >& /mnt2/results.txt0` The content of results.txt0 is: ``` Found valid GPT with...

The worker VM node has following condition: ``` "conditions": [ { "lastTransitionTime": "2023-12-13T06:44:18Z", "message": "Node failed to report startup in 10m0s", "reason": "NodeStartupTimeout", "severity": "Warning", "status": "False", "type": "Ready" },...

The NODENAME of worker VM "mgmt20-md-0-zzjt8-n2289" is missing in following command: ``` $ kubectl get machines --kubeconfig mgmt20/generated/mgmt20.kind.kubeconfig -n eksa-system NAME CLUSTER NODENAME PROVIDERID PHASE AGE VERSION mgmt20-4ftj6 mgmt20 mgmt20-4ftj6...

It's something specific to ubuntu 22.04 I don't have such issue with ubuntu 20.04

@jacobweinstock thanks. According to the output of command "efibootmgr", current boot entry is 0000, whose DISK is "/dev/nvme0n1" ``` # efibootmgr -v BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0002,0003,0004,0005,0006,0007,0008,0009,0001 Boot0000*...