'Upgrade Required' Flag Persists in Database Dashboard After Database Agents Wizard Completion (4309024)

After running the Database Agents Upgrade Wizard, the ‘Upgrade Required’ flag continues to appear on the Database Dashboard, even though the upgrade completed without errors.

This issue may occur in environments using a Federator FMS, where upgrade statuses from child FMS instances are not reflected immediately.

• The Foglight Management Server (FMS) UI has not refreshed the agent status and topology data after the upgrade.
• In federated environments, the Federator FMS may continue to display outdated status information for agents that were already upgraded on a child FMS.
• Cached topology or upgrade flags are not cleared post-wizard.
• Communication latency between the Federator and child FMS may delay UI updates.
• Partial or incomplete agent upgrade may leave flags behind.

Resolution 1 – Restart FglAMs After FMS Upgrade

Ensure all associated Foglight Agent Managers (FglAMs) are running and properly connected to the Foglight Management Server (FMS) after the FMS has been upgraded.
It may be necessary to restart the FglAMs manually.

Once the connections are re-established, the "Upgrade" option for the database agents should appear at the top of the Database dashboard.

Resolution 2 – Override Upgrade Flag Using Script Console

Manually override the isUpgradeRequired flag by running one of the following Groovy scripts in the FMS console:

Location:
Administration > Tooling > Script Console > Scripts Tab > Add > Enter script text

Disclaimer:
The following scripts are known to work successfully in lab environments, but have not been officially tested by Quest QA.
Always back up the Foglight installation and repository before executing scripts that modify topology.

Oracle Agents:

def dataService = server.DataService;
def canonicalFactory = server.CanonicalFactory;
def agents = #!DBO_Agent_Model#.topologyObjects;
for (agent in agents) {
    dataService.publish(canonicalFactory.createNode(agent, "isUpgradeRequired", "false", 60000L));
}
return true;

SQL Server Agents:

def dataService = server.DataService;
def canonicalFactory = server.CanonicalFactory;
def agents = #!DBSS_Agent_Model#.topologyObjects;
for (agent in agents) {
    dataService.publish(canonicalFactory.createNode(agent, "isUpgradeRequired", "false", 60000L));
}
return true;

DB2 Agents:

def dataService = server.DataService;
def canonicalFactory = server.CanonicalFactory;
def agents = #!DB2_Agent_Model#.topologyObjects;
for (agent in agents) {
    dataService.publish(canonicalFactory.createNode(agent, "isUpgradeRequired", "false", 60000L));
}
return true;

Resolution 3 – Federator Topology Sync

In federated environments, restart the FglAM hosting the database agent. This ensures the agent is properly shut down.

Then:

1. Delete the broken agent from the child FMS.

2. Recreate the agent on the child FMS.

3. Wait for the child FMS to synchronize with the Federator.

Once synchronization is complete, the "Upgrade Required" flag should no longer appear on the Federator's Database dashboard.

Resolution 4 – Align Cartridge Versions

Ensure that all child FMSs and the Federator are running the same version of the Database cartridge.

Once cartridge versions are consistent across all servers, the upgrade flag should clear automatically.

Resolution 5 – Additional Troubleshooting

Refer to KB 4290194 for further troubleshooting steps related to lingering upgrade indicators and agent inconsistencies.

Resolution 6 – Manual Cartridge Upgrade for Offline FglAM

If the FglAM is offline when the Database Agent Upgrade Wizard runs following a cartridge upgrade, the agents on that FglAM will not be upgraded.

Once the FglAM reconnects:

• The Database dashboard should detect the pending upgrade and display the wizard.

• If not, navigate to:
  Administration > Agents > Agent Managers
  Manually upgrade the Database cartridge on the affected FglAM.

Resolution 7 – Reset the DB_Global_View_UI Cartridge

To resolve UI display issues affecting the upgrade flag:

1. Go to Administration > Cartridges > Cartridge Inventory.

2. Locate the DB_Global_View_UI cartridge.

3. Check the box next to it.

4. Click Reset at the top of the table.

Important Note:

Quest Support and Development strongly recommend creating a full backup of the Foglight installation and repository database before executing any script, resetting cartridges, or removing topology data.

Cartridge upgrades consist of two phases

1. The first phase is installing the cartridge in Cartridge Inventory. This activity transfers the cartridge through the browser to the FMS cartridge manages the UI and basic functionality of the product.
2. The second phase, deploys a subset of the cartridge (a .gar file) from the FMS to the Agent Managers. It could be done through a wizard (as in the SQL Server, Oracle, and DB2 cartridges), or manually through the Administration | Agent Status or Administration | Agent Managers pages. This component on the FglAM is used for the communication processes between the local/remote host and the collections that run again the host.