ViPR Controller: Syncing - Configuration cannot be changed at this time, the system is not stable.

           

   Article Number:     489981                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller Controller 2.3,ViPR Controller

 

Issue:

 

 

   

      The ViPR application is in a constantly "Syncing" state.     
     
      The General Configuration tabs all show the following message:   
   
      Syncing - Configuration cannot be changed at this time, the system is not stable.   
   
     
      Running the command /opt/storageos/cli/bin/viprcli system remove-image -v vipr-2.2.0.1.1084 -force returned ViPR Controller to stable state.   
                                                             

 

 

Cause:

 

 

The ViPR Controller state remains "Syncing" because the previously downloaded ViPR Controller image files referenced in the backup are not available for automatic download through the ViPR Controller upgrade repository (A node recovery, node count change, backup and restore or upgrade operation were performed resulting in inconsistent availability entry of images in ViPR nodes)   
        
    It is the local repository which fails to fetch the images. While we backup the ViPR, we do not insert the previous images to the backup yet the entries about the images are backed up. If the entries are present in all the nodes, no issues. If they are missing on some nodes, they will try to sync within and fail as there is no image in the local repository.   
   
    You will have to do the steps in the Resolution only when there is a sync issue and this error is seen in syssvc logs. This is happening because the ViPR Controller image referenced vipr-2.2.0.1.1084 (example) is not available to download from repository:   

      UpgradeManager.java (line 637) Get remote image URL for version(vipr-2.2.0.1.1084) failed   
                                                             

 

 

Resolution:

 

 

   

         
  1.         View syssvc log, and locate the associated error, for example:     
  2.    
   

      Get remote image URL for version (vipr-2.2.0.1.1084) failed:com.emc.storageos.systemservices.exceptions.RemoteRepositoryException: Failed to read repository null (java.lang.NullPointerException)   

   
         
  1.         Forcefully remove this image by running the following CLI command for each image that had an issue downloading:                
               
    1.             Log in to any ViPR node:         
    2.        
                  
  2.    
   

      vi /opt/storageos/cli/viprcli.profile   

   
         
  1.         Edit VIPR_HOSTNAME with the Virtual IP of ViPR (UI)     
  2.    
   

      VIPR_HOSTNAME=xx.xx.xx.xx   

   
         
  1.         Save the file.     
  2.    
   

      /opt/storageos/cli/bin/viprcli authenticate -u root -d /tmp/cookie   

   
         
  1.         Log in as root with the password     
  2.    
   

      /opt/storageos/cli/bin/viprcli system remove-image -v vipr-2.2.0.1.1084 –force (Example only)   

   

      Running the above command will fix the issue, and after removing the image, the ViPR controller should return to stable state. (Check the previous logs and confirm the image versions.)   

                                                             

 

 

Notes:

 

 

This article has been promoted as HVC on DELL EMC Community Network (ECN): https://community.emc.com/docs/DOC-60072