+++ This bug was initially created as a clone of Bug #1111053 +++ +++ This bug was initially created as a clone of Bug #1110623 +++ Description of problem: Auto-config fails with "Error : CHECK_NRPE: Error - Could not complete SSL handshake" when RHSC engine uses a resolvable hostname. See below: ----------- # /usr/lib64/nagios/plugins/gluster/discovery.py -c 34cluster -H 10.70.42.229 Failed to execute NRPE command 'discoverhostparams' in host '10.70.42.203' Error : CHECK_NRPE: Error - Could not complete SSL handshake. Make sure NPRE server in host '10.70.42.203' is configured to accept requests from Nagios server ----------- Version-Release number of selected component (if applicable): rhsc-3.0.0-0.10.el6_5.noarch nagios-server-addons-0.1.3-3.el6rhs.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install and setup RHSC + Nagios Server by following http://rhsm.pad.engineering.redhat.com/rhsc-nagios-release-denali-7 2. Make sure that the RHSC engine is having a DNS resolvable hostname (EX: dhcp43-180.lab.eng.blr.redhat.com) 3. Add a few RHS nodes to a 3.4 cluster from the UI 4. Now, execute the following auto-config script from the engine: # /usr/lib64/nagios/plugins/gluster/discovery.py -c <cluster-name> -H <ip-address> Actual results: Auto-config script fails with the error mentioned above. Expected results: Auto-config script should execute sucessfully and detect the changes in the cluster configurations. Additional info: Restarting nrpe in ALL the RHS nodes seems to resolve the issue. --- Additional comment from Alon Bar-Lev on 2014-06-18 10:31:21 EDT --- Please move/duplicate to rhev/ovirt-host-deploy so I can add this to errata. --- Additional comment from Pavel Stehlik on 2014-06-19 05:30:12 EDT --- Guys, are you able to verify this? We don't have environment for testing this. Thank you, P. --- Additional comment from errata-xmlrpc on 2014-06-19 09:39:21 EDT --- Bug report changed to ON_QA status by Errata System. A QE request has been submitted for advisory RHBA-2014:18082-01 https://errata.devel.redhat.com/advisory/18082
pavel, why was this bug removed from errata for 3.4.1? afaiu this fix was already released with ovirt-host-deploy. wasn't it verified?
Verified this bug with RHS 3.0 RC ( glusterfs-3.6.0.27-1.el6rhs ) and RHEVM 3.4.2 ( av11 ) 3.4.2-0.1.el6ev 1. Stopped nrpe in RHSS Node 2. Added the node to RHEV Observation - Found that nrpe got started after adding the node to RHEVM Also I see that nrpe was listening to port 5666 [Wed Aug 27 06:34:20 UTC 2014 root.37.138:~ ] # netstat -tulp | grep 5666 tcp 0 0 *:5666 *:* LISTEN 17205/nrpe Based on the above observation, marking this bug as VERIFIED