Filter
Top Products
Chapter 4. Upgrade Instructions
24
Note
After upgrade from 3.0.4 to 4.2, if the usage server fails to restart then copy db.properties
from /etc/cloudstack/management to /etc/cloudstack/usage. Then start the Usage Server.
16. (VMware only) If you are upgrading from 3.0.6 or beyond and you have existing clusters,
additional steps are required to update the existing vCenter password for each VMware cluster.
These steps will not affect running guests in the cloud. These steps are required only for clouds
using VMware clusters:
a. Stop the Management Server:
service cloudstack-management stop
b. Perform the following on each VMware cluster:
i. Encrypt the vCenter password:
java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar
org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh
input=<_your_vCenter_password_> password="`cat /etc/cloudstack/management/key`"
verbose=false
Save the output from this step for later use. You need to add this in the cluster_details and
vmware_data_center tables in place of the existing password.
ii. Find the ID of the cluster from the cluster_details table:
mysql -u <username> -p<password>
select * from cloud.cluster_details;
iii. Update the existing password with the encrypted one:
update cloud.cluster_details set value = <_ciphertext_from_step_i_> where id =
<_id_from_step_ii_>;
iv. Confirm that the table is updated:
select * from cloud.cluster_details;
v. Find the ID of the VMware data center that you want to work with:
select * from cloud.vmware_data_center;
vi. Change the existing password to the encrypted one: