Where to find logs and diagnostics information for Tinkerbell workflow?
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What happened**:
Tinkerbell workflow failed in the EKSA provisioning process.
**What you expected to happen**:
The workflow succeeded.
**How to reproduce it (as minimally and precisely as possible)**:
Create an EKSA cluster with an Ubuntu image, instead of the default Bottlerocket one.
**Anything else we need to know?**:
Logs:
```
Environment:
DEST_DISK: /dev/sda2
DEST_PATH: /etc/netplan/config.yaml
DIRMODE: 0755
FS_TYPE: ext4
GID: 0
MODE: 0644
STATIC_NETPLAN: true
UID: 0
Image: public.ecr.aws/eks-anywhere/tinkerbell/hub/writefile:6c0f0d437bde2c836d90b000312c8b25fa1b65e1-eks-a-41
Name: write-netplan
Pid: host
Seconds: 3
Started At: 2023-07-18T22:03:30Z
Status: STATE_FAILED
Timeout: 90
```
**Environment**:
- EKS Anywhere Release: 0.16.0
- EKS Distro Release: N/A
May I know how to locate the logs and debug the issue?
Contributor guide
Research direction
Start with the failed Tinkerbell workflow details in the issue, especially the write-netplan step, and review how EKS Anywhere provisioning exposes diagnostics for Ubuntu images. Confirm where the workflow logs can be retrieved and what information is needed to diagnose the failure; done means the log location and debugging path are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, ubuntu
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100