Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A64AC0C5 for ; Thu, 7 Jun 2012 18:32:27 +0000 (UTC) Received: (qmail 71819 invoked by uid 500); 7 Jun 2012 18:32:27 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 71801 invoked by uid 500); 7 Jun 2012 18:32:27 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 71791 invoked by uid 99); 7 Jun 2012 18:32:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2012 18:32:27 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Edison.su@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2012 18:32:19 +0000 X-IronPort-AV: E=Sophos;i="4.75,732,1330923600"; d="scan'208";a="27254126" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Jun 2012 14:31:58 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Thu, 7 Jun 2012 11:31:57 -0700 From: Edison Su To: "cloudstack-users@incubator.apache.org" , 'sebastien goasguen' Date: Thu, 7 Jun 2012 11:31:57 -0700 Subject: RE: basic config gives "unable to add host" error Thread-Topic: basic config gives "unable to add host" error Thread-Index: Ac1ExhViquLCL28+TpKzhR36TEXHzAAFTJEg Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 > -----Original Message----- > From: sebastien goasguen [mailto:runseb@gmail.com] > Sent: Thursday, June 07, 2012 8:56 AM > To: cloudstack-users@incubator.apache.org > Subject: basic config gives "unable to add host" error >=20 > Hi, >=20 > I am trying to setup a basic zone with CS 3.0.1-1 > I have the mgt server running and I can access the GUI, I am bypassing > the wizard and going through "infrastructure" to setup the basic zone. > I have the storage setup via NFS and mounted properly. > I have the agent setup on a KVM host. iptables disabled for now. >=20 > When I finish the setup of the zone, it tries to add the host and > fails. the GUI says "Something went wrong, please correct the > following: Unable to add the host" > Looking into /var/log/cloud/management/management-server.log there is > not much info: >=20 > 2012-06-07 11:32:20,413 WARN [cloud.resource.ResourceManagerImpl] > (catalina-exec-7:null) Unable to find the server resources at > http:// >=20 > and before that: >=20 > 2012-06-07 11:27:19,391 DEBUG [utils.ssh.SSHCmdHelper] > (catalina-exec-7:null) cloud-setup-agent -m -z 1 -p 1 > -c 1 -g 6330f45e- > 516e-3295-8cd7-029e41d8cbea -a --pubNic=3Dcloudbr0 --prvNic=3Dcloudbr0 > --guestNic=3Dcloudbr0 output:[OK] > Restore Network ... to add your network configuration into > /etc/sysconfig/network-scripts at first > Try to restore your system: >=20 > Checking the agent, the cloud-agent service is actually not running. > The only info in the setup log is that cloudbr0 does not exist. >=20 > Does this mean that we need to create the bridges by hand on the agent > ? I did not see much info about this. I have a single br0 bridge > currently. Can you check /var/log/cloud/setupAgent.log on your kvm host? Or manually execute " cloud-setup-agent -m -z 1 -p 1 -c 1 = -g 6330f45e-516e-3295-8cd7-029e41d8cbea -a --pubNic=3Dcloudbr0 --prvNic=3Dc= loudbr0 --guestNic=3Dcloudbr0" on your kvm host? What's the outpout? Usually, cloud-setup-agent failed, due to hostname is not configured proper= ly. Check "hostname --fqdn" >=20 > Do we need to edit /etc/cloud/agent/agent.properties by hand before > adding the host via the GUI ? >=20 > Thanks for the help, >=20 > -- > --- > Sebastien Goasguen