You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2013/03/06 09:16:13 UTC
[jira] [Commented] (CLOUDSTACK-1515) None of the cloudstack packges
are marked for upgrade when tried to upgrade from.4.0/4.0.1 to 4.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594486#comment-13594486 ]
Rohit Yadav commented on CLOUDSTACK-1515:
-----------------------------------------
This looks like a packaging issue, maybe because we changed names from cloud- to cloudstack-, I'll add an upgrade db path from 4.0.1 to latest.
> None of the cloudstack packges are marked for upgrade when tried to upgrade from.4.0/4.0.1 to 4.1
> --------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1515
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1515
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Install and Setup
> Affects Versions: 4.0.0
> Reporter: Sailaja Mada
> Priority: Blocker
> Fix For: 4.1.0
>
>
> Setup :
> a) 4.0 Advanced Networking setup [Rhel63] with KVM 6.3 host
> b) 4.0.1 Advanced Networking setup [Rhel63] with KVM 6.3 host
> Tried two paths a) 4.0 to 4.1 b) 4.0.1 to 4.1 [Rhel63]. None of the packages are marked for upgrade.
> 4.0 build : CloudStack-non-OSS-140.tar
> 4.1 : CloudStack-non-OSS-4.1-65-rhel6.3.tar.gz
> [root@asfkvm63 CloudStack-non-OSS-4.1-65-rhel6.3]# sh install.sh Setting up the temporary repository...
> Cleaning Yum cache...
> Loaded plugins: product-id, security, subscription-manager Updating certificate-based repositories.
> Unable to read consumer identity
> Cleaning repos: cloud-temp rhel
> 1 metadata files removed
> Welcome to the Apache CloudStack (Incubating) Installer. What would you like to do?
> M) Install the Management Server
> A) Install the Agent
> S) Install the Usage Monitor
> E) Remove the MySQL server (will not remove the MySQL databases)
> Q) Quit
> > Q
> Done
--
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