Bug 1130662

Summary: In Docker container agent occasionally shutdown while trying to register with server
Product: [JBoss] JBoss Operations Network Reporter: Viet Nguyen <vnguyen>
Component: AgentAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED EOL QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.3.0   
Target Milestone: ---   
Target Release: JON 4.0.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-24 14:53:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
agent.log
none
server.log none

Description Viet Nguyen 2014-08-15 20:17:08 UTC
Created attachment 927269 [details]
agent.log

Description of problem:

When inside a Fedora 20 Docker container the default agent occasionally shutdown before registration 


Version-Release number of selected component (if applicable):
JON 3.3.DR1

How reproducible:
not reliably 

Steps to Reproduce:
1. Install Docker
2. Pull Docker images
#docker pull vnguyen/rhq-psql
#docker pull docker-registry.usersys.redhat.com/jon_qe/jon33:dr1

3. Start Postgresql container
#docker run -d --name jon-psql vnguyen/rhq-psql

4. Start a container for JON but don't install anything yet
#docker run -dPit --link jon-psql:db --name jon-server docker-registry.usersys.redhat.com/jon_qe/jon33:dr1 /bin/bash

5. Attach to JON container
#docker attach jon-server

6. Install JON
#automated install script
#cat /usr/local/bin/rhq-server-docker.sh

#now install jon to /opt
#rhq-server-docker.sh


Actual results:
See attachments

Comment 1 Viet Nguyen 2014-08-15 20:17:41 UTC
Created attachment 927270 [details]
server.log

Comment 2 Mike Foley 2014-08-15 20:21:02 UTC
Running JON in docker containers is a use-case that may become more important.  Targetting this for JON 4.0 for now.

Comment 3 Filip Brychta 2019-06-24 14:53:47 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.