cloudstack-dev mailing list archives

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


Marcus Sorensen commented on CLOUDSTACK-1487:

This is happening because there is no EOF on the provided in the RPM. If
I simply open the default, save it, and close, everything works.

Am I good to just add a newline to this? It seems like it was maybe created by a program if
all I have to do is open it and save it to fix the issue, and if it was then it might be pointless
to change the original in the code?
> cloudstack-setup-agent fails to set on KVM host add
> --------------------------------------------------------------------------
>                 Key: CLOUDSTACK-1487
>                 URL:
>             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 -z 1 -p 1 -c 1 -g 7e59f3ee-6112-301e-a361-ee475c63215a
-a --pubNic=cloudbr1 --prvNic=cloudbr0 --guestNic=cloudbr0 output:CloudStack Agent setup is
> but in the /etc/cloudstack/agent/, 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:
> workers=5
> port=8250
> pod=1
> zone=1
> guid=7e59f3ee-6112-301e-a361-ee475c63215a
> cluster=1
> domr.scripts.dir=scripts/network/domr/kvm
> host=

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:

View raw message