Filter
Top Products
Upgrade from 3.0.x to 4.2
23
Note
How will you know whether you need to do this? If the upgrade output in the previous step
included a message like the following, then some custom content was found in your old file,
and you need to merge the two files:
warning: /etc/cloud.rpmsave/management/components.xml created as /etc/cloudstack/
management/components.xml.rpmnew
a. Make a backup copy of your previous version file. For example: (substitute the file name
components.xml, db.properties, or server.xml in these commands as needed)
# mv /etc/cloudstack/management/components.xml /etc/cloudstack/management/
components.xml-backup
b. Copy the *.rpmnew file to create a new file. For example:
# cp -ap /etc/cloudstack/management/components.xml.rpmnew /etc/cloudstack/management/
components.xml
c. Merge your changes from the backup file into the new file. For example:
# vi /etc/cloudstack/management/components.xml
13. Repeat steps 8 - 12 on each management server node.
14. Start the first Management Server. Do not start any other Management Server nodes yet.
# service cloudstack-management start
Wait until the databases are upgraded. Ensure that the database upgrade is complete. After
confirmation, start the other Management Servers one at a time by running the same command on
each node.
Note
Failing to restart the Management Server indicates a problem in the upgrade. Restarting the
Management Server without any issues indicates that the upgrade is successfully completed.
15. Start all Usage Servers (if they were running on your previous version). Perform this on each
Usage Server host.
# service cloudstack-usage start