tinkerbell / tinkerbell/actions
kexec mount issue
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 368K 0 rom
vda 252:0 0 10G 0 disk
├─vda1 252:1 0 1M 0 part
├─vda2 252:2 0 200M 0 part /boot/efi
├─vda3 252:3 0 1G 0 part /boot
└─vda4 252:4 0 8.8G 0 part /
- name: "kexec into os"
image: ghcr.io/jacobweinstock/waitdaemon:latest
timeout: 180
pid: host
environment:
BLOCK_DEVICE: /dev/vda3
FS_TYPE: xfs
IMAGE: quay.io/tinkerbell/actions/kexec:latest
WAIT_SECONDS: 10
volumes:
- /var/run/docker.sock:/var/run/docker.sock
{
"time": "2025-04-28T05:03:44.893023425Z",
"level": "0",
"caller": "smee/internal/syslog/receiver.go:160",
"msg": "msg",
"service": "smee",
"msg": {
"app-name": "555e0af6f5f2",
"facility": "daemon",
"host": "192.168.254.13",
"msg": "time=\"2025-04-28T05:03:44Z\" level=info msg=\"Mounted [/dev/vda3] -> [/mountAction]\"\n",
"procid": "1542",
"severity": "ERR"
}
}
i cant mount /dev/vda3 with kexec
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the shown workflow with BLOCK_DEVICE=/dev/vda3 and FS_TYPE=xfs, then inspect the kexec action's mount behavior and the surrounding logs. The issue is resolved when the target partition is mounted as expected and the kexec workflow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, linux
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100