New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Failing ec2 boots on Ignition failures #1050

Open

jlebon opened this issue Feb 28, 2019 · 1 comment

Member

jlebon commented Feb 28, 2019

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 coreos/fedora-coreos-tracker#24 is settled. Though a distro-independent method would be nice if possible.

The text was updated successfully, but these errors were encountered:

Contributor

darkmuggle commented Jul 27, 2020

@jlebon is this still current? If not, would you mind closing this out?

Moving this to Ignition.

darkmuggle transferred this issue from coreos/ignition-dracut

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment