[
https://issues.apache.org/jira/browse/CLOUDSTACK-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav reassigned CLOUDSTACK-1515:
---------------------------------------
Assignee: Hugo Trippaers (was: Rohit Yadav)
Assigning to Hugo. Looks like a packaging upgrade issue because we changed the
name from cloud- to cloudstack-*
The cloud.spec should obsolete old package name, this way upgrade using new rpm
artifacts should works. I'm not sure how rpms upgrade, will just yum upgrade
work?
Also, we don't use install.sh anymore, comment Hugo, Wido and others? If we
still want this, pl. assign to Pradeep he will have more idea on
packaging/installation using install.sh
> 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
> Assignee: Hugo Trippaers
> 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
