From 9100fe2ef992b0372523997bb7ac9a8060778057 Mon Sep 17 00:00:00 2001 From: Radhika PC Date: Fri, 23 Aug 2013 11:57:14 +0530 Subject: [PATCH] CLOUDSTACK-4469 upgrade exception added to known issues --- docs/en-US/Release_Notes.xml | 117 ++++++----------------------------- 1 file changed, 19 insertions(+), 98 deletions(-) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index d4550065c4e..ca1e19251e3 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -373,8 +373,8 @@ under the License. Known Issues in 4.2.0 - - + + @@ -386,6 +386,20 @@ under the License. + + CLOUDSTACK-4207 + + The following exception is observed when the Management Server is started + after upgrade from any older versions to &PRODUCT; 4.2. + jsonParseException: The JsonDeserializer + com.cloud.agent.transport.ArrayTypeAdaptor@2426e26f failed to deserialize json + object + Ignore this exception, this would stop after you upgrade the System VM. + However, if you want to prevent this, stop system VM from the hypervisor before + upgrade. + + CLOUDSTACK-2709 @@ -1229,52 +1243,6 @@ service cloudstack-agent start this on each Usage Server host. # service cloudstack-usage start - - (VMware only) Additional steps are required for each VMware cluster. These steps will not affect running guests in - the cloud. These steps are required only for clouds using VMware clusters: - - - Stop the Management Server: - service cloudstack-management stop - - - Generate the encrypted equivalent of your 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 - Store the output from this step, we need to add this in cluster_details table - and vmware_data_center tables in place of the plain text password - - - Find the ID of the row of cluster_details table that you have to update: - mysql -u <username> -p<password> - select * from cloud.cluster_details; - - - Update the plain text password with the encrypted one - update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_; - - - Confirm that the table is updated: - select * from cloud.cluster_details; - - - Find the ID of the correct row of vmware_data_center that you want to - update - select * from cloud.vmware_data_center; - - - update the plain text password with the encrypted one: - update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_; - - - Confirm that the table is updated: - select * from cloud.vmware_data_center; - - - Start the &PRODUCT; Management server - service cloudstack-management start - - - Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and @@ -1917,53 +1885,6 @@ service cloudstack-agent start this on each Usage Server host. # service cloudstack-usage start - - (VMware only) Additional steps are required for each VMware cluster, if you are - upgrading from version 3.0.4 or beyond. These steps will not affect running guests in - the cloud. These steps are required only for clouds using VMware clusters: - - - Stop the Management Server: - service cloudstack-management stop - - - Generate the encrypted equivalent of your 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 - Store the output from this step, we need to add this in cluster_details table - and vmware_data_center tables in place of the plain text password - - - Find the ID of the row of cluster_details table that you have to update: - mysql -u <username> -p<password> - select * from cloud.cluster_details; - - - Update the plain text password with the encrypted one - update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_; - - - Confirm that the table is updated: - select * from cloud.cluster_details; - - - Find the ID of the correct row of vmware_data_center that you want to - update - select * from cloud.vmware_data_center; - - - update the plain text password with the encrypted one: - update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_; - - - Confirm that the table is updated: - select * from cloud.vmware_data_center; - - - Start the &PRODUCT; Management server - service cloudstack-management start - - - (KVM only) Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM @@ -1991,9 +1912,9 @@ service cloudstack-agent start - (KVM only) Additional steps are required for each KVM host. These steps will not - affect running guests in the cloud. These steps are required only for clouds using KVM - as hosts and only on the KVM hosts. + (KVM only) Perform the following additional steps on each KVM host. + These steps will not affect running guests in the cloud. These steps are required + only for clouds using KVM as hosts and only on the KVM hosts. Configure your CloudStack package repositories as outlined in the Installation