From 2f1c2fbd79f2b4fad0612f9569f1e5609fb0cb74 Mon Sep 17 00:00:00 2001
From: Joe Brockmeier <jzb@zonker.net>
Date: Sun, 23 Jun 2013 14:15:10 -0500
Subject: [PATCH] Removing a redundant step (stop service twice in upgrade 4.0
 to 4.1). Hack Day.

---
 docs/en-US/Release_Notes.xml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/en-US/Release_Notes.xml b/docs/en-US/Release_Notes.xml
index 46d97a3c3f8..687a93dd021 100644
--- a/docs/en-US/Release_Notes.xml
+++ b/docs/en-US/Release_Notes.xml
@@ -4708,10 +4708,6 @@ under the License.
                     <para>Make a backup of your MySQL database. If you run into any issues or need to roll back the upgrade, this will assist in debugging or restoring your existing environment. You'll be prompted for your password.</para>
                     <programlisting><prompt>#</prompt> mysqldump -u root -p cloud &gt; cloudstack-backup.sql</programlisting>
                 </listitem>
-                <listitem>
-                    <para>Whether you're upgrading a Red Hat/CentOS based system or Ubuntu based system, you're going to need to stop the CloudStack management server before proceeding.</para>
-                    <programlisting language="Bash"><prompt>#</prompt> service cloud-management stop</programlisting>
-                </listitem>
                 <listitem>
                     <para>If you have made changes to <filename>/etc/cloud/management/components.xml</filename>, you'll need to carry these over manually to the new file, <filename>/etc/cloudstack/management/componentContext.xml</filename>. This is not done automatically. (If you're unsure, we recommend making a backup of the original <filename>components.xml</filename> to be on the safe side.</para>
                 </listitem>