# Fixpack information remains visible after a major version upgrade in CubeCOS.

> The fixpack information should not remain visible after a major firmware upgrade in CubeCOS.

## Summary {#summary}

After upgrading to a new version of CubeCOS firmware, i.e., upgrading from 3.1.x to 3.2.0, the list of fixpacks should be updated and empty. In CubeCOS 3.1.0, fixpack versions will be displayed incorrectly to users after a firmware upgrade.

## Details {#details}

Steps to reproduce this symptom:

1. Install a fixpack on CubeCOS.
2. Upgrade the CubeCOS firmware.
3. Wait for the cluster to start.
4. Go to `Maintenance > Update > Fixpack` List.
5. The old fixpack version will still shown under the `Fixpack List` section.

This issue occurs because CubeCOS only removes the fixpack history after `cube-cos-api` is started. Consequently, the UI continues to display the fixpack version until `cube-cos-api` is manually restarted.

### Applicable versions {#applicable-versions}

CubeCOS 3.1.0

This article applies to environments running CubeCOS version 3.1.0.

## Resolution {#resolution}

The official patch will be included in a the 3.2.0 release. To mitigate the issue in CubeCOS 3.1.0, manually restart `cube-cos-api` on all control nodes.

### Apply the official patch (recommended) {#apply-the-official-patch-recommended}

Upcoming in CubeCOS 3.2.0.

### Restart the CubeCOS API manually to mitigate the issue {#restart-the-cubecos-api-manually-to-mitigate-the-issue}

To restart CubeCOS API manually on all control nodes, perform the following:

1. Open a terminal session.
2. Connect to the cluster VIP via SSH and log in as the `root` user.

   ```bash
   ssh root@<your-cluster-vip>
   ```

3. Execute the following command to restart the `cube-cos-api` component on all control nodes:

   ```bash
   cubectl node exec -p 'systemctl restart cube-cos-api' -r control
   ```

4. Verify that the `cube-cos-api` component has restarted without error on all control nodes.

   The output of the status for all nodes should return "Active: active (running)."

   ```bash
   cubectl node exec -p 'systemctl status cube-cos-api' -r control
   ```