Bug 962354 - Fail to restart a Jenkins server after force-stopping it
Summary: Fail to restart a Jenkins server after force-stopping it
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-13 09:22 UTC by Zhe Wang
Modified: 2015-05-14 23:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-11 03:56:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Zhe Wang 2013-05-13 09:22:05 UTC
Description of problem:
Given a Jenkins server that has been force-stopped, it fails to restart it again.

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

How reproducible:
always

Steps to Reproduce:
1. Create a Jenkins server
rhc app create jenkins jenkins-1.4

2. Force-stop this jenkins server
rhc app force-stop jenkins

3. Check if the server is accessible

4. Restart this Jenkins server
rhc app restart jenkins

5. Check if the server becomes accessible again
  
Actual results:
In both Step 3 & 5, the Jenkins server is inaccessible via its URL.

Expected results:
The jenkins server should be restarted successfully after force-stopping it.

Additional info:

Comment 1 Dan McPherson 2013-05-13 21:21:38 UTC
https://github.com/openshift/origin-server/pull/2445

Comment 3 Zhe Wang 2013-05-14 08:33:33 UTC
Verified in devenv_3223, and the steps are identical to those in Description.


Note You need to log in before you can comment on or make changes to this bug.