Day 2 components missing after VCF Operations 9.0.2 to 9.1 upgrade.

Products

• VCF Operations

Issue/Introduction

• After upgrading VCF Operations from version 9.0.2 to 9.1, the "Log Management" component does not appear in the component tab.

• Manual import of VCF Log Operations fails at the "Discover Log Management Component Information" stage. This occurs while executing the steps in KB "Import VCF Operations in Fleet Lifecycle" stage of "Deploy VCF Management Components" workflow fails or completes with warnings

• Running nodetool-no-pass status via root SSH reveals that one or more cluster nodes are in a Down/Normal (DN) state 

• The /storage/core/loginsight/var/cassandra.log file on one or more nodes contains the error: "Corrupt hint file found"

Environment

• VCF Operations 9.1.x
• VCF Operations 9.0.x
• VCF Operations for Logs 9.0.x

Cause

During the upgrade process, Cassandra hint files can become bloated or corrupted, preventing the Cassandra service from starting on the primary node and leading to a cluster synchronization failure.

Resolution

1. Log in to the affected VCF Operations for Logs node via SSH as root.

2. Stop the Log Insight service: 

   service loginsight stop

3. Remove the corrupted hint files: 

   rm -rf /usr/lib/loginsight/application/lib/apache-cassandra-*/data/hints/*

4. Force start the Cassandra service to trigger a repair: 

   /usr/lib/loginsight/application/sbin/li-cassandra.sh --startnow --force

5. Verify the node status shows as UN (Up/Normal): 

   nodetool-no-pass status

6. Restart the Log Insight service: 

   service loginsight start

7. Retry the failed VCF Operations for Logs import task

Additional Information

VCF Operations for Logs UI is not available after upgrade to 9.0.2

"FAILED: Unable to get user data. Possible Cassandra is down" - Aria Operations for Logs