Hmm, when you say binaries are you talking about RPMs? Is this centos? I've tested 4.1 rpms and we copy the old agent.properties, everything started up fine. I'll take a look. More info on your test setup is appreciated. On Mar 28, 2013 7:43 PM, "Sangeetha Hariharan (JIRA)" <j...@apache.org> wrote:
> Sangeetha Hariharan created CLOUDSTACK-1844: > ----------------------------------------------- > > Summary: Upgrade 4.0 -> 4.1 - KVM host agent.properties is > not restored as part of upgrading the binaries from 4.0 to 4.1. > Key: CLOUDSTACK-1844 > URL: > https://issues.apache.org/jira/browse/CLOUDSTACK-1844 > Project: CloudStack > Issue Type: Bug > Security Level: Public (Anyone can view this level - this is the > default.) > Components: Management Server > Affects Versions: 4.1.0 > Environment: Upgrade from 4.0 -> 41. > Reporter: Sangeetha Hariharan > Priority: Blocker > Fix For: 4.1.0 > > > Upgrade 4.0 -> 4.1 - KVM host agent.properties is not restored as part of > upgrading the binaries from 4.0 to 4.1. > > Install 4.1 binaries > Configure Advance Zone with KVM hosts. > Deploy few Vms. > > Stop management server. > Upgrade to 4.1 binaries. > > Start management server. > > From KVM host , > Stop cloud-agent. > Upgrade to 4.1 binaries. > > Start cloud-agent. > > Agent fails to start because it refers to the > /etc/cloudstack/agent/agent.properties which is NOT restored from the > original agent.properties. > > Following errors seen in the agent.log: > > 2013-03-28 19:46:44,294 INFO [cloud.agent.AgentShell] (main:null) Agent > started > 2013-03-28 19:46:44,296 INFO [cloud.agent.AgentShell] (main:null) > Implementation Version is 4.1.0-SNAPSHOT > 2013-03-28 19:46:44,298 INFO [cloud.agent.AgentShell] (main:null) > agent.properties found at /etc/cloudstack/agent/agent.properties > 2013-03-28 19:46:44,299 INFO [cloud.agent.AgentShell] (main:null) > Defaulting to using properties file for storage > 2013-03-28 19:46:44,301 INFO [cloud.agent.AgentShell] (main:null) > Defaulting to the constant time backoff algorithm > 2013-03-28 19:46:44,404 INFO [cloud.agent.Agent] (main:null) id is > 2013-03-28 19:46:44,466 ERROR [cloud.resource.ServerResourceBase] > (main:null) Nics are not configured! > 2013-03-28 19:46:44,475 INFO [cloud.resource.ServerResourceBase] > (main:null) Designating private to be nic cloudbr0 > 2013-03-28 19:46:44,489 INFO > [resource.virtualnetwork.VirtualRoutingResource] (main:null) > VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm > 2013-03-28 19:46:45,370 ERROR [cloud.agent.AgentShell] (main:null) Unable > to start agent: Failed to get private nic name > > > After restoring to the original agent.properties , agent is able to start > successfully. > > > > -- > 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 >
