Quantcast
Jenkins › Jenkins issues

[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously

classic Classic list List threaded Threaded
♦
♦
 5 messages Options
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Michael Watt
Components: s3
Created: 17/Jul/12 5:03 PM
Description:

We use the S3 plugin in both a newer Jenkins install (v1.471, waiting for some important stuff to clear before we update it to 1.474) and a few older Hudson builds. The current Jenkins w/S3 (v0.3) works for a while, then all our builds stop uploading to S3 with an "Access Denied" error from Amazon. The builds on the older Hudson/S3 still work to the same bucket, and our credentials still work when I test with s3fs on the same machine. Error from Jenkins build console of one failure (buckets and filenames changed to xxxxx):

Archiving artifacts
Publish artifacts to S3 Bucket Using S3 profile: builds2
Publish artifacts to S3 Bucket bucket=xxxxxxx/store, file=xxxxxxx.latest.apk
ERROR: Failed to upload files
java.io.IOException: put Destination [bucketName=xxxxxxxxx, objectName=xxxxxxx/store/xxxxxxxxxxx.latest.apk]: Status Code: 403, AWS Request ID: 85F9CB0156BF7CF6, AWS Error Code: AccessDenied, AWS Error Message: Access Denied, S3 Extended Request ID: swP7ylP4SQNW3o9uP3alhBO/VZthqvuFxWiZ2Pn54mqhSHk2uEtSrIlhPXlJLPUM
at hudson.plugins.s3.S3Profile.upload(S3Profile.java:82)
at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:119)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
at hudson.model.Run.execute(Run.java:1509)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Build step 'Publish artifacts to S3 Bucket' changed build result to UNSTABLE
Project: Jenkins
Priority: Major Major
Reporter: Theral Mackey
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously

JIRA noreply@jenkins-ci.org

Restarting (full stop, start) the Jenkins service in windows fixes this problem for a while, but it comes back eventually.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14470) S3 Plugin publishing fails spontaneously

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

This appears to be related to our using multiple S3 Profiles. We have ~18 projects on the problematic Jenkins server, most using the S3 uploader. We have 3 profiles setup in the general config area for S3. 2 are identical with the second being setup when the first set appeared to fail (adding credentials seems to temporarily get it working again as well). The other set was added for a different S3 bucket on a different project. We have noticed that when most builds go "unstable" due to S3 uploads failing, this other project still works. After restarting Jenkins to get the other projects working again, this project fails. It looks like Jenkins is switching credential sets between projects.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14470) S3 Plugin switches credential profiles

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Theral Mackey (27/Jul/12 5:41 PM)
Summary: S3 Plugin  publishing fails spontaneously  switches credential profiles
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-14470) S3 Plugin switches credential profiles

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Michael Watt assigned Bug JENKINS-14470 to Unassigned

Unassigning. I'm not going to be able to pick this up in the near future.
Change By: Michael Watt (21/Sep/12 10:53 AM)
Assignee: Michael Watt
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...
Powered by Nabble Edit this page