FCOS VM fails to boot on Nutanix without an Ignition config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Bug
FCOS/RHCOS VM fails to boot on Nutanix without an Ignition config. So the VM execution doesn't go past the fetch-offline stage
Operating System Version
FCOS: 36.20220505.3.2
Ignition Version
v2.14.0
Environment
What hardware/cloud provider/hypervisor is being used to run Ignition?
Nutanix AHV
Expected Behavior
FCOS VM should boot on Nutanix without an Ignition config
Actual Behavior
VM doesn't boot up properly without an Ignition
Reproduction Steps
Use this guide for launching a VM in Nutanix AHV but don't provide an Ignition config.
Other Information
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 Fedora CoreOS Nutanix provisioning guide and the attached boot logs, then reproduce a Nutanix AHV launch without an Ignition config. Investigate why execution stops at the fetch-offline stage; done means the FCOS/RHCOS VM boots successfully without an Ignition config.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100