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

Make ignition remote file retrieval retry on intermediate errors #2280

Closed
discordianfish opened this Issue Dec 7, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@discordianfish

discordianfish commented Dec 7, 2017

ignition supports downloading files from s3. Unfortunately s3 isn't always very reliable and every ~10 boot ignition fails because s3 returns a 5xx error. It would be great if ignition could retry in this case.

@crawford

This comment has been minimized.

Show comment
Hide comment
@crawford

crawford Dec 11, 2017

Member

Ignition already retries S3 fetches (it uses the default from the S3 golang library). In the event that the S3 fetch fails, Container Linux will reboot after five minutes and try to provision itself again.

Are you seeing different behavior?

Member

crawford commented Dec 11, 2017

Ignition already retries S3 fetches (it uses the default from the S3 golang library). In the event that the S3 fetch fails, Container Linux will reboot after five minutes and try to provision itself again.

Are you seeing different behavior?

@discordianfish

This comment has been minimized.

Show comment
Hide comment
@discordianfish

discordianfish Dec 12, 2017

It looked like it tried once and rebooted after that. Hrm.. I can look into this closer when it happens again. It happened quite frequently (maybe every ~10th boot) in us-east-1.

discordianfish commented Dec 12, 2017

It looked like it tried once and rebooted after that. Hrm.. I can look into this closer when it happens again. It happened quite frequently (maybe every ~10th boot) in us-east-1.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Jul 6, 2018

Member

Closing due to inactivity.

Member

bgilbert commented Jul 6, 2018

Closing due to inactivity.

@bgilbert bgilbert closed this Jul 6, 2018

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