You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
start a cluster from the cold always results in this error:
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
The text was updated successfully, but these errors were encountered: