[
https://issues.apache.org/jira/browse/CLOUDSTACK-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Sorensen resolved CLOUDSTACK-1487.
-----------------------------------------
Resolution: Fixed
Assignee: Marcus Sorensen
Fixed via adding EOF newline in agent.properties. I'm closing this, but if
anyone knows about how this might have happened or if it would happen again
please follow up.
> cloudstack-setup-agent fails to set private.network.device on KVM host add
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1487
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1487
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup, KVM
> Affects Versions: 4.1.0
> Environment: CentOS 6.3, KVM
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Priority: Blocker
> Fix For: 4.1.0
>
>
> When setting up zone and adding a host, the management server connects to the
> host and runs cloudstack-setup-agent. Per the management server log:
> "cloudstack-setup-agent -m 172.17.10.10 -z 1 -p 1 -c 1 -g
> 7e59f3ee-6112-301e-a361-ee475c63215a -a --pubNic=cloudbr1 --prvNic=cloudbr0
> --guestNic=cloudbr0 output:CloudStack Agent setup is done!"
> but in the /etc/cloudstack/agent/agent.properties, private.network.device is
> not set. This leaves people with a broken install with all sorts of symptoms
> that one might create bug reports for. I'm not familiar enough with python or
> all of the included cloudstack libraries to track it down.
> see resulting file:
> guest.network.device=cloudbr0
> workers=5
> port=8250
> resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
> pod=1
> zone=1
> guid=7e59f3ee-6112-301e-a361-ee475c63215a
> cluster=1
> public.network.device=cloudbr1
> local.storage.uuid=d6818058-ccad-4d8e-8473-7f7a0cfe3b7c
> domr.scripts.dir=scripts/network/domr/kvm
> host=172.17.10.10
> LibvirtComputingResource.id=1
--
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
