ViPR Controller: Reoccurring pending "Actionable Events" after upgrade to 3.5

           

   Article Number:     494137                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller,ViPR Controller Controller 3.5

 

Issue:

 

 

   

      Pending Actionable Events keeps on reoccurring after upgrading to ViPR Controller 3.5   

   

      User-added image     
     
          

   

          

                                                             

 

 

Cause:

 

 

Manually created cluster of discoverable Linux hosts generate Actionable event to remove the host from manual cluster after every discovery cycle.    
     
                                                           

 

 

Change:

 

 

Upgrading to 3.5                                                            

 

 

Resolution:

 

 

   

       If we 'Disable the Discovery of the Linux host' and the actionable events will not get generated during every discovery cycle.   

   

      Edit the Hosts that the actionable events gets triggered on and Uncheck the "Discoverable" option and then Save.     
      After that the Automatically discovered information from the host regarding IP Interfaces and Initiators would be disabled for this host(s).     
     
      The impact of disabling the discovery for these hosts would be just that if initiators (HBAs) are replaced for the host, then we will not be generating Actionable Events. In case of HBAs replacement for these hosts, then we can enable the discovery for these hosts and approve only the HBA replacement Actionable Events.