Bug 958089

Summary: RHQ Controll - rhqctl is not executable (doesn't have x permission)
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: InstallerAssignee: John Sanda <jsanda>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: high    
Version: JON 3.2CC: jsanda, loleary, mfoley
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-02 20:36:00 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: 951619    

Description Armine Hovsepyan 2013-04-30 11:19:00 UTC
Description of problem:
RHQ Controll - rhqctl is not executable (doesn't have x permission)

Version-Release number of selected component (if applicable):
jenkins build 177

How reproducible:
always

Steps to Reproduce:
1. 
2.
3.
  
Actual results:
rhqctl script is not executable by default 

Expected results:
rhqctl script should be executable by default

Additional info:

Comment 1 John Sanda 2013-04-30 17:43:58 UTC
The container build script has been updated to set the permissions on the rhqctl script. This change will be available in build 180.

Comment 2 Armine Hovsepyan 2013-05-02 17:49:48 UTC
reopened - last successful build (190) contains non-executable rhqctl

Comment 3 John Sanda 2013-05-02 19:59:33 UTC
This has to do with how the maven assembly plugin is configured in the rhq/modules/enterprise/server/appserver module. You also will find that other scripts do not have execute permission. This is not a regression as the behavior is the same in master. With that said, we should update the assembly plugin configuration to set the file permissions.

Comment 4 Armine Hovsepyan 2013-07-02 09:12:13 UTC
verified.