Bug 848715

Summary: Get error message like "create_job status:503" when enable Jenkins build on DEV.
Product: OKD Reporter: Mengjiao Gao <mgao>
Component: ContainersAssignee: Jhon Honce <jhonce>
Status: CLOSED DUPLICATE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: jhonce, szhou, yujzhang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 17:26:02 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
Error msg page when enable jenkins build. none

Description Mengjiao Gao 2012-08-16 09:29:51 UTC
Created attachment 604844 [details]
Error msg page when enable jenkins build.

Description of problem:
    After I created a application named "py", I tried to "Enable jenkins build" to it , but caughted error mistake: "Cartridge Could not add job "py-build" in jenkins server:create_job status:503 You'll need to correct this error before attemping to embed the Jenkins client again" , as the attachment show.
    If I tried again later by clicked "add jenkins" button in this error page, it will be added successful.
    This issue is probably caused by the too long time to prepare jenkins server.But the error message seems not clear to user. There should be a message to tell user what the problem is and guide user to wait a seconds to try again.

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

How reproducible:
always

Steps to Reproduce:
1.Create an application.
2.Tried to "Enable jenkins build" to it.
3.
  
Actual results:
Get error message which seems not clear to user. 

Expected results:
It should be added successful or give a more clear message to guide user waiting a minute to try again.

Additional info:

Comment 1 Clayton Coleman 2012-08-16 14:46:20 UTC
This looks like it was introduced by the changes to the Jenkins client - the message and error code needs to be the same as it was before.

Comment 2 Jhon Honce 2012-08-16 17:26:02 UTC

*** This bug has been marked as a duplicate of bug 823720 ***