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

Fix for BROOKLYN-314 #267

Merged
merged 1 commit into from Jul 19, 2016
Merged

Fix for BROOKLYN-314 #267

merged 1 commit into from Jul 19, 2016

Conversation

aledsage
Copy link
Contributor

Try-catch in getOptionalNode/getOptionalImage (e.g. if called by user
in rebind code, then don’t fail outright if cloud throws exception

Try-catch in getOptionalNode/getOptionalImage (e.g. if called by user
in rebind code, then don’t fail outright if cloud throws exception
@nakomis
Copy link
Contributor

nakomis commented Jul 19, 2016

Looks good, and pretty straightforward. Could you add a test for the rebind issue described in #BROOKLYN-314

@aledsage
Copy link
Contributor Author

@nakomis not particularly easily is the answer, for writing a test to recreate BROOKLYN-314! Would need to stub-out the a JcloudsLocation to simulate the failure, and to write a custom entity and an associated driver that calls machine.getOsDetails() in its constructor.

I'll have more of a look at doing that, but am going to merge this now.

@asfgit asfgit merged commit 1f1e7c7 into apache:master Jul 19, 2016
asfgit pushed a commit that referenced this pull request Jul 19, 2016
@aledsage aledsage deleted the fix/BROOKLYN-314 branch July 19, 2016 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants