Description of problem: Can't login with CLI client to JON 3.2 CP1
Version-Release number of selected component (if applicable):
JON 3.2.1 aka JON 3.2 CP
100%. me, viet. and docker-ized CLI automation.
Steps to Reproduce:
1. ./rhq-cli.sh -s 10.16.23.173 -u rhqadmin -p rhqadmin
[mfoley@foleymonsterbox1 bin]$ ./rhq-cli.sh -s 10.16.23.173 -u rhqadmin -p rhqadmin
RHQ Enterprise Remote CLI 4.9.0.JON320GA
Login failed: This client [3.2.0.GA-redhat-1] does not support the remote server [3.2.0.GA]
Usage: login username password [host port [transport]]
CLI client connects without compatibility check failure
This will block the running of the CLI automation ... (which could block the detection of other issues) ... so it should be of urgent priority.
This issue was detected with the new Docker-ized CLI automation test suite. This is a test suite that anyone (dev, community) can use to run the QE CLI automation against any JON 3.2 instance.
edge cases to additionally verify while verifying this BZ :
CLI mixed: existing CLI (JON 3.2 GA unpatched) with patched server (JON 3.2 GA patched) https://tcms.engineering.redhat.com/case/355140 positive testcase, should work
CLI mixed: patched CLI (JON 3.2 GA client patched to CP1) with unpatched server (JON 3.2 GA unpatched) https://tcms.engineering.redhat.com/case/355141 positive testcase, should work
This is fixed with commit c0c6cef9430b8c363 to RHQ release branch.
Moving this to MODIFIED for testing in next available productization build.
Moving to ON_QA as available for test in newest cumulative patch build from here:
I moved the earlier build to 3-18-2014.
Build Number :
JON 3.2.1 released week of 5/5/2014