UBA 5.4.2 Upgrade fails due to RHEL version compatibility issue

Available Languages

Updated:October 1, 2026
Document ID:SPLK051740

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

User Behavior Analytics 5.4.2

Description

During the upgrade of Splunk UBA from version to 5.4.2, the upgrade process aborts during the PreReqCheck step due to operating system version incompatibility. The upgrade script performs a prerequisite validation to confirm that the underlying operating system meets the supported version requirements.

On systems running RHEL 8.6, the script identifies the OS version as unsupported and terminates the upgrade process. The failure is reflected in the following error message:

pre-requisites check failed on node: "UBA-IP", exiting
Wed Aug 27 13:48:08 UTC 2025: Upgrade failed in step: PreReqCheck, aborting

Investigation

Upon Investigation , the Splunk documentation provides information regarding supported operating system versions for UBA 5.4.2:

  • In the What's New section of the 5.4.2 Release Notes, the supported operating systems are explicitly listed as RHEL 8.8 and RHEL 8.10.

  • The UBA 5.4.2 Upgrade Guide states that no operating system upgrade is required if the system is already on RHEL 8.6 or RHEL 8.8, which implies that RHEL 8.6 may still be considered supported for upgrade scenarios.

This inconsistency creates ambiguity regarding whether RHEL 8.6 is officially supported when upgrading or installing UBA 5.4.2.

During the upgrade attempt, the upgrade script performs a prerequisite validation and identifies the operating system version (RHEL 8.6) as unsupported. The process fails during the PreReqCheck stage with the following log messages:


The failure confirms that the upgrade script strictly enforces RHEL 8.8 and RHEL 8.10 as supported operating systems, rejecting RHEL 8.6 even though parts of the documentation imply otherwise.


Resolution
Splunk UBA 5.4.2 supports only Red Hat Enterprise Linux (RHEL) 8.8 and RHEL 8.10.


To resolve the issue, environments running RHEL 8.6 or older must upgrade the operating system to one of the supported versions before proceeding with the UBA upgrade.


As an alternative, the prerequisites validation can be bypassed by following the steps documented in the knowledge base article:


UBA – Bypass RHEL and OEL upgrade script if running an unsupported version upgrading to later/latest UBA version



    
    


















     

     
    
            
         	

                
Revision History

                

                    
 
                        
                            

                                Revision
                                Publish Date
                                Comments
                            

                            
                                                
                            
          
                                    

                                        
1.0

                                        

                                            
                                                01-Oct-2026
                                            
                                        

                                        
                                            
Initial Release

                                                                    
                                    

          
                            

                        
                    

                

            

        
    








	




    


    

        














 




























    

    

        

    

    
    
     
			
            

























    
    
    
    









            

                

















  
  

  
    
    
    
    
  






            

        
            
            




















  
Was this Document Helpful?

  
    
    
  
  
    
      
      FeedbackFeedback
    
  







            

                

















  
    
  



            


            

                
















    
Contact Cisco

    







            


            
            































    
   
    





            

                























    

	
  	


            


        
            

                
            

        

    

    
        

            
            

















    

            
Related Articles