vagrant-parallels 0.1.3 → 0.2.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (17) hide show
  1. data/README.md +6 -5
  2. data/Rakefile +3 -0
  3. data/config/i18n-tasks.yml.erb +13 -0
  4. data/lib/vagrant-parallels/action/import.rb +1 -1
  5. data/lib/vagrant-parallels/action/{is_saved.rb → is_suspended.rb} +1 -1
  6. data/lib/vagrant-parallels/action/message_already_running.rb +1 -1
  7. data/lib/vagrant-parallels/action/resume.rb +1 -4
  8. data/lib/vagrant-parallels/action.rb +7 -15
  9. data/lib/vagrant-parallels/config.rb +3 -4
  10. data/lib/vagrant-parallels/plugin.rb +1 -1
  11. data/lib/vagrant-parallels/provider.rb +1 -1
  12. data/lib/vagrant-parallels/version.rb +1 -1
  13. data/locales/en.yml +12 -1056
  14. data/test/unit/locales/locales_test.rb +14 -0
  15. data/vagrant-parallels.gemspec +1 -0
  16. metadata +22 -5
  17. data/lib/vagrant-parallels/action/is_paused.rb +0 -21
data/locales/en.yml CHANGED
@@ -1,521 +1,9 @@
1
1
  en:
2
2
  vagrant_parallels:
3
- cfengine_bootstrapping: |-
4
- Bootstrapping CFEngine with policy server: %{policy_server}...
5
- cfengine_bootstrapping_policy_hub: |-
6
- Performing additional bootstrap for policy hubs...
7
- cfengine_cant_autodetect_ip: |-
8
- Vagrant was unable to automatically detect the IP address of the
9
- running machine to use as the policy server address. Please specify
10
- the policy server address manually, or verify that the networks are
11
- configured properly internally.
12
- cfengine_cant_detect: |-
13
- Vagrant doesn't support detecting whether CFEngine is installed
14
- for the guest OS running in the machine. Vagrant will assume it is
15
- installed and attempt to continue.
16
- cfengine_detected_ip: |-
17
- Detected policy server IP address: %{address}...
18
- cfengine_installing: |-
19
- Installing CFEngine onto machine...
20
- cfengine_installing_files_path: |-
21
- Copying the 'files_path' files...
22
- cfengine_no_bootstrap: |-
23
- CFEngine doesn't require bootstrap. Not bootstrapping.
24
- cfengine_single_run: |-
25
- CFEngine running in "single run" mode. Will execute one file.
26
- cfengine_single_run_execute: |-
27
- Executing run file for CFEngine...
28
- chef_run_list_empty: |-
29
- Warning: Chef solo run list is empty. This may not be what you want.
30
-
31
- cfengine_config:
32
- classes_array: |-
33
- The 'classes' configuration must be an array.
34
- files_path_not_directory: |-
35
- The 'files_path' must point to a valid directory.
36
- invalid_mode: |-
37
- The mode must be 'bootstrap' or 'single_run'
38
- policy_server_address: |-
39
- The policy server address must be set for bootstrapping.
40
- run_file_not_found: |-
41
- The 'run_file' specified could not be found.
42
-
43
- general:
44
- batch_unexpected_error: |-
45
- An unexpected error ocurred when executing the action on the
46
- '%{machine}' machine. Please report this as a bug:
47
-
48
- %{message}
49
- batch_vagrant_error: |-
50
- An error occurred while executing the action on the '%{machine}'
51
- machine. Please handle this error then try again:
52
-
53
- %{message}
54
- config_upgrade_messages: |-
55
- There were warnings and/or errors while loading your Vagrantfile.
56
- Your Vagrantfile was written for an earlier version of Vagrant,
57
- and while Vagrant does the best it can to remain backwards
58
- compatible, there are some cases where things have changed
59
- significantly enough to warrant a message. These messages are
60
- shown below.
61
-
62
- %{output}
63
- moving_home_dir: "Moving old Vagrant home directory to new location: %{directory}"
64
- home_dir_migration_failed: |-
65
- Both an old and new Vagrant home directory exist. Only the new one will
66
- be used. Please merge the old directory into the new directory if you'd
67
- like to use the old data as well.
68
-
69
- Old: %{old}
70
- New: %{new}
71
- in_bundler: |-
72
- You appear to be running Vagrant in a Bundler environment. Because
73
- Vagrant should be run within installers (outside of Bundler), Vagrant
74
- will assume that you're developing plugins and will change its behavior
75
- in certain ways to better assist plugin development.
76
- not_in_installer: |-
77
- You appear to be running Vagrant outside of the official installers.
78
- Note that the installers are what ensure that Vagrant has all required
79
- dependencies, and Vagrant assumes that these dependencies exist. By
80
- running outside of the installer environment, Vagrant may not function
81
- properly. To remove this warning, install Vagrant using one of the
82
- official packages from vagrantup.com.
83
- upgraded_v1_dotfile: |-
84
- A Vagrant 1.0.x state file was found for this environment. Vagrant has
85
- gone ahead and auto-upgraded this to the latest format. Everything
86
- should continue working as normal. Beware, however, that older versions
87
- of Vagrant may no longer be used with this environment.
88
-
89
- However, in case anything went wrong, the old dotfile was backed up
90
- to the location below. If everything is okay, it is safe to remove
91
- this backup.
92
-
93
- Backup: %{backup_path}
94
-
95
3
  #-------------------------------------------------------------------------------
96
4
  # Translations for exception classes
97
5
  #-------------------------------------------------------------------------------
98
6
  errors:
99
- active_machine_with_different_provider: |-
100
- An active machine was found with a different provider. Vagrant
101
- currently allows each machine to be brought up with only a single
102
- provider at a time. A future version will remove this limitation.
103
- Until then, please destroy the existing machine to up with a new
104
- provider.
105
-
106
- Machine name: %{name}
107
- Active provider: %{active_provider}
108
- Requested provider: %{requested_provider}
109
- ansible_playbook_app_not_found: |-
110
- The "ansible-playbook" program could not be found! Please verify
111
- that "ansible-playbook" is available on the PATH of your host
112
- system, and try again.
113
-
114
- If you haven't installed Ansible yet, please install Ansible
115
- on your system. Vagrant can't do this for you in a safe, automated
116
- way. Please see ansible.cc for more info.
117
- base_vm_not_found: The base VM with the name '%{name}' was not found.
118
- batch_multi_error: |-
119
- An error occurred while executing multiple actions in parallel.
120
- Any errors that occurred are shown below.
121
-
122
- %{message}
123
- box_config_changing_box: |-
124
- While loading the Vagrantfile, the provider override specified
125
- a new box. This box, in turn, specified a different box. This isn't
126
- allowed, as it could lead to infinite recursion of Vagrant configuration
127
- loading. Please fix this.
128
- box_metadata_file_not_found: |-
129
- The "metadata.json" file for the box '%{name}' was not found.
130
- Boxes require this file in order for Vagrant to determine the
131
- provider it was made for. If you made the box, please add a
132
- "metadata.json" file to it. If someone else made the box, please
133
- notify the box creator that the box is corrupt. Documentation for
134
- box file format can be found at the URL below:
135
-
136
- http://docs.vagrantup.com/v2/boxes/format.html
137
- box_not_found: Box '%{name}' could not be found.
138
- box_provider_doesnt_match: |-
139
- The box you attempted to add doesn't match the provider you specified.
140
-
141
- Provider expected: %{expected}
142
- Provider of box: %{actual}
143
- box_upgrade_required: |-
144
- The box '%{name}' is still stored on disk in the Vagrant 1.0.x
145
- format. This box must be upgraded in order to work properly with
146
- this version of Vagrant.
147
- cfengine_bootstrap_failed: |-
148
- Failed to bootstrap CFEngine. Please see the output above to
149
- see what went wrong and address the issue.
150
- cfengine_install_failed: |-
151
- After installing CFEngine, Vagrant still can't detect a proper
152
- CFEngine installation. Please verify that CFEngine was properly
153
- installed, as the installation may have failed.
154
- cfengine_not_installed: |-
155
- CFEngine appears to not be installed on the guest machine. Vagrant
156
- can attempt to install CFEngine for you if you set the "install"
157
- setting to "true", but this setting was not set. Please install
158
- CFEngine on the guest machine or enable the "install" setting for
159
- Vagrant to attempt to install it for you.
160
- cli_invalid_options: |-
161
- An invalid option was specified. The help for this command
162
- is available below.
163
-
164
- %{help}
165
- cli_invalid_usage: |-
166
- This command was not invoked properly. The help for this command is
167
- available below.
168
-
169
- %{help}
170
- command_unavailable: |-
171
- The executable '%(file)' Vagrant is trying to run was not
172
- found in the PATH variable. This is an error. Please verify
173
- this software is installed and on the path.
174
- command_unavailable_windows: |-
175
- The executable '%(file)' Vagrant is trying to run was not
176
- found in the %PATH% variable. This is an error. Please verify
177
- this software is installed and on the path.
178
- config_invalid: |-
179
- There are errors in the configuration of this machine. Please fix
180
- the following errors and try again:
181
-
182
- %{errors}
183
- config_upgrade_errors: |-
184
- Because there were errors upgrading your Vagrantfiles, Vagrant
185
- can no longer continue. Please fix the errors above and try again.
186
- copy_private_key_failed: |-
187
- Vagrant failed to copy the default insecure private key into your
188
- home directory. This is usually caused by a permissions error.
189
- Please make sure the permissions of the source is readable and
190
- the destination is writable.
191
-
192
- Source: %{source}
193
- Destination: %{destination}
194
- destroy_requires_force: |-
195
- Destroy doesn't have a TTY to ask for confirmation. Please pass the
196
- `--force` flag to force a destroy, otherwise attach a TTY so that
197
- the destroy can be confirmed.
198
- dotfile_is_directory: |-
199
- The local file Vagrant uses to store data ".vagrant" already exists
200
- and is a directory! If you are in your home directory, then please run
201
- this command in another directory. If you aren't in a home directory,
202
- then please rename ".vagrant" to something else, or configure Vagrant
203
- to use another filename by modifying `config.vagrant.dotfile_name`.
204
- dotfile_upgrade_json_error: |-
205
- A Vagrant 1.0.x local state file was found. Vagrant is able to upgrade
206
- this to the latest format automatically, however various checks are
207
- put in place to verify data isn't incorrectly deleted. In this case,
208
- the old state file was not valid JSON. Vagrant 1.0.x would store state
209
- as valid JSON, meaning that this file was probably tampered with or
210
- manually edited. Vagrant's auto-upgrade process cannot continue in this
211
- case.
212
-
213
- In most cases, this can be resolve by simply removing the state file.
214
- Note however though that if Vagrant was previously managing virtual
215
- machines, they may be left in an "orphan" state. That is, if they are
216
- running or exist, they'll have to manually be removed.
217
-
218
- If you're unsure what to do, ask the Vagrant mailing list or contact
219
- support.
220
-
221
- State file path: %{state_file}
222
- downloader_error: |-
223
- An error occurred while downloading the remote file. The error
224
- message, if any, is reproduced below. Please fix this error and try
225
- again.
226
-
227
- %{message}
228
- downloader_interrupted: |-
229
- The download was interrupted by an external signal. It did not
230
- complete.
231
- environment_locked: |-
232
- An instance of Vagrant is already running. Only one instance of Vagrant
233
- may run at any given time to avoid problems with Parallels Desktop inconsistencies
234
- occurring. Please wait for the other instance of Vagrant to end and then
235
- try again.
236
- forward_port_adapter_not_found: |-
237
- The adapter to attach a forwarded port to was not found. Please
238
- verify that the given adapter is setup on the machine as a NAT
239
- interface.
240
-
241
- Host port: %{host}
242
- Guest port: %{guest}
243
- Adapter: %{adapter}
244
- gem_command_in_bundler: |-
245
- You cannot run the `vagrant plugin` command while in a bundler environment.
246
- This should generally never happen unless Vagrant is installed outside
247
- of the official installers or another gem is wrongly attempting to
248
- use Vagrant internals directly. Please properly install Vagrant to
249
- fix this. If this error persists, please contact support.
250
- guest_capability_invalid: |-
251
- The registered guest capability '%{cap}' for the
252
- detected guest OS '%{guest}' is invalid. The capability does
253
- not implement the proper method. This is a bug with Vagrant or the
254
- plugin that implements this capability. Please report a bug.
255
- guest_capability_not_found: |-
256
- Vagrant attempted to execute the capability '%{cap}'
257
- on the detect guest OS '%{guest}', but the guest doesn't
258
- support that capability. This capability is required for your
259
- configuration of Vagrant. Please either reconfigure Vagrant to
260
- avoid this capability or fix the issue by creating the capability.
261
- guest_not_detected: |-
262
- The guest operating system of the machine could not be detected!
263
- Vagrant requires this knowledge to perform specific tasks such
264
- as mounting shared folders and configuring networks. Please add
265
- the ability to detect this guest operating system to Vagrant
266
- by creating a plugin or reporting a bug.
267
- home_dir_not_accessible: |-
268
- The home directory you specified is not accessible. The home
269
- directory that Vagrant uses must be both readable and writable.
270
-
271
- You specified: %{home_path}
272
- interrupted: |-
273
- Vagrant exited after cleanup due to external interrupt.
274
- local_data_dir_not_accessible: |-
275
- The directory Vagrant will use to store local environment-specific
276
- state is not accessible. The directory specified as the local data
277
- directory must be both readable and writable for the user that is
278
- running Vagrant.
279
-
280
- Local data directory: %{local_data_path}
281
- linux_mount_failed: |-
282
- Failed to mount folders in Linux guest. This is usually beacuse
283
- the "prl_fs" file system is not available. Please verify that
284
- the Parallels Tools are properly installed in the guest and
285
- can work properly. The command attempted was:
286
-
287
- %{command}
288
- linux_nfs_mount_failed: |-
289
- Mounting NFS shared folders failed. This is most often caused by the NFS
290
- client software not being installed on the guest machine. Please verify
291
- that the NFS client software is properly installed, and consult any resources
292
- specific to the linux distro you're using for more information on how to
293
- do this.
294
- linux_shell_expand_failed: |-
295
- Vagrant failed to determine the shell expansion of the guest path
296
- for one of your shared folders. This is an extremely rare error case
297
- and most likely indicates an unusual configuration of the guest system.
298
- Please report a bug with your Vagrantfile.
299
- machine_guest_not_ready: |-
300
- Guest-specific operations were attempted on a machine that is not
301
- ready for guest communication. This should not happen and a bug
302
- should be reported.
303
- machine_not_found: |-
304
- The machine with the name '%{name}' was not found configured for
305
- this Vagrant environment.
306
- machine_state_invalid: |-
307
- An internal error has occurred! The provider of the machine you're
308
- trying to work with reported an invalid state. This is a bug with
309
- the provider you're using, and not with Vagrant itself or with
310
- any configuration you may have done. Please report this bug to
311
- the proper location.
312
- multi_vm_required: |-
313
- A multi-vm environment is required for name specification to this command.
314
- multi_vm_target_required: |-
315
- This command requires a specific VM name to target in a multi-VM environment.
316
- nfs_no_guest_ip: |-
317
- No guest IP was given to the Vagrant core NFS helper. This is an
318
- internal error that should be reported as a bug.
319
- nfs_no_host_ip: |-
320
- No host IP was given to the Vagrant core NFS helper. This is
321
- an internal error that should be reported as a bug.
322
- nfs_no_hostonly_network: |-
323
- NFS requires a host-only network with a static IP to be created.
324
- Please add a host-only network with a static IP to the machine
325
- for NFS to work.
326
- no_env: |-
327
- A Vagrant environment is required to run this command. Run `vagrant init`
328
- to set one up in this directory, or change to a directory with a
329
- Vagrantfile and try again.
330
- plugin_gem_error: |-
331
- An error occurred within RubyGems, the underlying system used to
332
- manage Vagrant plugins. The output of the errors are shown below:
333
-
334
- %{output}
335
- plugin_install_bad_entry_point: |-
336
- Attempting to load the plugin '%{name}' failed, because
337
- the entry point doesn't exist. The entry point attempted was
338
- '%{entry_point}'. If this is not correct, please manually
339
- specify an `--entry-point` when installing the plugin.
340
- plugin_install_license_not_found: |-
341
- The license file to install could not be found. Please verify
342
- the path you gave is correct. The path to the license file given
343
- was: '%{path}'
344
- plugin_install_not_found: |-
345
- The plugin '%{name}' could not be found in local or remote
346
- repositories. Please check the name of the plugin and try again.
347
- plugin_load_error: |-
348
- The plugin "%{plugin}" could not be found. Please make sure that it is
349
- properly installed via `vagrant plugin`. Note that plugins made for
350
- Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
351
- continue to show when you use `plugin install` with a 1.0.x plugin.
352
- plugin_load_failed: |-
353
- Failed to load the "%{plugin}" plugin. View logs for more details.
354
- plugin_load_failed_with_output: |-
355
- Failed to load the "%{plugin}" plugin. The output from loading
356
- the plugin is shown below. View the logs for complete details.
357
-
358
- stdout: %{stdout}
359
-
360
- stderr: %{stderr}
361
- plugin_not_found: |-
362
- The plugin '%{name}' could not be found. Please install this plugin
363
- prior to attempting to do anything with it.
364
- port_collision_resume: |-
365
- This VM cannot be resumed, because the forwarded ports would collide
366
- with a running program (it could be another virtual machine). Normally,
367
- Vagrant will attempt to fix this for you but Parallels Desktop only allows
368
- forwarded ports to change if the VM is powered off. Therefore, please
369
- reload your VM or stop the other program to continue.
370
- provider_not_found: |-
371
- The provider '%{provider}' could not be found, but was requested to
372
- back the machine '%{machine}'. Please use a provider that exists.
373
- scp_permission_denied: |-
374
- Failed to upload a file to the guest VM via SCP due to a permissions
375
- error. This is normally because the user running Vagrant doesn't have
376
- read permission on the file. Please set proper permissions on the file:
377
-
378
- %{path}
379
- scp_unavailable: |-
380
- SSH server on the guest doesn't support SCP. Please install the necessary
381
- software to enable SCP on your guest operating system.
382
- shared_folder_create_failed: |-
383
- Failed to create the following shared folder on the host system. This is
384
- usually because Vagrant does not have sufficient permissions to create
385
- the folder.
386
-
387
- %{path}
388
-
389
- Please create the folder manually or specify another path to share.
390
- ssh_authentication_failed: |-
391
- SSH authentication failed! This is typically caused by the public/private
392
- keypair for the SSH user not being properly set on the guest VM. Please
393
- verify that the guest VM is setup with the proper public key, and that
394
- the private key path for Vagrant is setup properly as well.
395
- ssh_bad_exit_status: |-
396
- The following SSH command responded with a non-zero exit status.
397
- Vagrant assumes that this means the command failed!
398
-
399
- %{command}
400
- ssh_connect_eacces: |-
401
- SSH is getting permission denied errors when attempting to connect
402
- to the IP for SSH. This is usually caused by network rules and not being
403
- able to connect to the specified IP. Please try changing the IP on
404
- which the guest machine binds to for SSH.
405
- ssh_connection_refused: |-
406
- SSH connection was refused! This usually happens if the VM failed to
407
- boot properly. Some steps to try to fix this: First, try reloading your
408
- VM with `vagrant reload`, since a simple restart sometimes fixes things.
409
- If that doesn't work, destroy your VM and recreate it with a `vagrant destroy`
410
- followed by a `vagrant up`. If that doesn't work, contact a Vagrant
411
- maintainer (support channels listed on the website) for more assistance.
412
- ssh_connection_reset: |-
413
- SSH connection was reset! This usually happens when the machine is
414
- taking too long to reboot. First, try reloading your machine with
415
- `vagrant reload`, since a simple restart sometimes fixes things.
416
- If that doesn't work, destroy your machine and recreate it with
417
- a `vagrant destroy` followed by a `1vagrant up`. If that doesn't work,
418
- contact support.
419
- ssh_connection_timeout: |-
420
- Vagrant timed out while attempting to connect via SSH. This usually
421
- means that the VM booted, but there are issues with the SSH configuration
422
- or network connectivity issues. Please try to `vagrant reload` or
423
- `vagrant up` again.
424
- ssh_disconnected: |-
425
- The SSH connection was unexpectedly closed by the remote end. This
426
- usually indicates that SSH within the guest machine was unable to
427
- properly start up. Please boot the VM in GUI mode to check whether
428
- it is booting properly.
429
- ssh_host_down: |-
430
- While attempting to connect with SSH, a "host is down" (EHOSTDOWN)
431
- error was received. Please verify your SSH settings are correct
432
- and try again.
433
- ssh_is_putty_link: |-
434
- The `ssh` executable found in the PATH is a PuTTY Link SSH client.
435
- Vagrant is only compatible with OpenSSH SSH clients. Please install
436
- an OpenSSH SSH client or manually SSH in using your existing client
437
- using the information below.
438
-
439
- Host: %{host}
440
- Port: %{port}
441
- Username: %{username}
442
- Private key: %{key_path}
443
- ssh_key_bad_owner: |-
444
- The private key to connect to the machine via SSH must be owned
445
- by the user running Vagrant. This is a strict requirement from
446
- SSH itself. Please fix the following key to be owned by the user
447
- running Vagrant:
448
-
449
- %{key_path}
450
- ssh_key_bad_permissions: |-
451
- The private key to connect to this box via SSH has invalid permissions
452
- set on it. The permissions of the private key should be set to 0600, otherwise SSH will
453
- ignore the key. Vagrant tried to do this automatically for you but failed. Please set the
454
- permissions on the following file to 0600 and then try running this command again:
455
-
456
- %{key_path}
457
- ssh_key_type_not_supported: |-
458
- The private key you're attempting to use with this Vagrant box uses
459
- an unsupported encryption type. The SSH library Vagrant uses does not support
460
- this key type. Please use `ssh-rsa` or `ssh-dss` instead. Note that
461
- sometimes keys in your ssh-agent can interfere with this as well,
462
- so verify the keys are valid there in addition to standard
463
- file paths.
464
- ssh_not_ready: |-
465
- The provider for this Vagrant-managed machine is reporting that it
466
- is not yet ready for SSH. Depending on your provider this can carry
467
- different meanings. Make sure your machine is created and running and
468
- try again. Additionally, check the output of `vagrant status` to verify
469
- that the machine is in the state that you expect. If you continue to
470
- get this error message, please view the documentation for the provider
471
- you're using.
472
- ssh_port_not_detected: |-
473
- Vagrant couldn't determine the SSH port for your VM! Vagrant attempts to
474
- automatically find a forwarded port that matches your `config.ssh.guest_port`
475
- (default: 22) value and uses this for SSH. Alternatively, if `config.ssh.port`
476
- is set, it will use this.
477
-
478
- However, in this case Vagrant was unable to find a forwarded port that matches
479
- the guest port and `config.ssh.port` is not set!
480
-
481
- Please make sure that you have a forwarded port that goes to the configured
482
- guest port value, or specify an explicit SSH port with `config.ssh.port`.
483
- ssh_unavailable: "`ssh` binary could not be found. Is an SSH client installed?"
484
- ssh_unavailable_windows: |-
485
- `ssh` executable not found in any directories in the %PATH% variable. Is an
486
- SSH client installed? Try installing Cygwin, MinGW or Git, all of which
487
- contain an SSH client. Or use the PuTTY SSH client with the following
488
- authentication information shown below:
489
-
490
- Host: %{host}
491
- Port: %{port}
492
- Username: %{username}
493
- Private key: %{key_path}
494
- ui_expects_tty: |-
495
- Vagrant is attempting to interface with the UI in a way that requires
496
- a TTY. Most actions in Vagrant that require a TTY have configuration
497
- switches to disable this requirement. Please do that or run Vagrant
498
- with TTY.
499
- unimplemented_provider_action: |-
500
- Vagrant attempted to call the action '%{action}' on the provider
501
- '%{provider}', but this provider doesn't support this action. This
502
- is probably a bug in either the provider or the plugin calling this
503
- action, and should be reported.
504
- vagrantfile_exists: |-
505
- `Vagrantfile` already exists in this directory. Remove it before
506
- running `vagrant init`.
507
- vagrantfile_load_error: |-
508
- There was an error loading a Vagrantfile. The file being loaded
509
- and the error message are shown below. This is usually caused by
510
- a syntax error.
511
-
512
- Path: %{path}
513
- Message: %{message}
514
- vagrantfile_syntax_error: |-
515
- There is a syntax error in the following Vagrantfile. The syntax error
516
- message is reproduced below for convenience:
517
-
518
- %{file}
519
7
  prlctl_error: |-
520
8
  There was an error while executing `prlctl`, a CLI used by Vagrant
521
9
  for controlling Parallels Desktop. The command and stderr is shown below.
@@ -528,19 +16,13 @@ en:
528
16
  be found. Please verify Parallels Desktop is properly installed. You can verify
529
17
  everything is okay by running "prlctl --version" and verifying
530
18
  that the Parallels Desktop version is outputted.
531
- virtualbox_invalid_version: |-
532
- Vagrant has detected that you have a version of Parallels Desktop installed
533
- that is not supported. Please install one of the supported versions
534
- listed below to use Vagrant:
535
-
536
- %{supported_versions}
537
19
  parallels_kernel_module_not_loaded: |-
538
20
  Parallels Desktop is complaining that the kernel module is not loaded. Please
539
21
  run `prlctl --version` or open the Parallels Desktop GUI to see the error
540
22
  message which should contain instructions on how to fix this error.
541
23
  parallels_install_incomplete: |-
542
- Parallels Desktop is complaining that the installation is incomplete. Try to reinstall Parallels
543
- Desktop or contact Parallels support.
24
+ Parallels Desktop is complaining that the installation is incomplete.
25
+ Try to reinstall Parallels Desktop or contact Parallels support.
544
26
  parallels_no_room_for_high_level_network: |-
545
27
  There is no available slots on the Parallels Desktop VM for the configured
546
28
  high-level network interfaces. "private_network" and "public_network"
@@ -548,98 +30,10 @@ en:
548
30
  Parallels Desktop VM. Parallels Desktop limits the number of slots to 8, and it
549
31
  appears that every slot is in use. Please lower the number of used
550
32
  network adapters.
551
- virtualbox_not_detected: |-
552
- Vagrant could not detect Parallels Desktop! Make sure Parallels Desktop is properly installed.
553
- Vagrant uses the `prlctl` binary that ships with Parallels Desktop, and requires
554
- this to be available on the PATH. If Parallels Desktop is installed, please find the
555
- `prlctl` binary and add it to the PATH environmental variable.
556
- vm_creation_required: |-
557
- VM must be created before running this command. Run `vagrant up` first.
558
- vm_inaccessible: |-
559
- Your VM has become "inaccessible." Unfortunately, this is a critical error
560
- with Parallels Desktop that Vagrant can not cleanly recover from. Please open Parallels Desktop
561
- and clear out your inaccessible virtual machines or find a way to fix
562
- them.
563
- vm_name_exists: |-
564
- A Parallels Desktop virtual machine with the name '%{name}' already exists.
565
- Please use another name or delete the machine with the existing
566
- name, and try again.
567
- vm_no_match: |-
568
- No virtual machines matched the regular expression given.
569
- vm_not_found: |-
570
- A VM by the name of %{name} was not found.
571
- vm_not_running: |-
572
- VM must be running to open SSH connection. Run `vagrant up`
573
- to start the virtual machine.
574
-
575
33
  #-------------------------------------------------------------------------------
576
34
  # Translations for config validation errors
577
35
  #-------------------------------------------------------------------------------
578
36
  config:
579
- common:
580
- bad_field: "The following settings don't exist: %{fields}"
581
- error_empty: "`%{field}` must be not be empty."
582
- chef:
583
- cookbooks_path_empty: "Must specify a cookbooks path for chef solo."
584
- cookbooks_path_missing: |-
585
- Cookbook path doesn't exist: %{path}
586
- server_url_empty: "Chef server URL must be populated."
587
- validation_key_path: "Validation key path must be valid path to your chef server validation key."
588
- loader:
589
- bad_v1_key: |-
590
- Unknown configuration section '%{key}'. If this section was part of
591
- a Vagrant 1.0.x plugin, note that 1.0.x plugins are incompatible with 1.1+.
592
- root:
593
- bad_key: |-
594
- Unknown configuration section '%{key}'.
595
- ssh:
596
- private_key_missing: "`private_key_path` file must exist: %{path}"
597
- vm:
598
- base_mac_invalid: "Base MAC address for eth0/NAT must be set. Contact box maintainer for more information."
599
- box_missing: "A box must be specified."
600
- box_not_found: "The box '%{name}' could not be found."
601
- hostname_invalid_characters: |-
602
- The hostname set for the VM should only contain letters, numbers,
603
- and hyphens.
604
- network_invalid: |-
605
- The network type '%{type}' is not valid. Please use
606
- 'hostonly' or 'bridged'.
607
- network_ip_required: |-
608
- Host only networks require an IP as an argument.
609
- network_ip_invalid: |-
610
- The host only network IP '%{ip}' is invalid.
611
- network_ip_ends_one: |-
612
- The host only network IP '%{ip}' must not end in a 1, as this
613
- is reserved for the host machine.
614
- nfs_not_supported: |-
615
- It appears your machine doesn't support NFS, or there is not an
616
- adapter to enable NFS on this machine for Vagrant. Please verify
617
- that `nfsd` is installed on your machine, and try again. If you're
618
- on Windows, NFS isn't supported. If the problem persists, please
619
- contact Vagrant support.
620
- nfs_requires_host: |-
621
- Using NFS shared folders requires a host to be specified
622
- using `config.vagrant.host`.
623
- network_ip_required: |-
624
- An IP is required for a private network.
625
- network_fp_host_not_unique: |-
626
- Forwarded port '%{host}' (host port) is declared multiple times
627
- network_fp_requires_ports: |-
628
- Forwarded port definitions require a "host" and "guest" value
629
- network_type_invalid: |-
630
- Network type '%{type}' is invalid. Please use a valid network type.
631
- provisioner_not_found: |-
632
- The '%{name}' provisioner could not be found.
633
- shared_folder_guestpath_duplicate: |-
634
- A shared folder guest path is used multiple times. Shared
635
- folders must all map to a unique guest path: %{path}
636
- shared_folder_guestpath_relative: |-
637
- The shared folder guest path must be absolute: %{path}
638
- shared_folder_hostpath_missing: |-
639
- The host path of the shared folder is missing: %{path}
640
- shared_folder_nfs_owner_group: |-
641
- Shared folder that have NFS enabled do no support owner/group
642
- attributes. Host path: %{path}
643
37
  id_in_pre_import: |-
644
38
  The ':id' parameter is not available in "pre-import" customizations.
645
39
  invalid_event: |-
@@ -652,145 +46,33 @@ en:
652
46
  common:
653
47
  vm_already_running: |-
654
48
  Parallels Desktop VM is already running.
655
- vm_not_created: "VM not created. Moving on..."
656
- vm_not_running: "VM is not currently running. Please bring it up to run this command."
657
- box:
658
- no_installed_boxes: "There are no installed boxes! Use `vagrant box add` to add some."
659
- removing: |-
660
- Removing box '%{name}' with provider '%{provider}'...
661
- destroy:
662
- confirmation: "Are you sure you want to destroy the '%{name}' VM? [y/N] "
663
- will_not_destroy: |-
664
- The VM '%{name}' will not be destroyed, since the confirmation
665
- was declined.
666
- init:
667
- success: |-
668
- A `Vagrantfile` has been placed in this directory. You are now
669
- ready to `vagrant up` your first virtual environment! Please read
670
- the comments in the Vagrantfile as well as documentation on
671
- `vagrantup.com` for more information on using Vagrant.
672
- plugin:
673
- installed_license: |-
674
- The license for '%{name}' was successfully installed!
675
- installing_license: |-
676
- Installing license for '%{name}'...
677
- no_plugins: |-
678
- No plugins installed.
679
- installed: |-
680
- Installed the plugin '%{name} (%{version})'!
681
- installing: |-
682
- Installing the '%{name}' plugin. This can take a few minutes...
683
- uninstalling: |-
684
- Uninstalling the '%{name}' plugin...
685
49
  status:
686
- aborted: |-
687
- The VM is in an aborted state. This means that it was abruptly
688
- stopped without properly closing the session. Run `vagrant up`
689
- to resume this virtual machine. If any problems persist, you may
690
- have to destroy and restart the virtual machine.
691
- gurumeditation: |-
692
- The VM is in the "guru meditation" state. This is a rare case which means
693
- that an internal error in VitualBox caused the VM to fail. This is always
694
- the sign of a bug in Parallels Desktop. You can try to bring your VM back online
695
- with a `vagrant up`.
696
50
  inaccessible: |-
697
- The VM is inaccessible! This is a rare case which means that Parallels Desktop
698
- can't find your VM configuration. This usually happens when upgrading
699
- Parallels Desktop, moving to a new computer, etc. Please consult Parallels
700
- for how to handle this issue.
701
- output: |-
702
- Current machine states:
703
-
704
- %{states}
705
-
706
- %{message}
51
+ The VM is inaccessible! This is a rare case which means that Parallels
52
+ Desktop can't find your VM configuration. This usually happens when deleting
53
+ the VM via Parallels Desktop GUI, moving to a new computer, etc.
54
+ Please consult Vagrant Parallels provider for how to handle this issue.
707
55
  not_created: |-
708
56
  The environment has not yet been created. Run `vagrant up` to
709
57
  create the environment. If a machine is not created, only the
710
58
  default provider will be shown. So if a provider is not listed,
711
59
  then the machine is not created for that environment.
712
- paused: |-
713
- The VM is paused. This VM may have been paused via the Parallels Desktop
714
- GUI or the prlctl command line interface. To unpause, please
715
- use the Parallels Desktop GUI and/or prlctl command line interface so
716
- that vagrant would be able to control the VM again.
717
- poweroff: |-
718
- The VM is powered off. To restart the VM, simply run `vagrant up`
60
+ suspended: |-
61
+ The VM is suspended. To resume this VM you can run `vagrant resume`
62
+ or `vagrant up` to restart it again, so that vagrant would be able
63
+ to control the VM again.
64
+ stopped: |-
65
+ The VM is stopped. To start the VM, simply run `vagrant up`
719
66
  running: |-
720
67
  The VM is running. To stop this VM, you can run `vagrant halt` to
721
68
  shut it down forcefully, or you can run `vagrant suspend` to simply
722
69
  suspend the virtual machine. In either case, to restart it again,
723
70
  simply run `vagrant up`.
724
- saving: |-
725
- The VM is currently saving its state. In a few moments this state
726
- should transition to "saved." Please run `vagrant status` again
727
- in a few seconds.
728
- saved: |-
729
- To resume this VM, simply run `vagrant up`.
730
- stuck: |-
731
- The VM is "stuck!" This is a very rare state which means that
732
- Parallels Desktop is unable to recover the current state of the VM.
733
- The only known solution to this problem is to restart your
734
- machine, sorry.
735
- listing: |-
736
- This environment represents multiple VMs. The VMs are all listed
737
- above with their current state. For more information about a specific
738
- VM, run `vagrant status NAME`.
739
- up:
740
- upping: |-
741
- Bringing machine '%{name}' up with '%{provider}' provider...
742
- version:
743
- output: "Vagrant version %{version}"
744
-
745
71
  #-------------------------------------------------------------------------------
746
72
  # Translations for Vagrant middleware acions
747
73
  #-------------------------------------------------------------------------------
748
74
  actions:
749
- runner:
750
- waiting_cleanup: "Waiting for cleanup before exiting..."
751
- exit_immediately: "Exiting immediately, without cleanup!"
752
75
  vm:
753
- boot:
754
- booting: Booting VM...
755
- waiting: Waiting for VM to boot. This can take a few minutes.
756
- ready: VM booted and ready for use!
757
- failed: Failed to connect to VM!
758
- failed_to_boot: |-
759
- Failed to connect to VM via SSH. Please verify the VM successfully booted
760
- by looking at the Parallels Desktop GUI.
761
- failed_to_run: |-
762
- The VM failed to remain in the "running" state while attempting to boot.
763
- This is normally caused by a misconfiguration or host system incompatibilities.
764
- Please open the Parallels Desktop GUI and attempt to boot the virtual machine
765
- manually to get a more informative error message.
766
- bridged_networking:
767
- available: |-
768
- Available bridged network interfaces:
769
- bridging: |-
770
- Bridging adapter #%{adapter} to '%{bridge}'
771
- enabling: |-
772
- Enabling bridged network...
773
- preparing: |-
774
- Preparing bridged networking...
775
- specific_not_found: |-
776
- Specific bridge '%{bridge}' not found. You may be asked to specify
777
- which network to bridge to.
778
- check_box:
779
- not_found: |-
780
- Box '%{name}' was not found. Fetching box from specified URL for
781
- the provider '%{provider}'. Note that if the URL does not have
782
- a box for this provider, you should interrupt Vagrant now and add
783
- the box yourself. Otherwise Vagrant will attempt to download the
784
- full box prior to discovering this error.
785
- not_specified: |-
786
- No base box was specified! A base box is required as a staring point
787
- for every vagrant virtual machine. Please specify one in your Vagrantfile
788
- using `config.vm.box`
789
- does_not_exist: |-
790
- Specified box `%{name}` does not exist!
791
-
792
- The box must be added through the `vagrant box add` command. Please view
793
- the documentation associated with the command for more information.
794
76
  check_guest_tools:
795
77
  not_detected: |-
796
78
  No Parallels Tools were detected on the base box for this VM! Parallels
@@ -809,336 +91,10 @@ en:
809
91
 
810
92
  Parallels Tools Version: %{tools_version}
811
93
  Parallels Desktop Version: %{parallels_version}
812
- clear_forward_ports:
813
- deleting: Clearing any previously set forwarded ports...
814
- clear_network_interfaces:
815
- deleting: Clearing any previously set network interfaces...
816
- clear_shared_folders:
817
- deleting: Cleaning previously set shared folders...
818
- customize:
819
- failure: |-
820
- A customization command failed:
821
-
822
- %{command}
823
-
824
- The following error was experienced:
825
-
826
- %{error}
827
-
828
- Please fix this customization and try again.
829
- running: Running any VM customizations...
830
- destroy:
831
- destroying: Destroying VM and associated drives...
832
- destroy_network:
833
- destroying: Destroying unused networking interface...
834
- disable_networks:
835
- disabling: Disabling host only networks...
836
- discard_state:
837
- discarding: Discarding saved state of VM...
838
94
  export:
839
- create_dir: Creating temporary directory for export...
840
- exporting: Exporting VM...
841
95
  compacting: Compacting exported HDD...
842
- power_off: "The Vagrant virtual environment you are trying to package must be powered off."
843
- forward_ports:
844
- auto_empty: |-
845
- Vagrant found a port collision for the specified port and virtual machine.
846
- While this port was marked to be auto-corrected, the ports in the
847
- auto-correction range are all also used.
848
-
849
- VM: %{vm_name}
850
- Forwarded port: %{guest_port} => %{host_port}
851
- collision_error: |-
852
- Vagrant cannot forward the specified ports on this VM, since they
853
- would collide with some other application that is already listening
854
- on these ports. The forwarded port to %{host_port} is already in use
855
- on the host machine.
856
-
857
- To fix this, modify your current projects Vagrantfile to use another
858
- port. Example, where '1234' would be replaced by a unique host port:
859
-
860
- config.vm.network :forwarded_port, guest: %{guest_port}, host: 1234
861
-
862
- Sometimes, Vagrant will attempt to auto-correct this for you. In this
863
- case, Vagrant was unable to. This is usually because the guest machine
864
- is in a state which doesn't allow modifying port forwarding.
865
- fixed_collision: |-
866
- Fixed port collision for %{guest_port} => %{host_port}. Now on port %{new_port}.
867
- forwarding: Forwarding ports...
868
- forwarding_entry: |-
869
- -- %{guest_port} => %{host_port} (adapter %{adapter})
870
- non_nat: |-
871
- Parallels Desktop network adapter #%{adapter} not configured as "NAT". Skipping port
872
- forwards on this adapter.
873
- privileged_ports: |-
874
- You are trying to forward to privileged ports (ports <= 1024). Most
875
- operating systems restrict this to only privileged process (typically
876
- processes running as an administrative user). This is a warning in case
877
- the port forwarding doesn't work. If any problems occur, please try a
878
- port higher than 1024.
879
- halt:
880
- force: Forcing shutdown of VM...
881
- graceful: Attempting graceful shutdown of VM...
882
- waiting: Waiting for VM to shutdown. This can take a few minutes.
883
- failed: Failed to gracefully shutdown the VM.
884
- done: VM shutdown complete!
885
- hostname:
886
- setting: "Setting hostname..."
887
- import:
888
- importing: Importing base box '%{name}'...
889
- failure: |-
890
- The VM import failed! Try running `prlctl import` on the box file
891
- manually for more verbose error output.
892
96
  match_mac:
893
97
  generate: |-
894
98
  The specified base MAC is already in use. Generating a new unique MAC
895
99
  address for Shared network...
896
100
  matching: Matching MAC address for Shared network...
897
- no_base_mac: |-
898
- No base MAC address was specified. This is required for the NAT networking
899
- to work properly (and hence port forwarding, SSH, etc.). Specifying this
900
- MAC address is typically up to the box and box maintiner. Please contact
901
- the relevant person to solve this issue.
902
- network:
903
- adapter_collision: |-
904
- More than one network have been assigned to the same adapter. Please
905
- make sure your networks you've configured in your Vagrantfile do not
906
- overlap.
907
- configuring: |-
908
- Configuring and enabling network interfaces...
909
- dhcp_already_attached: |-
910
- A host only network interface you're attempting to configure via DHCP
911
- already has a conflicting host only adapter with DHCP enabled. The
912
- DHCP on this adapter is incompatible with the DHCP settings. Two
913
- host only network interfaces are not allowed to overlap, and each
914
- host only network interface can have only one DHCP server. Please
915
- reconfigure your host only network or remove the virtual machine
916
- using the other host only network.
917
- no_adapters: |-
918
- No available adapters on the virtual machine were found to accomodate
919
- for all configured networks. Parallels Desktop virtual machines have 8
920
- network interfaces available usually, so please lower the number of
921
- networks to below 8.
922
- preparing: |-
923
- Preparing network interfaces based on configuration...
924
- host_only_network:
925
- collides: |-
926
- The specified host network collides with a non-hostonly network!
927
- This will cause your specified IP to be inaccessible. Please change
928
- the IP or name of your host only network to not match that of
929
- a bridged or non-hostonly network.
930
- creating: "Creating new host only network for environment..."
931
- enabling: "Enabling host only network..."
932
- not_found: |-
933
- The specified host network could not be found: '%{name}.'
934
- If the name specification is removed, Vagrant will create a new
935
- host only network for you. Alternatively, please create the
936
- specified network manually.
937
- preparing: "Preparing host only network..."
938
- nfs:
939
- exporting: Exporting NFS shared folders...
940
- mounting: Mounting NFS shared folders...
941
- persist:
942
- dotfile_error: |-
943
- The dotfile which Vagrant uses to store the UUID of the project's
944
- virtual machine already exists and is not a file! The dotfile is
945
- currently configured to be '%{dotfile_path}'
946
-
947
- To change this value, please see `config.vagrant.dotfile_name`
948
-
949
- Are you trying to use Vagrant from your home directory? This is the
950
- leading cause of this error message. To resolve this, simply use a
951
- different directory. Or, if you really want to run Vagrant from your
952
- home directory, modify the `config.vagrant.dotfile_name` configuration
953
- key.
954
- persisting: "Persisting the VM UUID (%{uuid})..."
955
- provision:
956
- beginning: "Running provisioner: %{provisioner}..."
957
- resume:
958
- resuming: Resuming suspended VM...
959
- unpausing: |-
960
- Unpausing the VM...
961
- share_folders:
962
- creating: Creating shared folders metadata...
963
- mounting: Mounting shared folders...
964
- mounting_entry: "-- %{guest_path}"
965
- nomount_entry: "-- Automounting disabled: %{host_path}"
966
- set_name:
967
- setting_name: |-
968
- Setting the name of the VM...
969
- suspend:
970
- suspending: Saving VM state and suspending execution...
971
-
972
- box:
973
- unpackage:
974
- untar_failure: |-
975
- The box failed to unpackage properly. Please verify that the box
976
- file you're trying to add is not corrupted and try again. The
977
- output from attempting to unpackage (if any):
978
-
979
- %{output}
980
- already_exists: |-
981
- The box you're attempting to add already exits:
982
-
983
- Name: %{name}
984
- Provider: %{provider}
985
- add:
986
- adding: |-
987
- Extracting box...
988
- added: |-
989
- Successfully added box '%{name}' with provider '%{provider}'!
990
- destroy:
991
- destroying: "Deleting box '%{name}'..."
992
- download:
993
- cleaning: "Cleaning up downloaded box..."
994
- downloading: "Downloading or copying the box..."
995
- interrupted: "Box download was interrupted. Exiting."
996
- verify:
997
- verifying: "Verifying box..."
998
- failed: |-
999
- The box file you're attempting to add is invalid. This can be
1000
- commonly attributed to typos in the path given to the box add
1001
- command. Another common case of this is invalid packaging of the
1002
- box itself.
1003
-
1004
- general:
1005
- package:
1006
- packaging: "Packaging additional file: %{file}"
1007
- compressing: "Compressing package to: %{tar_path}"
1008
- output_exists: |-
1009
- The specified file to save the package as already exists. Please
1010
- remove this file or specify a different file name for outputting.
1011
- output_is_directory: |-
1012
- The specified output is a directory. Please specify a path including
1013
- a filename.
1014
- requires_directory: |-
1015
- A directory was not specified to package. This should never happen
1016
- and is a result of an internal inconsistency.
1017
- include_file_missing: |-
1018
- Package include file doesn't exist: %{file}
1019
-
1020
- downloaders:
1021
- file:
1022
- download: "Copying box to temporary location..."
1023
- file_missing: "The specified path to a file doesn't exist."
1024
- http:
1025
- connection_reset: |-
1026
- The remote server unexpectedly closed the connection. Vagrant was
1027
- unable to finish downloading the box. Please try again. If this
1028
- problem persists, please try downloading the box manually outside
1029
- of Vagrant, then adding the box from the filesystem.
1030
- connection_timeout: |-
1031
- Vagrant timed out while attempting to connect to the HTTP host.
1032
- Please check your internet and proxy settings and try again.
1033
- download: "Downloading box: %{url}"
1034
- socket_error: |-
1035
- An error occurred while trying to download the specified box. This most
1036
- often happens if there is no internet connection or the address is
1037
- invalid.
1038
- status_error: |-
1039
- Bad status code: %{status}
1040
-
1041
- Please verify that the box exists and is accessible. Also verify that
1042
- this computer is properly connected to the internet.
1043
-
1044
- hosts:
1045
- bsd:
1046
- nfs_export: |-
1047
- Preparing to edit /etc/exports. Administrator privileges will be required...
1048
- nfs_prune: |-
1049
- Pruning invalid NFS exports. Administrator privileges will be required...
1050
- linux:
1051
- nfs_export: |-
1052
- Preparing to edit /etc/exports. Administrator privileges will be required...
1053
- nfs_prune: |-
1054
- Pruning invalid NFS exports. Administrator privileges will be required...
1055
- arch:
1056
- nfs_export:
1057
- prepare: "Preparing to edit /etc/exports. Administrator privileges will be required..."
1058
- freebsd:
1059
- nfs_whitespace: |-
1060
- FreeBSD hosts do not support sharing directories with whitespace in
1061
- their path. Please adjust your path accordingly.
1062
-
1063
- provisioners:
1064
- chef:
1065
- chef_not_detected: |-
1066
- The chef binary (either `chef-solo` or `chef-client`) was not found on
1067
- the VM and is required for chef provisioning. Please verify that chef
1068
- is installed and that the binary is available on the PATH.
1069
- cookbook_folder_not_found_warning:
1070
- "The cookbook path '%{path}' doesn't exist. Ignoring..."
1071
- json: "Generating chef JSON and uploading..."
1072
- client_key_folder: "Creating folder to hold client key..."
1073
- upload_validation_key: "Uploading chef client validation key..."
1074
- upload_encrypted_data_bag_secret_key: "Uploading chef encrypted data bag secret key..."
1075
- running_client: "Running chef-client..."
1076
- running_client_again: "Running chef-client again (failed to converge)..."
1077
- running_solo: "Running chef-solo..."
1078
- running_solo_again: "Running chef-solo again (failed to converge)..."
1079
- missing_shared_folders: |-
1080
- Shared folders that Chef requires are missing on the virtual machine.
1081
- This is usually due to configuration changing after already booting the
1082
- machine. The fix is to run a `vagrant reload` so that the proper shared
1083
- folders will be prepared and mounted on the VM.
1084
- no_convergence: |-
1085
- Chef never successfully completed! Any errors should be visible in the
1086
- output above. Please fix your recipes so that they properly complete.
1087
- not_detected: |-
1088
- The `%{binary}` binary appears to not be in the PATH of the guest. This
1089
- could be because the PATH is not properly setup or perhaps chef is not
1090
- installed on this guest. Chef provisioning can not continue without
1091
- chef properly installed.
1092
- server_url_required: |-
1093
- Chef server provisioning requires that the `config.chef.chef_server_url` be set to the
1094
- URL of your chef server. Examples include "http://12.12.12.12:4000" and
1095
- "http://myserver.com:4000" (the port of course can be different, but 4000 is the default)
1096
- server_validation_key_required: |-
1097
- Chef server provisioning requires that the `config.chef.validation_key_path` configuration
1098
- be set to a path on your local machine of the validation key used to register the
1099
- VM with the chef server.
1100
- server_validation_key_doesnt_exist: |-
1101
- The validation key set for `config.chef.validation_key_path` does not exist! This
1102
- file needs to exist so it can be uploaded to the virtual machine.
1103
-
1104
- puppet:
1105
- not_detected: |-
1106
- The `%{binary}` binary appears to not be in the PATH of the guest. This
1107
- could be because the PATH is not properly setup or perhaps Puppet is not
1108
- installed on this guest. Puppet provisioning can not continue without
1109
- Puppet properly installed.
1110
- running_puppet: "Running Puppet with %{manifest}..."
1111
- manifest_missing: |-
1112
- The configured Puppet manifest is missing. Please specify a path to an
1113
- existing manifest:
1114
-
1115
- %{manifest}
1116
- manifests_path_missing: "The manifests path specified for Puppet does not exist: %{path}"
1117
- missing_shared_folders: |-
1118
- Shared folders that Puppet requires are missing on the virtual machine.
1119
- This is usually due to configuration changing after already booting the
1120
- machine. The fix is to run a `vagrant reload` so that the proper shared
1121
- folders will be prepared and mounted on the VM.
1122
- module_path_missing: "The configured module path doesn't exist: %{path}"
1123
-
1124
- puppet_server:
1125
- not_detected: |-
1126
- The `%{binary}` binary appears to not be in the PATH of the guest. This
1127
- could be because the PATH is not properly setup or perhaps Puppet is not
1128
- installed on this guest. Puppet provisioning can not continue without
1129
- Puppet properly installed.
1130
- running_puppetd: "Running Puppet agent..."
1131
-
1132
- shell:
1133
- args_not_string: "Shell provisioner `args` must be a string."
1134
- no_path_or_inline: "One of `path` or `inline` must be set."
1135
- path_and_inline_set: "Only one of `path` or `inline` may be set."
1136
- path_invalid: "`path` for shell provisioner does not exist on the host system: %{path}"
1137
- running: "Running: %{script}"
1138
- upload_path_not_set: "`upload_path` must be set for the shell provisioner."
1139
-
1140
- ansible:
1141
- no_playbook: "`playbook` must be set for the Ansible provisioner."
1142
- playbook_path_invalid: "`playbook` for the Ansible provisioner does not exist on the host system: %{path}"
1143
- inventory_file_path_invalid: "`inventory_file` for the Ansible provisioner does not exist on the host system: %{path}"
1144
- extra_vars_not_hash: "`extra_vars` for the Ansible provisioner must be a hash"