[
https://issues.apache.org/jira/browse/CLOUDSTACK-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694510#comment-13694510
]
Jessica Tomechak commented on CLOUDSTACK-3138:
----------------------------------------------
More doc flaws found by a user upgrading from 2.2.14 to 4.1.0, and reported on
the mailing list (http://markmail.org/message/bfkbdwuy5qo34tsw)
Although this user was on another upgrade path, it seems likely these errors
affect all upgrade instructions, and all could be fixed at the same time. If
not, please feel free to spawn a separate bug for this set of comments.
This user suggests the following changes to upgrade instructions in docs:
1.
Automatically take a mysqldump prior to the database upgrade.
If it fails, revert to the dump and log.
This would be faster to diag / fix and leave the db in a usable state. I know
you should take a db backup first anyway, but this would be cleaner.
2.
The vhd-util download isn't on the upgrade guides.
3.
The upgrade guide for 4.1.0 incorrectly list the repos in the examples and 4.0
4.
The upgrade guide gets cloud and Cloudstack folders wrong all the time
5.
I had an issue with a SR-BACKEND failure that ended up being a corrupt vhd.
This was throwing all kinds of errors with the solution. I know this is a
Xenserver issue, just might help others with SR-BACKEND failures.
6.
4.0.2 Ubuntu repo install is missing the cloud-setup-encryption binaries.
7.
Can't upgrade from 2.2.14 to 4.0.2 due to a know bug that is listed as solved
due to 4.1.0 being released. This doesn't help when you can't get 4.1.0 to
work. ( bug is for the database conversion missing 4.02 schema files ). If the
upgrades don't work, can we put that on the upgrade guide / release notes?
> Flaws in upgrade documentation from 3.0.2 -> 4.1.0
> --------------------------------------------------
>
> Key: CLOUDSTACK-3138
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3138
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.1.0
> Reporter: Joe Brockmeier
> Priority: Critical
> Labels: documentation
> Fix For: 4.1.1
>
>
> Reported on the mailing list (http://markmail.org/message/ussthbb6sx6kjm2j)
> there are many errors in release notes for upgrade form CS 3.0.2 to 4.0.1.
> Here are just a few, from the top of my head. I suggest you correct them.
> 1. Location of config files is not at /etc/cloud/ but rather at
> /etc/cloudstack now.
> 2. components.xml is nowhere to be found in /etc/cloudstack
> 3. server.xml generation failed, because i had enabled ssl in it. It
> required me to generate them from scratch.
> 4. There were no instructions for enabling https, anywhere. I had to fix
> server.xml and tomcat6.xml to use my certificate.
> 5. cloud-sysvmadm is nonexistent. I think there is cloudstack-sys.. Also
> switches are wrong.
> 6. Python and bash scripts are now located
> /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/
> instead
> of /usr/lib64/cloud/common/ scripts/vm/hypervisor/
> xenserver/xenserver60/ as documentation would tell you.
> 7. for pbd in `xe pbd-list currently-attached=false| grep ^uuid | awk
> '{print $NF}'`; do xe pbd-plug uuid=$pbd ; doesn't work:
> [root@x1 ~]# for pbd in `xe pbd-list currently-attached=false| grep
> ^uuid | awk '{print $NF}'`; do xe pbd-plug uuid=$pbd
> >
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
