After the upgrade to VNA 22.2.4 the notification filter stopped to work and trying to GET notification filter details from the VNA Notification user interface, the GET request loads endlessly and comes to no result.
Release : 22.2
The inventory table had the index corrupted.
./mysqlcheck -uroot -padmin --all-databases
showed:
mysql.columns_priv OK
mysql.component OK
mysql.db OK
mysql.default_roles OK
mysql.engine_cost OK
mysql.func OK
mysql.general_log OK
mysql.global_grants OK
mysql.gtid_executed OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.password_history OK
mysql.plugin OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.replication_asynchronous_connection_failover OK
mysql.replication_asynchronous_connection_failover_managed OK
mysql.replication_group_configuration_version OK
mysql.replication_group_member_actions OK
mysql.role_edges OK
mysql.server_cost OK
mysql.servers OK
mysql.slave_master_info OK
mysql.slave_relay_log_info OK
mysql.slave_worker_info OK
mysql.slow_log OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
sys.sys_config OK
vna_slfjdedcnm104.aciendpointgroup_labels OK
vna_slfjdedcnm104.application_class_entry OK
vna_slfjdedcnm104.applicationroutingpolicy_backuppaths OK
vna_slfjdedcnm104.applicationroutingpolicy_preferredpaths OK
vna_slfjdedcnm104.cache_keys OK
vna_slfjdedcnm104.custom_properties OK
vna_slfjdedcnm104.databasechangelog OK
vna_slfjdedcnm104.databasechangeloglock OK
vna_slfjdedcnm104.entity_tags OK
vna_slfjdedcnm104.inventory
Warning : InnoDB: The B-tree of index PRIMARY is corrupted.
error : Corrupt
vna_slfjdedcnm104.ip_address OK
vna_slfjdedcnm104.ipdevice_dnsnames OK
vna_slfjdedcnm104.ipdevice_macaddresses OK
vna_slfjdedcnm104.ipdevice_roles OK
vna_slfjdedcnm104.local_id_cache OK
vna_slfjdedcnm104.local_id_cache_backup OK
vna_slfjdedcnm104.local_id_cache_meta OK
vna_slfjdedcnm104.network_segment OK
vna_slfjdedcnm104.networkpath_hops OK
vna_slfjdedcnm104.notification_attributes OK
vna_slfjdedcnm104.notification_filter_cache OK
vna_slfjdedcnm104.notification_filter_cache_backup OK
vna_slfjdedcnm104.notification_filter_cache_meta OK
vna_slfjdedcnm104.notification_sequence OK
vna_slfjdedcnm104.notifications OK
vna_slfjdedcnm104.perspectives OK
vna_slfjdedcnm104.perspectives_keys OK
vna_slfjdedcnm104.pluginconfig OK
vna_slfjdedcnm104.pluginvariable OK
vna_slfjdedcnm104.policy_rules OK
vna_slfjdedcnm104.relation OK
vna_slfjdedcnm104.relation_perspectives OK
vna_slfjdedcnm104.remote_vna_aggregator_cache OK
vna_slfjdedcnm104.remote_vna_aggregator_cache_backup OK
vna_slfjdedcnm104.remote_vna_aggregator_cache_meta OK
vna_slfjdedcnm104.rules OK
vna_slfjdedcnm104.self_monitoring_configurations OK
vna_slfjdedcnm104.servicefunctionchain_networkfunctionids OK
vna_slfjdedcnm104.servicefunctionchain_networkfunctioninterfaceids OK
vna_slfjdedcnm104.subnetted_ip_address OK
vna_slfjdedcnm104.textmatchrule_stringstomatch OK
vna_slfjdedcnm104.vnaconfig OK
1) stop wildfly
service wilfly stop
2) take a backup of VNA database
/opt/CA/VNA/tools/bin/db_backup.sh -p admin /tmp/vna_db.sql
3) login to mysql and drop the database
cd /opt/CA/mysql/bin
./mysql -u root -p
mysql> show databases;
mysql> drop database vna_slfjdedcnm104;
mysql> exit
4) restore the database from the backup
/opt/CA/VNA/tools/bin/db_restore.sh /tmp/vna_db.sql
5) verify that the database was successfully restored and then start wildfly
service wildfly start