[
https://issues.apache.org/jira/browse/CLOUDSTACK-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Nalley updated CLOUDSTACK-1936:
-------------------------------------
Priority: Critical (was: Major)
> On CentOS, after a upgrade from 4.0.1 to 4.1 on a cloud node (cloud-agent),
> the new cloustack-agent isn't add as a service (chkconfig)
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1936
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1936
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.1.0
> Reporter: Milamber
> Priority: Critical
> Labels: upgrade
>
> On CentOS 6.4, after a upgrade from 4.0.1 to 4.1 on a cloud node (server with
> cloud-agent), the new cloudstack-agent isn't add as a service
> chkconfig --list without cloustack-agent, but it's present into /etc/init.d/
> 4.1-SNAPSHOT (2013/04/04)
--
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
