Open Swalloow opened 1 year ago
Hi @Swalloow. It looks like you're missing the partition number in the DESK_DISK
parameter on your v0.17.0 example, is that right?
Yes but in v0.11.4 to v0.14.6 it ran with the proper partition number without the template.
In v0.15.0 to v0.17.0, do I need to use TinkerbellTemplateConfig
to configure the partition number?
Understood. xvd
isn't supported in upstream. I've made a patch (https://github.com/tinkerbell/tink/pull/786) to the upstream project and we will consider patching in EKS-A.
@d8660091 FYI.
Dependent on the upstream release, this may be fixed when we upgrade the stack in aws/eks-anywhere-internal#1952
Someone need to validate it on latest EKS-A BM release ( @ndeksa , @sp1999 )
What happened: EKS Anywhere's write-netplan action failed because
DEST_DISK
value is incorrect.What you expected to happen: EKS Anywhere's write-netplan action should also succeed when using Ubuntu.
How to reproduce it (as minimally and precisely as possible): Follow EKS Anywhere bare metal cluster creation instruction with an Ubuntu 20.04 image.
Anything else we need to know?: It succeeds in EKS Anywhere v0.11.4 with the same settings. The states on success and failure are as follows:
Environment:
public.ecr.aws/eks-anywhere/tinkerbell/hub/writefile:404dab73a8a7f33e973c6e71782f07e82b125da9-eks-a-45