Failing ec2 boots on Ignition failures
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
In CL, one technique to fail the health check in ec2 when the boot failed was to do:
cat > ${UNIT_DIR}/systemd-networkd.service.d/10-conflict-emergency.conf <<EOF
[Unit]
Conflicts=emergency.target
Conflicts=emergency.service
Conflicts=dracut-emergency.service
EOF
so that I presume the AWS platform wouldn't be able to even contact the node.
Think about how we'll approach this once https://github.com/coreos/fedora-coreos-tracker/issues/24 is settled. Though a distro-independent method would be nice if possible.
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 reviewing Fedora CoreOS tracker issue 24 and the proposed systemd-networkd.service.d/10-conflict-emergency.conf drop-in. Then inspect how EC2 health checks currently observe Ignition boot failures. Done means agreeing on and implementing a distro-independent way for failed Ignition boots to fail the EC2 health check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100