Hello, I'm trying an experimental crowbar setup using VMs, as a learning exercise and i'm stuck with a curious problem that i can't find an explanation.
The first time i installed crowbar (i'm using virtual box) all went just fine. I made a "infrastructure" with 5 VMs, one being the admin node and the rest i used to deploy a multi-node openstack install, which also worked just fine. After messing around with crowbar and openstack config files, i decided to start over from scratch, so i erased all the VMs i used and created new ones, with new disks but the rest of the configurations (CPUs, memory, networks, etc) are just like before. The admin node installation seems to be ok, but when i try to add a new node it boots what seems to be a CentOS system and it is not recognized by the crowbar dashboard as an available node. When it worked at the first time i installed, the nodes i added were in some sort of "waiting status", repeating a message like this: BMC_ROUTER= BMC_ADDRESS=192.168.124.163 BMC_NETMASK=255.255.255.0 HOSTNAME=d08-00-27-cf-03-f6.crowbar.org NODE_STATE=false The above no longer happens. Does anyone knows why are the nodes booting CentOS instead of waiting for allocation? Luis Carlos Jersak jer...@gmail.com
_______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
