Ignition fails on duplicate user UIDs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Bug
Ignition validation does not consider duplicate user UIDs causing a failure to boot.
Operating System Version
Fedora 32
Ignition Version
v2.3.0
Environment
What hardware/cloud provider/hypervisor is being used to run Ignition?
VMware
Expected Behavior
Validation should pickup duplicate UIDs that will cause bootstrap to fail.
Actual Behavior
Core OS does not boot and drops into an emergency console.
Reproduction Steps
Create a fcc file with users that have a duplicate UID:
- name: user1
home_dir: /home/user1
groups:
- wheel
- sudo
- docker
shell: /bin/bash
uid: 9002
- name: user2
home_dir: /home/user2
groups:
- wheel
- sudo
- docker
shell: /bin/bash
uid: 9002
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 by tracing Ignition's validation handling for the user definitions shown in the reproduction steps. Reproduce the duplicate UID configuration on Fedora 32 under VMware, then verify that validation reports the duplicate before boot rather than allowing the system to reach an emergency console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100