You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Pierre-Luc Dion (JIRA)" <ji...@apache.org> on 2014/05/22 04:13:38 UTC
[jira] [Assigned] (CLOUDSTACK-3381) Wrong instruction in CloudStack
release notes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Luc Dion reassigned CLOUDSTACK-3381:
-------------------------------------------
Assignee: Pierre-Luc Dion
> Wrong instruction in CloudStack release notes
> ---------------------------------------------
>
> Key: CLOUDSTACK-3381
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3381
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Doc
> Affects Versions: 4.1.0
> Environment: Link to particular documentation article:
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Release_Notes/upgrade-instructions.html
> Reporter: Aabd
> Assignee: Pierre-Luc Dion
> Labels: documentation
>
> The CloudStack upgrade instructions contains an error.
> At some point the reader is instructed to execute the command:
> nohup cloud-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > sysvm.log 2>&1 &
> This should be:
> nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -s -r > sysvm.log 2>&1 &
> * The "cloud-sysvmadm" script does not exist, this should be "cloudstack-sysvmadm".
> * The -c argument does not exist in the sysvmadm script. As a result of this of this, only the virtual router vm is restarted. A quick glance at the code of the sysvmadm scripts reveals that a reboot of the secondary storage vm and console proxy vm is initiated by the -s parameter.
--
This message was sent by Atlassian JIRA
(v6.2#6252)