cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1487) cloudstack-setup-agent fails to set private.network.device on KVM host add
Date Sat, 02 Mar 2013 02:03:12 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591209#comment-13591209
] 

Marcus Sorensen commented on CLOUDSTACK-1487:
---------------------------------------------

Note, if I delete /etc/cloudstack/agent/agent.properties while the agent is running, it gets
rewritten correctly, or if I manually run "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"
it gets written correctly. 

The issue only occurs when the management server attempts to first connect the host. It may
have something to do with the default agent.properties.
                
> 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
>            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

Mime
View raw message