[JIRA] (JENKINS-36430) S3 plugin - Unable to load AWS credentials from any provider in the chain

[anand.krishnan@telegraph.co.uk (JIRA)]

Anand Krishnan created an issue

Jenkins / JENKINS-36430 S3 plugin - Unable to load AWS credentials from any provider in the chain Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Jul/05 9:09 AM Environment: jenkins 2.11 - docker , amazon lunix 64bit, java 8 Labels: plugin 2.11 jenkins Priority: Major Reporter: Anand Krishnan Trying to upload the ACCESS_KETY and SECRET KEY to the Configure System area for the s33 plugin get the following in the logs and the details do not get written to the config file : java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:553) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: com.amazonaws.AmazonClientException: Unable to load AWS credentials from any provider in the chain at com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:131) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3653) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3612) at com.amazonaws.services.s3.AmazonS3Client.listBuckets(AmazonS3Client.java:743) at com.amazonaws.services.s3.AmazonS3Client.listBuckets(AmazonS3Client.java:749) at hudson.plugins.s3.S3BucketPublisher$DescriptorImpl.doLoginCheck(S3BucketPublisher.java:374) ... 68 mo Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[anand.krishnan@telegraph.co.uk (JIRA)]

Anand Krishnan updated an issue

Jenkins / JENKINS-36430 S3 plugin - Unable to load AWS credentials from any provider in the chain

Change By: Anand Krishnan Trying  to upload the   ACCESS_KETY   ACCESS_KEY and SECRET KEY  to the Configure System area for the s33 s3 plugin , get the following in the logs and the details do not get written to the config file :

[mr.akbashev@gmail.com (JIRA)]

Alexander A updated an issue

Jenkins / JENKINS-36430 S3 plugin - Unable to load AWS credentials from any provider in the chain

Plugin version? aws-sdk version? Change By: Alexander A Trying  to upload the  ACCESS_KEY and SECRET KEY  to the Configure System area for the s3 plugin,  get the following in the logs and the details do not get written to the config file : {code}

{code}

Add Comment

[anand.krishnan@telegraph.co.uk (JIRA)]

Anand Krishnan updated an issue

Jenkins / JENKINS-36430 S3 plugin - Unable to load AWS credentials from any provider in the chain

Change By: Anand Krishnan Environment: jenkins 2.11 - docker , amazon lunix 64bit, java 8      , s3 plugin version - 0.10.6, aws-java-sdk (version:1.10.50)

Add Comment

[anand.krishnan@telegraph.co.uk (JIRA)]

Anand Krishnan commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

s3 plugin version - 0.10.6, aws-java-sdk (version:1.10.50) Add Comment

[ajit.joglekar@gmail.com (JIRA)]

Ajit Joglekar commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

On the same jenkins instance as Anand has mentioned above, I get following exception while trying to save the S3 bucket access keys. It seems the keys are not written to the disk and when a login check is attempted it fails with the following exception: (actual host name replaced with xxxx) WARNING: Error while serving http://<xxxxxxxxxxxxxxxxxxxxxxxxx>/publisher/S3BucketPublisher/loginCheck

... 68 more The hudson.plugins.s3.S3BucketPublisher.xml file is writable by jenkins user and there is no other exception / log message indicating that the file write has failed -Ajit

Add Comment

[mr.akbashev@gmail.com (JIRA)]

Alexander A commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

It looks like you have issue with read-write access to .aws/ on local or remote node.

Add Comment

[anand.krishnan@telegraph.co.uk (JIRA)]

Anand Krishnan commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

Hi , I am not sure what you mean I am running the docker instance as: docker run -d -u 1000 -p 8080:8080 -p 50000:50000 -v /var/lib/jenkins:/var/jenkins_home jenkinsci/jenkins:2.11 do you mean the .aws in jenkins_home ?

Add Comment

[chetan@pixelcop.net (JIRA)]

Chetan Sarva commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

I ran into this issue as well. It appears that if you initially tick the "IAM Role" checkbox and save your config, you cannot undo that setting (verified via network panel, always sent as iam_role=true). I fixed it by deleting the S3 profile and recreating it without ticking that box at all. The checkbox label should probably also be renamed to "Use Instance IAM Role"

Add Comment

[arun.kaundal@gmail.com (JIRA)]

Arun Kumar commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

Yes Chetan Sarva . You are right. I faced similar problem. I also fixed it by deleting the S3 profile and recreating it without ticking that box at all.

Add Comment

[brentcourtois@gmail.com (JIRA)]

Brent Courtois commented on JENKINS-36430

Re: S3 plugin - Unable to load AWS credentials from any provider in the chain

I ran into this issue as well, when checking the Use IAM Role checkbox. Other people circumvented the issue by not using the IAM role but I need to. s3 plugin version - 0.10.7, Amazon Web Services SDK - 1.10.50

Add Comment