race condition in kickstart installation not detecting target disk
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
there seems to be a race condition, where sometimes (often in my case) the photon-os-installer
fails to detect the configured target disk (eg. /dev/sda).
issuing
umount /mnt/media
exit
will restart the installation without problems
Reproduction steps
package a kickstarter with
"disk": "/dev/sda",
"bootmode": "dualboot",
"partition_type": "gpt",
"partitions": [
{"mountpoint": "/", "size": 0, "filesystem": "ext4"},
{"mountpoint": "/boot", "size": 1024, "filesystem": "ext4"},
{"mountpoint": "/root", "size": 1024, "filesystem": "ext4"},
{"mountpoint": "/data", "size": 1024, "filesystem": "ext4"},
{"size": 1024, "filesystem": "swap"}
],
Expected behavior
the installer should check and wait (timeout) for the availability of the configured installation target disk
Additional context
No response
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
Start with the photon-os-installer kickstart path that detects the configured target disk, using the supplied /dev/sda configuration to reproduce the race. Done means the installer waits with a timeout for the target disk to become available instead of failing and requiring the installation restart workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100