Skip to content
This repository has been archived by the owner. It is now read-only.

Container Linux should fail EC2 instance status checks when provisioning fails #1890

Closed
crawford opened this issue Mar 30, 2017 · 0 comments
Closed

Comments

@crawford
Copy link
Member

@crawford crawford commented Mar 30, 2017

Issue Report

Feature Request

Environment

AWS

Desired Feature

When Ignition fails on AWS, we should tear down the network so it starts failing instance status checks. This will make it easier to recognize that there is something wrong.

csssuf added a commit to csssuf/bootengine that referenced this issue Jun 22, 2017
If ignition fails when running on EC2, systemd-networkd should be
stopped so that the instance's status checks fail and indicate
ignition's failure.

Fixes coreos/bugs#1890.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.