Open jlebon opened 5 years ago
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.
@jlebon is this still current? If not, would you mind closing this out?
Moving this to Ignition.
In CL, one technique to fail the health check in ec2 when the boot failed was to do:
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.