Description of problem: Status printed by rhqctl for the storage node can be confusing if the user's terminal does not support a character set which includes the characters ✔ (U+2714 HEAVY CHECK MARK) and ✘ (U+2718 HEAVY BALLOT X). This is because the status is printed as ?running or ?down in the event the extended characters are not supported. Version-Release number of selected component (if applicable): 3.3 How reproducible: Always Steps to Reproduce: 1. Execute rhqctl status command using a locale that does not support extended characters: LC_CTYPE=C rhqctl status --storage Actual results: RHQ Storage Node (no pid file) is ?down Expected results: RHQ Storage Node (no pid file) is ✘down Additional info: This issue does not affect the agent or server because their status decorator is printed by the shell script rather then by Java code: RHQ Storage Node (pid 24597 ) is ?running RHQ Server (pid 433 ) is ✔running JBossAS Java VM child process (pid 564 ) is ✔running RHQ Agent (pid 1169 ) is ✔running
commit 1054ad0e115bf88a7faba44a6749b58b55565119 Author: Josejulio Martínez <jmartine> Date: Wed Apr 20 19:07:30 2016 -0500 Bug 1323325 - rhqctl status can report storage node as ?running or ?down if locale does not support extended character sets
Moving to ON_QA as available to test with JON 3.3.6 DR01 brew build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=499890
Verified on version : 3.3.0.GA Update 06 Build Number : 675641d:2fcd5b7 Verified on a solaris 10 vm (POSIX locale). Verified that before applying CP6, rhqctl status for storage was displaying below: RHQ Storage Node (no pid file) is ?down --------------------------------- RHQ Storage Node (pid 1247 ) is ?running After applying CP6, it shows: RHQ Storage Node (no pid file) is ✘down ------------------------------------------------------ RHQ Storage Node (pid 19528 ) is ✔running
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-1519.html