 
            
            
            
            
                11 Feb
                
                    2020
                
            
            
                11 Feb
                
                '20
                
            
            
            
        
    
                9:11 a.m.
            
        Hi, We recently upgraded to 4.3.8 from 4.1.9. In the update process we set Cluster and DataCenter compatibility versions to 4.3, but now we're facing a problem with VmPools. They cannot be edited and 4.1 as compatibility level is still forcibly set. That means that when new machines are added to the pool, compatibility version 4.1 is set on them and they cannot be started as a message stating the following pops up: Failed to run VM XXX-34 due to a failed validation: [Cannot run VM. The Custom Compatibility Version of VM XXX-34 (4.1) is not supported in Data Center compatibility version 4.3.] (User: admin@internal). Is there a workaround to start those machines, or a way to fix the problem? Thanks.
        2089
        
      
          Age (days ago)
        
      
        2089
        
    
          Last active (days ago)
        
        
        
        0 comments
    
    
        
        1 participants
    
    
    
    
    
    
    
    
    participants (1)
- 
                 nicolas@devels.es nicolas@devels.es