search

equinix-labs / terraform-equinix-metal-eks-anywhere

EKS Anywhere on Equinix Metal (Baremetal)
https://deploy.equinix.com/labs/terraform-equinix-metal-eks-anywhere/
Apache License 2.0
9 stars 5 forks source link

Use static interface names #63

Closed cprivitere closed 1 year ago

cprivitere commented 1 year ago

related to https://github.com/equinix-labs/terraform-equinix-metal-eks-anywhere/issues/33#issuecomment-1258699194

displague commented 1 year ago

noting that the cluster did not come up for me on my first try with these changes. I haven't retried yet.

ctreatma commented 1 year ago

I confirmed that this change works for c2.medium.x86, but consistently fails for m3.small.x86 (this is in SV, so it's possible I'd find more variance in the outcome by testing other regions, instance types, etc.).

For m3.small.x86, it looks like the Tinkerbell provisioning process for both the control plane and data plane nodes gets stuck around the same time, but at different parts of the process.

This is the error from the control plane serial output:

[  307.393287] sundog[3039]: Setting generator 'netdog generate-hostname' failed with exit code 1 - stderr: Failed to read current IP data in '/var/lib/netdog/current_ip': No such file or directory (os error 2)
[FAILED] Failed to start User-specified setting generators.
See 'systemctl status sundog.service' for details.
[DEPEND] Dependency failed for Bottlerocket initial configuration complete.
[DEPEND] Dependency failed for Isolates configured.target.
[DEPEND] Dependency failed for Applies settings to create config files.
[DEPEND] Dependency failed for Sets the hostname.

And this is the end of the serial output from the data plane node:

time="2022-12-05T22:13:59.715739385Z" level=info msg="starting signal loop[   24.281570] IPVS: ftp: loaded support on port[0] = 21
" namespace=services.linuxkit path=/run/containerd/io.containerd.runtime.v2.task/services.linuxkit/rngd pid=1366
[   24.305007] random: crng init done
[   24.386503] Initializing XFRM netlink socket
[  497.322779] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
cprivitere commented 1 year ago

This seems to have all gotten committed via some other route. So going to close this.