From 81b4966a71606bfb0797e135dcdc639824df7619 Mon Sep 17 00:00:00 2001 From: Radhika PC Date: Fri, 16 Aug 2013 14:41:46 +0530 Subject: [PATCH] CLOUDSTACK-4245 known issues section updated with removing the fixed issues, upgrade section updated with CentOS 5.5 issue with upgrading usage server --- docs/en-US/Release_Notes.xml | 78 +++++++++++------------------------- 1 file changed, 23 insertions(+), 55 deletions(-) diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml index d1d0d1ba3fe..2db405ca5f8 100644 --- a/docs/en-US/Release_Notes.xml +++ b/docs/en-US/Release_Notes.xml @@ -213,7 +213,7 @@ under the License. ###
- Autoscale + <para>###</para> </section> <section id="api-throttling"> @@ -455,43 +455,6 @@ under the License. has not started yet.</para> </entry> </row> - <row> - <entry><para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-1824" - >CLOUDSTACK-1824</ulink></para></entry> - <entry><para>Service CloudStack-Management is being displayed as cloud-management - service </para> - <para>Many scripts and text entries have references to cloud-management rather than - cloudstack-management due to the changeover between 4.0 and 4.2 to rename - services. This is a minor issue and should be corrected by 4.2.</para> - </entry> - </row> - <row> - <entry> - <para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-1824" - >CLOUDSTACK-1824</ulink></para></entry> - <entry><para>Service CloudStack-Management is being displayed as cloud-management - service</para> - </entry> - </row> - <row> - <entry> - <para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-1510" - >CLOUDSTACK-1510</ulink></para> - </entry> - <entry> - <para>NPE when primary storage is added with wrong path</para> - </entry> - </row> - <row> - <entry> - <para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-1428" - >CLOUDSTACK-1428</ulink></para> - </entry> - <entry> - <para>[UI] Instance which are created without display name are not visible when - added to LB</para> - </entry> - </row> <row> <entry> <para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-1306" @@ -559,15 +522,6 @@ under the License. <para>Creation of compute offering allow combination of local storage + HA</para> </entry> </row> - <row> - <entry> - <para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-282" - >CLOUDSTACK-282</ulink></para> - </entry> - <entry> - <para>Virtual Routers do not properly resolve DNS SRV Records</para> - </entry> - </row> <row> <entry> <para><ulink url="https://issues.apache.org/jira/browse/CLOUDSTACK-276" @@ -637,7 +591,7 @@ under the License. <para>If you run into any issues during upgrades, please feel free to ask questions on users@cloudstack.apache.org or dev@cloudstack.apache.org.</para> <section id="upgrade-from-4.0-to-4.1"> - <title>Upgrade from 4.0.x to 4.2.0 + Upgrade from 4.x.x to 4.2.0 This section will guide you from &PRODUCT; 4.0.x versions to &PRODUCT; 4.2.0. Any steps that are hypervisor-specific will be called out with a note. @@ -645,9 +599,9 @@ under the License. The package structure for &PRODUCT; has changed significantly since the 4.0.x releases. If you've compiled your own packages, you'll notice that the package names and the number of packages has changed. This is not a bug. - However, this does mean that the procedure is not as simple as an - apt-get upgrade or yum update, so please follow - this section carefully. + However, this does mean that the procedure is not as simple as an apt-get + upgrade or yum update, so please follow this section + carefully. We recommend reading through this section once or twice before beginning your upgrade procedure, and working through it on a test system before working on a production @@ -693,8 +647,8 @@ under the License. After upgrading to 4.2, API clients are expected to send plain text passwords for - login and user creation, instead of MD5 hash. Incase, api client changes are not - acceptable, following changes are to be made for backward compatibility: + login and user creation, instead of MD5 hash. If API client changes are not acceptable, + following changes are to be made for backward compatibility: Modify componentsContext.xml, and make PlainTextUserAuthenticator as the default authenticator (1st entry in the userAuthenticators adapter list is default) @@ -804,7 +758,8 @@ service cloudstack-agent restart The first order of business will be to change the yum repository for each system with &PRODUCT; packages. This means all management servers, and any hosts that have - the KVM agent. (No changes should be necessary for hosts that are running VMware or + the KVM agent. + (No changes should be necessary for hosts that are running VMware or Xen.) Start by opening /etc/yum.repos.d/cloudstack.repo on any systems that have &PRODUCT; packages installed. @@ -816,7 +771,7 @@ baseurl=http://cloudstack.apt-get.eu/rhel/4.0/ enabled=1 gpgcheck=0 - If you are using the community provided package repository, change the baseurl + If you are using the community provided package repository, change the base url to http://cloudstack.apt-get.eu/rhel/4.2/ If you're using your own package repository, change this line to read as appropriate for your 4.2.0 repository. @@ -839,6 +794,19 @@ gpgcheck=0 /etc/cloud/agent to /etc/cloudstack/agent. + + For CentOS 5.5, perform the following: + + + Run the following command: + rpm -Uvh http://download.cloud.com/support/jsvc/jakarta-commons-daemon-jsvc-1.0.1-8.9.el6.x86_64.rpm + + + Upgrade the Usage server. + sudo yum upgrade cloud-usage + + + Verify that the file /etc/cloudstack/agent/environment.properties has a line that