Bug 1110623

Summary: Auto-config fails to execute as NRPE is NOT set to restart after 'Add Host'
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanth <pprakash>
Component: rhscAssignee: Darshan <dnarayan>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: high Docs Contact:
Priority: urgent    
Version: rhgs-3.0CC: alonbl, dnarayan, dpati, kmayilsa, ltrilety, nlevinki, rhs-bugs, rhsc-qe-bugs, sgraf
Target Milestone: ---   
Target Release: RHGS 3.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-host-deploy-1.2.2-1.el6ev Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1111053 (view as bug list) Environment:
Last Closed: 2014-09-22 19:11:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1111053, 1111268    
Bug Blocks:    

Description Prasanth 2014-06-18 05:48:31 UTC 
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.
Comment 1 Alon Bar-Lev 2014-06-18 14:31:21 UTC 
Please move/duplicate to rhev/ovirt-host-deploy so I can add this to errata.
Comment 2 Dusmant 2014-06-19 08:49:43 UTC 
RHEV bug is : https://bugzilla.redhat.com/show_bug.cgi?id=1111053 and added dependency...
Comment 3 Prasanth 2014-06-26 14:08:19 UTC 
Verified in ovirt-host-deploy-1.2.2-1.el6ev

------------------
# /usr/lib64/nagios/plugins/gluster/discovery.py -c ErrataCluster -H 10.70.43.90                                                                                
Cluster configurations changed                                                                                                                                                                
                                                                                                                                                                                              
Changes :                                                                                                                                                                                     
Hostgroup ErrataCluster - ADD                                                                                                                                                                 
Host ErrataCluster - ADD                                                                                                                                                                      
         Service - Volume Utilization - firstvol -ADD                                                                                                                                         
         Service - Volume Self-Heal - firstvol -ADD                                                                                                                                           
         Service - Volume Status - firstvol -ADD                                                                                                                                              
         Service - Volume Utilization - secondvol -ADD                                                                                                                                        
         Service - Volume Status - secondvol -ADD                                                                                                                                             
         Service - Cluster Utilization -ADD                                                                                                                                                   
         Service - Cluster - Quorum -ADD 
         Service - Cluster Auto Config -ADD 
Host dhcp43-90.lab.eng.blr.redhat.com - ADD
         Service - Brick Utilization - /rhs/brick1/first -ADD 
         Service - Brick - /rhs/brick1/first -ADD 
         Service - Brick Utilization - /rhs/brick2/second -ADD 
         Service - Brick - /rhs/brick2/second -ADD 
Host dhcp42-241.lab.eng.blr.redhat.com - ADD
         Service - Brick Utilization - /rhs/brick1/first -ADD 
         Service - Brick - /rhs/brick1/first -ADD 
         Service - Brick Utilization - /rhs/brick2/second -ADD 
         Service - Brick - /rhs/brick2/second -ADD 
Are you sure, you want to commit the changes? (Yes, No) [Yes]: 
Enter Nagios server address [rhs-client3.lab.eng.blr.redhat.com]: 
Cluster configurations synced successfully from host 10.70.43.90
Do you want to restart Nagios to start monitoring newly discovered entities? (Yes, No) [Yes]: 
Nagios re-started successfully
------------------
Comment 4 errata-xmlrpc 2014-09-22 19:11:20 UTC 
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.

http://rhn.redhat.com/errata/RHEA-2014-1277.html