Bug 535763 (RHQ-2425) - Port argument for CLI start-up script ignored unless host argument also specified
Summary: Port argument for CLI start-up script ignored unless host argument also speci...
Keywords:
Status: CLOSED WONTFIX
Alias: RHQ-2425
Product: RHQ Project
Classification: Other
Component: CLI
Version: unspecified
Hardware: All
OS: All
low
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On: RHQ-2298
Blocks: rhq_triage
TreeView+ depends on / blocked
 
Reported: 2009-09-15 15:02 UTC by John Sanda
Modified: 2014-05-09 15:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-09 15:50:17 UTC
Embargoed:

Attachments (Terms of Use)

Description John Sanda 2009-09-15 15:02:00 UTC 
You can specify the port and host with the start up script which is useful for connecting to different hosts and for running over SSL. Consider the following,

$ rhq-cli.sh -u rhqadmin -p rhqadmin -s localhost --port=7443 

The above will log me into the server running on localhost and will communications will be over SSL. If however, I leave out the host (-s) option, the port is ignored and the default (7080) is used. This needs to be modified so that the port is not ignored even when the host is not specified.
Comment 1 John Sanda 2009-09-15 15:02:42 UTC 
Discovered this as a result of testing RHQ-2298
Comment 2 Red Hat Bugzilla 2009-11-10 21:04:13 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2425
Comment 3 wes hayutin 2010-02-16 16:56:45 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 4 wes hayutin 2010-02-16 17:02:02 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 5 Corey Welton 2010-10-07 03:44:13 UTC 
Triaged 5-Oct
Comment 6 Jay Shaughnessy 2014-05-09 15:50:17 UTC 
This may have been fixed, if not I think this has expired.
Note You need to log in before you can comment on or make changes to this bug.