Ignition should be able to enable systemd aliases
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Issue by @arithx
Issue Report
Bug
Expected Behavior
When you enable a systemd alias the service should correctly be enabled on the resulting system.
Actual Behavior
Ignition writes a systemd-preset which explicitly does not work with aliases.
Other Information
I ran into this when re-writing the kola nfs tests trying to enable the nfsd.service resulted in nothing happening on the nfs host. Changing the unit being enabled to nfs-server.service fixed the issue.
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 how Ignition writes the systemd preset and review the kola NFS tests mentioned in the report. Reproduce enabling nfsd.service versus nfs-server.service, then verify that enabling a systemd alias results in the service being enabled on the resulting system.
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
- 45/100