Bug 962354 - Fail to restart a Jenkins server after force-stopping it
Fail to restart a Jenkins server after force-stopping it
Product: OpenShift Origin
Classification: Red Hat
Component: Containers (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Dan McPherson
libra bugs
Depends On:
  Show dependency treegraph
Reported: 2013-05-13 05:22 EDT by Zhe Wang
Modified: 2015-05-14 19:11 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-10 23:56:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Zhe Wang 2013-05-13 05:22:05 EDT
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):

How reproducible:

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 17:21:38 EDT
Comment 3 Zhe Wang 2013-05-14 04:33:33 EDT
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.