Icinga/icingaweb2-module-vspheredb

After Update to 1.7.1 module complains about DB schema change

pbirokas opened this issue · 0 comments

Expected Behavior

After an update there should be not complaining about db schema changes.

Current Behavior

After updating from Version 1.6.0 to 1.7.1 the icinga-vsphere service displays errors:
Trying to set invalid virtual_machine key "guest_ip_addresses". DB schema change?
We tried to update the mysql DB schema but it looks like it was already done by the service:

[root@icingaweb2 mysql-migrations]# mysql -u root -p vspheredb < upgrade_58.sql
Enter password:
ERROR 1060 (42S21) at line 1: Duplicate column name 'guest_ip_addresses'

Your Environment

  • VMware vCenter®/ESXi™-Version: 7.0.3
  • Version/GIT-Hash of this module: 1.7.1
  • Icinga Web 2 version: 2.11.4
  • Operating System and version: Rocky Linux release 8.8 (Green Obsidian)
  • Webserver, PHP versions: 7.4.33