Bug 815185

Summary: A lot of error message is seen in jenkins log
Product: OpenShift Online Reporter: Johnny Liu <jialiu>
Component: ImageAssignee: Ben Parees <bparees>
Status: CLOSED WORKSFORME QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.xCC: dmcphers, mfisher
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-10 15:39:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
jenkins.log none

Description Johnny Liu 2012-04-23 04:23:59 UTC 
Description of problem:
Create app with jenkins embedded, and do git push to trigger jenkins build.
Though jenkins build is finished successfully, a lot of error message is seen in jenkins log. It is so noisy for user's debug.

Attach my jenkins log for your reference.

Version-Release number of selected component (if applicable):
devenv_1735

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Johnny Liu 2012-04-23 04:24:59 UTC 
Created attachment 579409 [details]
jenkins.log
Comment 2 Bill DeCoste 2012-04-23 16:20:20 UTC 
This isn't a bug and resolves itself. I've seen this fairly often when jenkins is trying reload the configuration by hitting http://loopback:port/job/app/config.xml - jenkins returns a 500. There is an jenkins bug open to reload job configuration via their api - once this is fixed we can update jenkins and reload via the api vs via the url. I'll leave this bug open until we get to that point.
Comment 3 Ben Parees 2014-02-10 15:39:17 UTC 
I just tried this with both a php and jboss app and the only error that appears in the jenkin.log is the known UDP broadcast failure, for which we have another bug.  I'm assuming this was fixed upstream in the last 2 years, but if you are still seeing it and have more details on how to recreate, please reopen.