Problem Information
Item | Description |
Storage type | Distributed storage |
Product version | FusionStorage 8.0.0; FusionStorage 8.0.1 |
Problem type | Capacity expansion |
Keyword | HCS; UVP package update |
Problem Symptom
After the UVP package of an earlier version has been imported to the existing FusionSphere OpenStack system, the UVP package of a later version cannot be imported.
Problem Diagnosis
Log in to the FusionSphere OpenStack web client and choose Cloud Service > FusionStorage to check whether the FusionStorage_Manager version of the created VM is the same as the version of the UVP package to be imported. If they are different, the old UVP package cannot be overwritten by importing a new package.
Causes
FusionSphere OpenStack does not allow component packages to be updated in overwritten mode. The current UVP package contains the storage software version. Therefore, you need to manually delete the current UVP package and then import a new one of a later version.
Solution
Use SSH to log in to a FusionSphere OpenStack node as user fsp, switch to user root, and run the following command to import the environment variables:
source set_env
Information similar to the following is displayed:
please choose environment variable which you want to import: (1) openstack environment variable (keystone v3) (2) cps environment variable (3) openstack environment variable legacy (keystone v2) please choose:[1|2|3]
Enter 1, press Enter, and enter the password of OS_USERNAME as prompted. The default password is FusionSphere123. The environment variables have been successfully imported if the command outputs of cps host-list and nova list are automatically displayed. After the environment variables are imported, the system uses Keystone V3 authentication, and you can run both CPS and OpenStack commands.
Run the cps package-instance-list | grep FusionStorage_Manager command to query the FusionStorage Manager version. FusionStorage Manager 8.0.1.1 is used as an example.
Run the cps package-delete --version FusionStorage_Manager_8.0.1.1 command to delete the FusionStorage Manager package of the earlier version.
Run the cps package-delete-status command to query the deletion progress. When progress is 100%, the deletion is complete.
Run the cps package-instance-list | grep FusionStorage_Manager command to check whether the FusionStorage Manager package of the earlier version has been deleted.
Log in to the FusionSphere OpenStack web client and choose Cloud Service > FusionStorage. In the Installation Package area, upload the latest UVP package FusionStorage_UVP_8.0.1.2.tar.gz.
Use SSH to log in to a FusionSphere OpenStack node as user fsp and switch to user root. Run the cps package-instance-list | grep FusionStorage_Manager command to query the updated FusionStorage Manager version.
Run the nova list | grep dsware command to query the IDs of the dsware server VMs.
Run the nova meta 0d5ef488-1709-4ffc-b0a4-6eca73c8965a set version=FusionStorage_Manager_8.0.1.2 command on all the queried dsware server VMs to modify the VM version to the updated version.
Log in to the FusionSphere OpenStack web client and choose Cloud Service > FusionStorage. In the VM List area, check whether the version of the created VMs is the updated version.
Check After Recovery
N/A
Suggestion and Summary
After a new UVP package is imported, the newly created VMs and new compute nodes will use the contents in the new package. However, the existing VMs and added compute nodes are not updated synchronously. The FusionStorage_Agent component of existing compute nodes needs to be updated by upgrading the storage package.
Applicable Versions
All
