[Crowbar] client nodes stuck in "discovered"

Plaetinck, Dieter dieter at vimeo.com
Wed Jul 11 05:04:54 CDT 2012


Andi,
my mistake. should have realized this was correct behavior.  But why does it keep printing the messages to the console?
How about printing "Node is now in state discovered.  Ready to be allocated..." and printing those variables once?

Dieter

On Tue, 10 Jul 2012 20:53:31 +0200
"Andi_Abes at Dell.com" <Andi_Abes at Dell.com> wrote:

> Yup. They'll wait there until you allocate them or include them in some proposal.
> e.g. if you're trying to deploy openstack components, navigate to the Barclamps -> Openstack, and deploy the relevant components (mysql, keystone...)
> if you're going for swift, make sure to take a peek at [1] for pre-req's.
> 
> [1] https://github.com/dellcloudedge/crowbar/wiki/Swift--barclamp
> 
> 
> -----Original Message-----
> From: crowbar-bounces On Behalf Of Plaetinck, Dieter
> Sent: Tuesday, July 10, 2012 2:06 PM
> To: crowbar
> Subject: [Crowbar] client nodes stuck in "discovered"
> 
> Hi
> using openstack111219.iso
> installed admin node per
> https://github.com/dellcloudedge/crowbar/wiki/Running-Crowbar-in-VirtualBox-VMs
> created two openstack nodes per the same document.
> 
> their consoles show stuff like:
> (...)
> BMT_ROUTER=
> BMC_ADDRESS=192.168.124.163
> BMC_NETMASK=255.255.255.0
> HOSTNAME=<uuid>.crowbar.org
> NODE_STATE=false
> 
> and in the crowbar webUI they are stuck on "discovered"
> 
> Dieter
> 
> _______________________________________________
> Crowbar mailing list
> Crowbar at dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: https://github.com/dellcloudedge/crowbar/wiki



More information about the Crowbar mailing list