Symptoms
Upon completing an upgrade of an App Volumes Manager, you may notice that either App Volumes Manager admin UI is not available, and the service cannot be started on the server.While attempting to access the AppVolumes manager console, it becomes inaccessible and displays the following error message:"Startup Failure – Unable to start App Volumes Manager – Migrations are pending. To resolve this issue, run bin/rails db:migrate RAILS_ENV=production."
Cause
The error occurs when attempting to validate the operating system during the execution of the command 'bundle.bat exec rake db:migrate RAILS_ENV=production'. The validation process encounters an error related to Ruby-ODBC and encoding issues.
Resolution
To work around the issue, uninstall the App Volumes Manager software on the server in question and reinstall it. On reinstall, point to the existing database. Do not select the Overwrite existing database (if any) check box. Once the reinstall completes, confirm the service is working properly by proceeding with registering the App Volumes Manager. For details, see the Register App Volumes Manager Server section in the VMware App Volumes Administration Guide at VMware Docs.If the issue still persist, Follow these steps to resolve the issue:
Stop the App Volumes Manager service.
Prior to proceeding, ensure that full backups of AVDB (App Volumes database) and the manager servers are taken for safety.
Access the AVDB and navigate to the "snapvol_operatingsystem" table.
Delete all rows that have a 'NULL' value under the 'Primordial' column. Use the following SQL command: DELETE FROM <tablename> WHERE primordial IS NULL;
Start the App Volumes Manager service.
From the C:\Program Files (x86)\CloudVolumes\Manager\ruby\bin> directory, execute the database migration command again: bundle.bat exec rake db:migrate RAILS_ENV=production
This time, the command should complete successfully.
Verify and confirm that the AVM UI now functions as expected.
Note: It is important to ensure that appropriate backups are taken before making any changes to the database. If you encounter any further issues or require additional assistance, please reach out to the technical support team for further guidance.
By following these steps, you should be able to resolve the issue of the AVM console being inaccessible after the upgrade. If error still occurs, follow the additional steps:
Stopped App volumes service.Removed file "xxxxxxxxx_change_version_limit_in_snapvol_apps_table.rb" from path D:\ProgramFiles(x86)\CloudVolumes\Manager\db\migrate on impacted App Volumes Manager VM.Ran below command from Windows command prompt again [migration completed]:
bundle exec rake db:migrate RAILS_ENV=productionAccess admin page to validate error is gone.
