Skip to content

aws: get region after getting config#828

Merged
ajeddeloh merged 2 commits intocoreos:masterfrom
ajeddeloh:fix-aws
Jul 19, 2019
Merged

aws: get region after getting config#828
ajeddeloh merged 2 commits intocoreos:masterfrom
ajeddeloh:fix-aws

Conversation

@ajeddeloh
Copy link
Copy Markdown
Contributor

@ajeddeloh ajeddeloh commented Jul 16, 2019

Should fix #826

should be backported to spec2x once merged

Andrew Jeddeloh added 2 commits July 16, 2019 14:11
Allow each provider's FetchConfig function to mutate the provider it
uses. This will allow the aws platform to set the region after it has
fetched the config.
We try to set the region as soon as Ignition starts, but sometimes the
metadata server isn't accessible yet. Set the region after we've fetched
the config since the server must be up by then.
Copy link
Copy Markdown
Contributor

@arithx arithx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming it passes kola tests.

@ajeddeloh
Copy link
Copy Markdown
Contributor Author

Tested with kola, confirmed it can still fetch the config. Given that I can't repro the original bug's environment to trigger the bug, that is still untested, but I'm fairly confident this should fix it.

@ajeddeloh ajeddeloh merged commit befbc86 into coreos:master Jul 19, 2019
@ajeddeloh ajeddeloh mentioned this pull request Jul 19, 2019
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

Successfully merging this pull request may close these issues.

S3 region invalid if ec2-metadata fails on first attempt

4 participants