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

Update aws java sdk to support ecs task roles #25552

Conversation

matarrese
Copy link
Contributor

@matarrese matarrese commented Jul 5, 2017

Hi,
there are some failing tests, so it should not be considered as a ready to be reviewed pull request? Just to know if it's something related what you were talking about here: #23039

@karmi
Copy link
Contributor

karmi commented Jul 5, 2017

Hi @matarrese, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@matarrese
Copy link
Contributor Author

Thank you @karmi for your prompt reply.
I have added the email to my profile

@tedder
Copy link
Contributor

tedder commented Aug 4, 2017

Any updates here?

@matarrese
Copy link
Contributor Author

Solved by #26479

@matarrese matarrese closed this Sep 12, 2017
@dadoonet
Copy link
Member

OMG! I'm very sorry I did not see your PR before I merged the other one. :shame:

@mohit
Copy link
Contributor

mohit commented Sep 12, 2017

actually @matarrese #26479 does not update the SDK for repository-s3 which your PR does, so I still think this PR would be worth getting to master.

@dadoonet
Copy link
Member

True. @matarrese wanna add some missing bits to your PR?

@dadoonet dadoonet reopened this Sep 12, 2017
@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@matarrese
Copy link
Contributor Author

Hi @dadoonet, I missed the new updates on this.
Does this pull request need more work? Or is it ready to be reviewed?

Copy link
Member

@dadoonet dadoonet left a comment

Choose a reason for hiding this comment

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

Left a comment.
Please run also gradle check. It will most likely fail as the SHA1 changed for the new jars. Could you fix it as well?

@@ -23,7 +23,7 @@ esplugin {
}

versions << [
'aws': '1.10.69'
'aws': '1.11.16'
Copy link
Member

Choose a reason for hiding this comment

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

Could you update it to 1.11.187 to align with what we have in #26479?

@dadoonet
Copy link
Member

@matarrese Did you run gradle check locally?

@matarrese
Copy link
Contributor Author

Hi @dadoonet , now seems fine to me locally.
Let me know if we need further changes!

@dadoonet
Copy link
Member

dadoonet commented Oct 2, 2017

jenkins test it please

@dadoonet
Copy link
Member

dadoonet commented Oct 2, 2017

I'm surprised gradle check is passing well without changing the SHA1 files. Let see what Jenkins says.

@dadoonet
Copy link
Member

dadoonet commented Oct 2, 2017

As I told you it failed with:

16:35:47 Checking sha for aws-java-sdk-s3-1.11.187.jar
16:35:47 :plugins:repository-s3:dependencyLicenses FAILED
16:35:47 :plugins:repository-s3:dependencyLicenses (Thread[main,5,main]) completed. Took 0.004 secs.
16:35:47 
16:35:47 FAILURE: Build failed with an exception.
16:35:47 
16:35:47 * What went wrong:
16:35:47 Execution failed for task ':plugins:repository-s3:dependencyLicenses'.
16:35:47 > Missing SHA for aws-java-sdk-s3-1.11.187.jar. Run 'gradle updateSHAs' to create

Run:

gradle :plugins:repository-s3:updateSHAs
gradle :plugins:repository-s3:check

And commit the changes. Thanks!

@dadoonet
Copy link
Member

dadoonet commented Oct 3, 2017

jenkins test it please

@rjernst
Copy link
Member

rjernst commented Jan 9, 2018

@elasticmachine test this please

@matarrese
Copy link
Contributor Author

@rjernst could you please test this branch again?

@rjernst
Copy link
Member

rjernst commented Jan 15, 2018

@elasticmachine test this please

* master: (74 commits)
  Update version of TaskInfo header serialization after backport
  TEST: Tightens file-based condition in peer-recovery
  Correct backport replica rollback to 6.2 (elastic#28181)
  Backport replica rollback to 6.2 (elastic#28181)
  Rename deleteLocalTranslog to createNewTranslog
  AwaitsFix #testRecoveryAfterPrimaryPromotion
  TEST: init unassigned gcp in testAcquireIndexCommit
  Replica start peer recovery with safe commit (elastic#28181)
  Truncate tlog cli should assign global checkpoint (elastic#28192)
  Fix lock accounting in releasable lock
  Add ability to associate an ID with tasks  (elastic#27764)
  [DOCS] Removed differencies between text and code (elastic#27993)
  text fixes (elastic#28136)
  Update getting-started.asciidoc (elastic#28145)
  [Docs] Spelling fix in painless-getting-started.asciidoc (elastic#28187)
  Fixed the cat.health REST test to accept 4ms, not just 4.0ms (elastic#28186)
  Do not keep 5.x commits once having 6.x commits (elastic#28188)
  Rename core module to server (elastic#28180)
  upgraded jna from 4.4.0-1 to 4.5.1 (elastic#28183)
  [TEST] Do not call RandomizedTest.scaledRandomIntBetween from multiple threads
  ...
@rjernst
Copy link
Member

rjernst commented Jan 16, 2018

@elasticmachine test this please

@colings86 colings86 added v6.3.0 and removed v6.2.0 labels Jan 22, 2018
@rjernst
Copy link
Member

rjernst commented Jan 24, 2018

@elasticmachine test this please

@rjernst
Copy link
Member

rjernst commented Jan 28, 2018

@matarrese I think you need to remove the sha files you are adding to the licenses dir, as those were from a previous version of this PR when you had updated the sdk version.

The test failure looks unrelated. If you remove those sha files, I will trigger tests once more, and if there are still unrelated failures I will pull and test this manually.

@matarrese
Copy link
Contributor Author

Hi @rjernst , I have removed the generated sha files.

@dadoonet dadoonet removed their assignment Feb 5, 2018
@rjernst
Copy link
Member

rjernst commented Feb 9, 2018

@elasticmachine test this please

@clintongormley clintongormley added :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs and removed :Plugin Repository S3 labels Feb 14, 2018
@rjernst
Copy link
Member

rjernst commented Feb 26, 2018

@elasticmachine test this please

@rjernst
Copy link
Member

rjernst commented Dec 6, 2018

This was actually picked up in #31864 by someone unaware of this old PR. I'm going to close this as it is no longer necessary, but thank you for the contribution @matarrese!

@rjernst rjernst closed this Dec 6, 2018
@jimczi jimczi added v7.0.0-beta1 and removed v7.0.0 labels Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.