Skip to content
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.

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

Packet: failed deployments related to CoreOS issues on c1.small #171

Open
vielmetti opened this issue Oct 12, 2018 · 2 comments
Open

Packet: failed deployments related to CoreOS issues on c1.small #171

vielmetti opened this issue Oct 12, 2018 · 2 comments

Comments

@vielmetti
Copy link

Please see coreos/bugs#2508 for an issue we are tracking at Packet regarding elevated failure rates for provisioning c1.small instances on CoreOS Stable. The symptom is provisions time out after 25 minutes; if you dig into the problem, and examine a booting system, you'll find that the error message "bond0: link status down for interface enp1s0f0, disabling it in 200 ms" is repeated on the console.

@vielmetti
Copy link
Author

Problem update:

This issue manifests itself twofold; one in the CoreOS "installer" stage where CoreOS writes bits to disk, and one in the CoreOS runtime when the newly installed system boots or reboots.

We have repaired the problem in our "installer" part, which runs for every install; that would appear to have decreased the frequency of problems. It hasn't eliminated them yet because the runtime for CoreOS beta and stable both still exhibit this issue. CoreOS alpha should be set (it doesn't use the same kernel as beta and stable).

The issue is not specific to c1.small so switching to a different machine type or location will not change the behavior.

@vielmetti
Copy link
Author

Based on #415 being resolved, I think this and #175 can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant