Bug 1148403

Summary:	Remote agent install won't work correctly with *csh
Product:	[JBoss] JBoss Operations Network	Reporter:	Michael Burman <miburman>
Component:	Agent	Assignee:	John Mazzitelli <mazz>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:	mmurray
Priority:	unspecified
Version:	JON 3.3.0	CC:	fbrychta, hrupp, loleary, myarboro
Target Milestone:	---	Keywords:	Documentation, EasyFix
Target Release:	JON 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	The remote agent installation runs shell scripts on the target machine. Those require a Bourne Shell like /bin/sh or /bin/bash. They will not work correctly with other types of shells like (t)csh. The user should use select a Bourne Shell as login shell of the account the remote agent is installed into.	Story Points:	---
Clone Of:		Environment:	[Install_Guide] Added Text into the Release Notes. Checking with Larry whether it also needs mention in the Installation Guide.
Last Closed:	2019-06-10 15:02:31 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:
Bug Depends On:
Bug Blocks:	1070242

Description Michael Burman 2014-10-01 11:51:50 UTC

Description of problem: The remote agent install will only work with sh or compatible shell. If the destination account is using csh/tcsh, the process will fail on several occasions.

---

The method to check if agent has been installed already (agentInstallCheck in SSHInstallUtility) sends a command with bash-only syntax (if [ -f .. ] ), that prevents the feature from working if destination account is using some other shell as default. This is the only command that depends on the bash-syntax.

agentInstallCheck malfunction will result in agent not installed will be presented, even if the agent is found and is running. Also, agent override existing installation = "no" will not work, but it is always overwritten.

"Remove any old agent update binary jars" part of the installation will fail, if there's no old files, as csh will evaluate *-sign and show an error "rm: No match" with exitCode 1, while bash will not show anything and return exit code 0 (and we expect empty return).

Version-Release number of selected component (if applicable): 3.3.0.ER05


How reproducible: Always


Steps to Reproduce:
1. chsh to something not compatible with bash (for example tcsh)
2. 
3.

Actual results: 


Expected results:


Additional info:

Comment 5 Heiko W. Rupp 2014-10-16 09:16:53 UTC

Turning into docs bug

Comment 7 Simeon Pinder 2014-10-20 17:26:40 UTC

Moving to CR01 as missed ER05 initial and extended cutoffs.

Comment 12 Mike McCune 2016-03-28 23:02:11 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 13 Filip Brychta 2019-06-10 15:02:31 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.