Problem:

A client migrated their Opsview version from 6.9.3 to 6.11.4. During Step 3 (Opsview MySQL databases) of Migrate Opsview 6 to new hardware, running setup-everything.yml failed with the following error:

ERROR 1146 (42S02) at line 1: Table 'opsview.notifications' doesn't exist

The opsview.notifications table is also missing from the original Opsview 6.9.3 database, causing the deployment to fail.

Possible solution:

1. Disable or uncomment the lines in the Opsview crontab, ie no backups, import_runtime, housekeep on:

   crontab -e -u opsview

2. Run the database upgrade scripts on the orchestrator as the opsview user:

   /opt/opsview/coreutils/installer/upgradedb_opsview.pl
   /opt/opsview/coreutils/installer/upgradedb_runtime.pl

3. Validate if opsview.notifications now exists

   <Access opsview database>
   MySQL [opsview]> desc notifications;

4. Re-run the deployment playbooks:

   cd /opt/opsview/deploy/
   
   # configure the base hosts
   ./bin/opsview-deploy lib/playbooks/setup-hosts.yml
   
   # install and configure the core infrastructure (database, datastore, messagequeue, etc)
   ./bin/opsview-deploy lib/playbooks/setup-infrastructure.yml
   
   # install core files for the orchestrator
   ./bin/opsview-deploy lib/playbooks/orchestrator-install.yml

5. Verify or update the messagequeue and datastore host variables are set to the correct values.

Related article(s):

• Migrate Opsview 6 to new hardware

• JIra Bug: OP-75273

   

If you need further help:

• Please contact with our Client Services team via the chat service box available in any of our websites or via email to support@itrsgroup.com
  
• Make sure you provide to us:
  • ANY LOG FILE OR DIAGNOSTIC
  • ANY SCREENSHOT
  • ANY VENDOR/VERSION OF WHAT THEY ARE TRYING TO CONNECT TO
  • Any troubleshooting step already verified from the ones described in this article.