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

[FLOC-4552] Harden EBS tag parsing #2974

Merged
merged 8 commits into from
Dec 9, 2016
Merged

Conversation

wallrj
Copy link
Contributor

@wallrj wallrj commented Dec 8, 2016

Fixes: https://clusterhq.atlassian.net/browse/FLOC-4552

Based on #2973 with some extra logging and unit tests.

Thanks to @sgnn7 for reporting this issue and providing a patch.

sgnn7 and others added 6 commits December 7, 2016 12:18
If there is a volume in EBS with a tag key of `flocker-dataset-id` but
the value is not a valid UUID, any Flocker agent connected to that
account will throw an exception during iteration and will be unusable.

The change here catches bad values and makes them process as just
another volume that's not part of the asking cluster rather than
throwing the mentioned exceptions.
@wallrj
Copy link
Contributor Author

wallrj commented Dec 8, 2016

Well that went badly.
Seems to be trying to contact th AWS API.
On my laptop, the Volume s were created without any AWS API interaction.
Perhaps there's some other way to create these resources.

@wallrj
Copy link
Contributor Author

wallrj commented Dec 9, 2016

@sgnn7 Please review the changes in the branch and leave comments and / or a LGTM.

Copy link
Contributor

@sgnn7 sgnn7 left a comment

Choose a reason for hiding this comment

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

LGTM!

@wallrj wallrj merged commit 97f30a5 into master Dec 9, 2016
@wallrj wallrj deleted the FLOC-4552-harden_ebs_tag_parsing branch December 9, 2016 01:54
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.

2 participants