Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cold cluster start always errors #54

Open
jamesonjlee opened this issue Nov 17, 2013 · 1 comment
Open

cold cluster start always errors #54

jamesonjlee opened this issue Nov 17, 2013 · 1 comment

Comments

@jamesonjlee
Copy link

start a cluster from the cold always results in this error:

Vagabond error encountered. Exiting: Requested name is not a valid node name: mongo_nodes

re-running the same command results in success.

From what I can tell, it looks like having to start the server and (re-running the configure) is altering the command from cluster into regular node.

here is the full output

vagrant@vagabond-lxc-host:~/chef-repo$ bundle exec vagabond cluster mongo_nodes
WARNING: Local chef server is not currently running!
Vagabond: Building cluster - mongo_nodes
Vagabond: Creating server
  -> CREATED!
  -> Bootstrapping chef-zero...
  -> COMPLETE
Auto uploading all assets to local Chef server...
Local chef server: Uploading roles
  -> UPLOADED ROLES
Local chef server: Uploading data bags
  -> UPLOADED DATA BAGS
Local chef server: Uploading environments
  -> UPLOADED ENVIRONMENTS
Local chef server: Uploading cookbooks
Cookbooks being uploaded via berks
  -> UPLOADED COOKBOOKS
  -> All assets uploaded!
Vagabond error encountered. Exiting: Requested name is not a valid node name: mongo_nodes
@chrisroberts
Copy link
Owner

Identified issue in chains building

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants