templates/locales/en.yml in vagrant-unbundled-2.2.9.0 vs templates/locales/en.yml in vagrant-unbundled-2.2.10.0

- old
+ new

@@ -125,10 +125,11 @@ to automatically delete Chef nodes and clients. chef_run_list_empty: |- Warning: Chef run list is empty. This may not be what you want. cli_interrupt: |- Exiting due to interrupt. + cloud_init_waiting: Waiting for cloud init to finish running container_pulling_single: |- -- Image: %{name} container_building_single: |- -- Path: %{path} container_running: |- @@ -162,10 +163,14 @@ -- Detected changes to container '%{name}' args, restarting... docker_restarting_container_image: |- -- Detected newer image for container '%{name}', restarting... docker_starting_containers: |- Starting Docker containers... + hyperv_enable_enhanced_session: |- + Setting VM Enhanced session transport type to HvSocket + hyperv_disable_enhanced_session: |- + Setting VM Enhanced session transport type to disabled/default (VMBus) inserted_key: |- Key inserted! Disconnecting and reconnecting using new SSH key... inserting_insecure_detected: |- Vagrant insecure key detected. Vagrant will automatically replace this with a newly generated keypair for better security. @@ -786,10 +791,15 @@ It doesn't need to be running. Additionally, the created environment must be started with a provider matching this provider. For example, if you're using VirtualBox, the clone environment must also be using VirtualBox. + cloud_init_not_found: |- + cloud-init is not found. Please ensure that cloud-init is installed and + available on path for guest '%{guest_name}'. + cloud_init_command_failed: |- + cloud init command '%{cmd}' failed on guest '%{guest_name}'. command_deprecated: |- The command 'vagrant %{name}' has been deprecated and is no longer functional within Vagrant. command_suspend_all_arguments: |- The suspend command with the `--all-global` flag does not take any arguments. @@ -830,10 +840,13 @@ to manually correct it, then remove the data file at the path below. This will leave all existing Vagrant environments "orphaned" and they'll have to be destroyed manually. Path: %{path} + create_iso_host_cap_not_found: |- + Vagrant cannot create an iso due to the host capability for creating isos not existing. + Vagrant will now exit. destroy_requires_force: |- Destroy doesn't have a TTY to ask for confirmation. Please pass the `--force` flag to force a destroy, otherwise attach a TTY so that the destroy can be confirmed. dotfile_upgrade_json_error: |- @@ -937,10 +950,22 @@ host_explicit_not_detected: |- The host implementation explicitly specified in your Vagrantfile ("%{value}") could not be found. Please verify that the plugin is installed which implements this host and that the value you used for `config.vagrant.host` is correct. + iso_build_failed: |- + Failed to build iso image. The following command returned an error: + + %{cmd} + + Stdout from the command: + + %{stdout} + + Stderr from the command: + + %{stderr} hyperv_virtualbox_error: |- Hyper-V and VirtualBox cannot be used together and will result in a system crash. Vagrant will now exit. Please disable Hyper-V if you wish to use VirtualBox. interrupted: |- @@ -1433,10 +1458,15 @@ ssh_disconnected: |- The SSH connection was unexpectedly closed by the remote end. This usually indicates that SSH within the guest machine was unable to properly start up. Please boot the VM in GUI mode to check whether it is booting properly. + ssh_no_exit_status: |- + The SSH command completed, but Vagrant did not receive an exit status. + This indicates that the command was terminated unexpectedly. Please + check that the VM has sufficient memory to run the command and that no + processes were killed by the guest operating system. ssh_no_route: |- While attempting to connect with SSH, a "no route to host" (EHOSTUNREACH) error was received. Please verify your network settings are correct and try again. ssh_host_down: |- @@ -1661,15 +1691,34 @@ virtualbox_broken_version_040214: |- Vagrant detected you have VirtualBox 4.2.14 installed. VirtualBox 4.2.14 contains a critical bug which prevents it from working with Vagrant. VirtualBox 4.2.16+ fixes this problem. Please upgrade VirtualBox. - virtualbox_disks_defined_exceed_limit: |- - VirtualBox only allows up to 30 disks to be attached to a single guest using the SATA Controller, - including the primray disk. + virtualbox_disks_controller_not_found: |- + Vagrant expected to find a storage controller called '%{name}', + but there is no controller with this name attached to the current VM. + If you have changed or removed any storage controllers, please restore + them to their previous configuration. + virtualbox_disks_no_supported_controllers: |- + Vagrant was unable to detect a disk controller with any of the + following supported types: - Please ensure only up to 30 disks are configured for your guest. + %{supported_types} + + Please add one of the supported controller types in order to use the + disk configuration feature. + virtualbox_disks_defined_exceed_limit: |- + VirtualBox only allows up to %{limit} disks to be attached to the + storage controller '%{name}'. Please remove some disks from your disk + configuration, or attach a new storage controller. + virtualbox_disks_primary_not_found: |- + Vagrant was not able to detect a primary disk attached to the main + controller. Vagrant Disks requires that the primary disk be attached + to the first port of the main controller in order to manage it. + virtualbox_disks_unsupported_controller: |- + An disk operation was attempted on the controller '%{controller_name}', + but Vagrant doesn't support this type of disk controller. virtualbox_guest_property_not_found: |- Could not find a required VirtualBox guest property: %{guest_property} This is an internal error that should be reported as a bug. virtualbox_invalid_version: |- @@ -1827,10 +1876,15 @@ #------------------------------------------------------------------------------- # Translations for config validation errors #------------------------------------------------------------------------------- config: disk: + dvd_type_file_required: + A 'file' option is required when defining a disk of type ':dvd' for guest '%{machine}'. + dvd_type_primary: |- + Disks of type ':dvd' cannot be defined as a primary disks. Please + remove the 'primary' argument for disk '%{name}' on guest '%{machine}'. invalid_ext: |- Disk type '%{ext}' is not a valid disk extention for '%{name}'. Please pick one of the following supported disk types: %{exts} invalid_type: |- Disk type '%{type}' is not a valid type. Please pick one of the following supported disk types: %{types} invalid_size: |- @@ -1939,25 +1993,40 @@ "box_download_ca_path" directory not found: %{path} box_download_checksum_blank: |- Checksum type specified but "box_download_checksum" is blank box_download_checksum_notblank: |- Checksum specified but must also specify "box_download_checksum_type" + box_empty: "Box value for guest '%{machine_name}' is an empty string." box_missing: "A box must be specified." box_download_options_type: |- Found "box_download_options" specified as type '%{type}', should be a Hash box_download_options_not_converted: |- Something went wrong converting VM config `box_download_options`. Value for provided key '%{missing_key}' is invalid type. Should be String or Bool clone_and_box: "Only one of clone or box can be specified." + config_type: "Found '%{option}' specified as type '%{given}', should be '%{required}'" hostname_invalid_characters: |- The hostname set for the VM '%{name}' should only contain letters, numbers, hyphens or dots. It cannot start with a hyphen or dot. ignore_provider_config: |- Ignoring provider config for validation... multiple_primary_disks_error: |- There are more than one primary disks defined for guest '%{name}'. Please ensure that only one disk has been defined as a primary disk. + multiple_disk_files_error: |- + The following disk files are used multiple times in the disk + configuration for the VM '%{name}': + + %{disk_files} + + Each disk file may only be attached to a VM once. multiple_disk_names_error: |- - Duplicate disk names defined: '%{name}'. Disk names must be unique. + The following disks names are defined multiple times in the disk + configuration for the VM '%{name}': + + %{disk_names} + + Disk names must be unique. + multiple_networks_set_hostname: "Multiple networks have set `:hostname`" name_invalid: |- The sub-VM name '%{name}' is invalid. Please don't use special characters. network_ip_ends_in_one: |- You assigned a static IP ending in ".1" to this machine. This is very often used by the router and can cause the @@ -1972,10 +2041,11 @@ with the protocol '%{protocol}'. network_fp_requires_ports: |- Forwarded port definitions require a "host" and "guest" value network_type_invalid: |- Network type '%{type}' is invalid. Please use a valid network type. + network_with_hostname_must_set_ip: "Network specified with `:hostname` must provide a static ip" provisioner_not_found: |- The '%{name}' provisioner could not be found. shared_folder_guestpath_duplicate: |- A shared folder guest path is used multiple times. Shared folders must all map to a unique guest path: %{path} @@ -2203,26 +2273,58 @@ #------------------------------------------------------------------------------- # Translations for Vagrant middleware actions #------------------------------------------------------------------------------- cap: + cleanup_disks: + disk_cleanup: |- + Disk '%{name}' no longer exists in Vagrant config. Removing and closing medium from guest... + disk_not_found: |- + Disk '%{name}' could not be found, and could not be properly removed. Please remove this disk manually if it still exists configure_disks: - start: "Configuring storage mediums..." + create_disk: |- + Disk '%{name}' not found in guest. Creating and attaching disk to guest... floppy_not_supported: "Floppy disk configuration not yet supported. Skipping disk '%{name}'..." - dvd_not_supported: "DVD disk configuration not yet supported. Skipping disk '%{name}'..." shrink_size_not_supported: |- VirtualBox does not support shrinking disk sizes. Cannot shrink '%{name}' disks size. - create_disk: |- - Disk '%{name}' not found in guest. Creating and attaching disk to guest... resize_disk: |- Disk '%{name}' needs to be resized. Resizing disk... recovery_from_resize: |- Vagrant has encountered an exception while trying to resize a disk. It will now attempt to reattach the original disk, as to prevent any data loss. The original disk is located at %{location} If Vagrant fails to reattach the original disk, it is recommended that you open the VirtualBox GUI and navigate to the current guests settings for '%{name}' and look at the 'storage' section. Here is where you can reattach a missing disk if Vagrant fails to do so... recovery_attached_disks: |- Disk has been reattached. Vagrant will now continue on an raise the exception receieved + start: "Configuring storage mediums..." + cloud_init: + content_type_not_set: |- + 'content_type' must be defined for a cloud_init config. Guest '%{machine}' + has not defined a 'content_type' for its cloud_init config. Valid options + supported by Vagrant are listed below: + + %{accepted_types} + incorrect_content_type: |- + Content-type "%{content_type}" is not supported by Vagrant and + cloud-init on machine '%{machine}'. Valid options supported by Vagrant are + listed below: + + %{accepted_types} + incorrect_inline_type: |- + The inline config cloud_init option for guest '%{machine}' is of type '%{type}', but + should be a String. + incorrect_path_type: |- + The path '%{path}' given for guest '%{machine}' is of type '%{type}'. + Config option 'path' must be a String. + incorrect_type_set: |- + The type '%{type}' defined for a cloud_init config with guest '%{machine}' + is not a valid type. Currently, Vagrant only supports type: '%{default_type}'. + path_and_inline_set: |- + Guest '%{machine}' defines both a 'path' and 'inline' for its cloud_init config, + however only one config option should be defined for cloud_init. + path_invalid: |- + The path '%{path}' defined for guest '%{machine}' cloud_init config was + not found on the system. actions: runner: waiting_cleanup: "Waiting for cleanup before exiting..." exit_immediately: "Exiting immediately, without cleanup!" disk: @@ -2291,10 +2393,12 @@ creating: Cloning VM... failure: Creation of the linked clone failed. create_master: failure: |- Failed to create lock-file for master VM creation for box %{box}. + cloud_init_user_data_setup: |- + Preparing user data for cloud-init... customize: failure: |- A customization command failed: %{command} @@ -2607,11 +2711,11 @@ invalid_alias_value: |- Provisioner option `%{opt}` is not set as a valid type. Must be a string, or one of the alias shortcuts: %{alias} missing_provisioner_name: |- Could not find provisioner name `%{name}` defined for machine `%{machine_name}` to run provisioner "%{provisioner_name}" `%{action}`. wrong_type: |- - Provisioner option `%{opt}` is not set as a valid type. Must be a string. + Provisioner option `%{opt}` is not set as a valid type. Must be a %{type}. chef: chef_not_detected: |- The chef binary (either `chef-solo` or `chef-client`) was not found on the VM and is required for chef provisioning. Please verify that chef is installed and that the binary is available on the PATH. @@ -2671,11 +2775,11 @@ installed on this guest. Chef provisioning can not continue without chef properly installed. server_url_required: |- Chef server provisioning requires that the `config.chef.chef_server_url` be set to the URL of your chef server. Examples include "http://12.12.12.12:4000" and - "http://myserver.com:4000" (the port of course can be different, but 4000 is the default) + "http://example.com:4000" (the port of course can be different, but 4000 is the default) server_validation_key_required: |- Chef server provisioning requires that the `config.chef.validation_key_path` configuration be set to a path on your local machine of the validation key used to register the VM with the chef server. server_validation_key_doesnt_exist: |- @@ -2892,5 +2996,11 @@ You must set the option `install_type` when specifying a `version`. pushes: file: no_destination: "File destination must be specified." + + autocomplete: + installed: |- + Autocomplete installed at paths: + - %{paths} + not_installed: "Autocomplete not installed"