Created attachment 1396532 [details] all logs Description of problem: After upgrade of JON evn with 2 servers and 2 storage nodes to 3.3.10 there is a warning in agent log visible in additional storage. Version-Release number of selected component (if applicable): JON3.3.10 How reproducible: Alwyas Steps to Reproduce: 1. prepare postgres db to be able to accept remote connections on host 1 2. unzip jon-server-3.3.0.GA.zip 3. install the server: jon-server-3.3.0.GA/bin/rhqctl install 4. start it and wait until it's fully up 5. install additional jon server and storage node on another host 2 a) unzip jon-server-3.3.0.GA.zip b) edit jon-server-3.3.0.GA/bin/rhq-server.properties to use postgres on host 1 d) install the server: jon-server-3.3.0.GA/bin/rhqctl install e) start it 6. stop all components on both hosts jon-server-3.3.0.GA/bin/rhqctl stop 7. apply the patch on host 1 jon-server-3.3.0.GA-update-10/apply-updates.sh jon-server-3.3.0.GA 8. apply the patch on host 2 jon-server-3.3.0.GA-update-10/apply-updates.sh jon-server-3.3.0.GA 9. start all components on host 1 and wait until it's fully up 10 start all components on host 2 and wait until it's fully up Actual results: Following warning in agent.log on host2: 2018-02-15 09:01:31,855 WARN [MeasurementManager.collector-1] (rhq.core.pc.measurement.MeasurementCollectorRunner)- Failure to collect measurement data for Resource[id=10162, uuid=0e180baf-4dfa-4335-8980-51cccce72dc2, type={RHQStorage}MessagingService, key=org.apache.cassandra.net:type=MessagingService, name=Messaging Service, parent=RHQ Storage Node(fbr-ha2.bc.jonqe.lab.eng.bos.redhat.com)] - cause: java.lang.ClassCastException:java.lang.String cannot be cast to java.net.InetAddress Expected results: No warnings in logs Additional info: Tried to run Update Plugins on Agents operation and to restart everything but it did not help. Attaching rhq-server.properties, cassandra.yaml, agent.log, server log. Note that hostnames were used instead of IPs Server is bound to 0.0.0.0
Fixed in the master: commit 1768a029d7eff3b86a568e6483355bb3dcf0881f (HEAD -> master) Author: Michael Burman <miburman> Date: Tue Jul 17 16:11:59 2018 +0300 [BZ 1545742] If hostname is used as configuration parameter for Cassandra instead of ip address, our configuration lookup will fail since we assumed IP format was used
Used hostnames instead of IPs in rhq-server.properties and cassandra.yaml. Followed the steps and verified that after applying the patch and starting all components on host 2, there is no warning in agent.log of host2.
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://access.redhat.com/errata/RHSA-2018:2930