chrisroberts
Repos
142
Followers
156
Following
3

Events

Add support for Ruby 3.1

The biggest change comming with Ruby 3.1 is that net/ftp is no longer bundled with Ruby but distributed as a separate gem.

Add Ruby 3.1 to the CI

Relax overly strict grpc-tools version requirement

"~> 1.41.1" limits us to 1.41 which is already a year old now, relaxing this to "~> 1.41" allows us to pick up fresher and maintained releases.

Fix capitalizations in docs

Fixes various capitalizations in the docs

  • Ex: VMware, Linux/Unix, PowerShell, some abbreviations

Also, Prettier auto-formatted away some trailing spaces.

Remove vmware plugin tos (no longer relevant)

Remove vmware plugin eula

Merge pull request #12850 from soapy1/vmware-tos

Remove vmware plugin tos (no longer relevant)

Pass in echo/secret ui input setting

Ensure candidate ips are available when determining mount name

Merge pull request #12834 from danbarr/fix-capitalization

Fix capitalizations in docs

(#12884) Use default ssh.private_key_path when ssh.keys_only = false

Add new config

This will link to the forum to encourage users to post questions there instead of GitHub. This was borrowed from Nomad.

Merge pull request #12890 from kaitlincart/patch-1

Add new config

Bump sdk

Merge pull request #12876 from soapy1/secret-input

Pass in echo/secret ui input setting

Update CHANGELOG.md

Run mod tidy

Merge pull request #12892 from soapy1/mod-tidy

Run mod tidy

Fix syntax error in spectesting.yml

Multiple keys of the same name are not allowed. Instead, the "if's" can be evaluated as a boolean (and) expression

Colour go experimental warning

Created at 1 hour ago
issue comment
Unable to run vagrant on my PC: OS Name Microsoft Windows 11 Enterprise

Hi there,

The Vagrantfile provided in the issue description is not a Vagrantfile. It appears to be the contents of the json class from the json library. The error message provided appears to be failing to load the machine index file. If errors are persisting, you can try to remove the vagrant home directory (located at .vagrant.d in the user's home directory) which will remove any state Vagrant has on the host system (will remove any plugins and local guest information) and then try again. If the error persists, please provide a minimal, valid Vagrantfile and a gist of the debug output obtained by running vagrant up --debug.

Thanks.

Created at 1 day ago
closed issue
`vagrant reload` did not bring up new VM when updated the `Vagrantfile`

Vagrant version

Installed Version: 2.3.0 Latest Version: 2.3.0

Host operating system

MacOS 12

Guest operating system

ubuntu-bionic-18.04-cloudimg-20220902

Vagrantfile

See below.

Debug output

...
==> lb: VM not created. Moving on...
...

Expected behavior

  1. Brint up the new VM based on the lastest Vagrantfile;
  2. After new VM running, destroy the old VM;

Actual behavior

  1. First, we set the Vagrantfile like this:
config.vm.define "loadbalancer" do |node|
    node.vm.provider "virtualbox" do |vb|
        vb.name = "kubernetes-ha-lb"
        vb.memory = 512
        vb.cpus = 1
    end
    node.vm.hostname = "loadbalancer"
  1. Then do the vagrant up;
  2. After the loadbalancer VM running, we changed the name:
config.vm.define "lb" do |node|
    node.vm.provider "virtualbox" do |vb|
        vb.name = "kubernetes-ha-lb"
        vb.memory = 512
        vb.cpus = 1
    end
    node.vm.hostname = "lb"
  1. Then do the vagrant reload, it just output ==> lb: VM not created. Moving on....

Steps to reproduce

See above.

Created at 1 day ago
issue comment
`vagrant reload` did not bring up new VM when updated the `Vagrantfile`

Hi there,

This is due to the underlying way Vagrant currently works. The guest can still be located (and destroyed) via vagrant global-status. However, for interaction with a guest in a project, it must be defined in the Vagrantfile. This limitation is being removed in the new vagrant-go work, but the existing behavior in the current Ruby implementation will not be changed.

Cheers!

Created at 1 day ago
issue comment
Make bash completion for "vagrant box add"

If you'd like to open a PR with the change that would be great!

Created at 1 day ago
issue comment
vagrant up fails on Windows with Virtualbox

Hi there. This issue has come up in the past and is generally related to antivirus software or a bad install of virtualbox on the host.

Created at 1 day ago
closed issue
vagrant up fails or doesn't boot up the VM on Virtual Box on Windows 10/11 (--type headless is causing the issue)

Debug output

vagrant up --debug output https://gist.github.com/skeeith/7a99c1308af668250e0523455798c403

VBoxSVC.log file https://gist.github.com/skeeith/970c2245c1ad45726684fd45ca2391fa

Expected behavior

Just boots the VM normally

Actual behavior

Stuck on Booting VM

Reproduction information

install Virtual Box v6.1.38 and Vagrant v2.3.0 on Windows 10/11

Vagrant version

Version 2.3.0

Host operating system

Windows 11

Guest operating system

Ubuntu 20.04 LTS

Steps to reproduce

  1. vagrant up

Reference Issue

https://github.com/hashicorp/vagrant/issues/12897

Created at 1 day ago
issue comment
vagrant up fails or doesn't boot up the VM on Virtual Box on Windows 10/11 (--type headless is causing the issue)

Duplicate of #12897

Created at 1 day ago
issue comment
Vagrant file bypass 'config.vm.box_check_update = false' on ubuntu.

Hi there,

The underlying cause of the issue you are encountering is due to the box you are using, or a plugin you have installed. The box_check_update option controls whether or not Vagrant (on the host machine) checks if the box is use has been updated. The errors you are encountering are due to an apt command failing to download packages on the guest. This is occurring due to a provisioner defined defined in the box Vagrantfile, a plugin that you may have installed which is providing some extended functionality for the guest, or perhaps in your existing Vagrantfile if the entire thing was not provided in the original issue description.

The Vagrantfile you provided is also defining a named guest but part of the configuration is being applied to all defined guests due to using the config variable instead of the core variable. The contents should look like this:

Vagrant.configure("2") do |config|
  config.vm.box_check_update = false
  config.vm.box = "ubuntu18.04.6"  
  config.vm.define "core" do |core|    
    core.vm.network "public_network", ip: "192.168.1.216", bridge: "en0: Wi-Fi (Wireless)"
    conre.vm.provision "file", source: "~/.ssh/id_rsa.pub", destination: "~/.ssh/me.pub"    
    core.vm.provision "shell", inline: <<-SHELL
      cat /home/vagrant/.ssh/me.pub >> /home/vagrant/.ssh/authorized_keys
    SHELL
  end
end

If you remove any installed plugins and try again with the bento/ubuntu-18.04 box and still encounter errors, please provide a gist of the entire debug log (the output from running vagrant up --debug).

Cheers!

Created at 1 day ago

Fix previous branch creation and updates

Created at 4 days ago
create branch
chrisroberts create branch release/2.3.x
Created at 4 days ago
create branch
chrisroberts create branch release/2.3.0
Created at 4 days ago

Update files for new development

Include extension on compressed asset

Add support for Ruby 3.1

The biggest change comming with Ruby 3.1 is that net/ftp is no longer bundled with Ruby but distributed as a separate gem.

Add Ruby 3.1 to the CI

Relax overly strict grpc-tools version requirement

"~> 1.41.1" limits us to 1.41 which is already a year old now, relaxing this to "~> 1.41" allows us to pick up fresher and maintained releases.

Fix capitalizations in docs

Fixes various capitalizations in the docs

  • Ex: VMware, Linux/Unix, PowerShell, some abbreviations

Also, Prettier auto-formatted away some trailing spaces.

Remove vmware plugin tos (no longer relevant)

Remove vmware plugin eula

Merge pull request #12850 from soapy1/vmware-tos

Remove vmware plugin tos (no longer relevant)

Pass in echo/secret ui input setting

Ensure candidate ips are available when determining mount name

Merge pull request #12834 from danbarr/fix-capitalization

Fix capitalizations in docs

(#12884) Use default ssh.private_key_path when ssh.keys_only = false

Add new config

This will link to the forum to encourage users to post questions there instead of GitHub. This was borrowed from Nomad.

Merge pull request #12890 from kaitlincart/patch-1

Add new config

Bump sdk

Merge pull request #12876 from soapy1/secret-input

Pass in echo/secret ui input setting

Update CHANGELOG.md

Run mod tidy

Merge pull request #12892 from soapy1/mod-tidy

Run mod tidy

Created at 4 days ago
create tag
chrisroberts create tag v2.3.1
Created at 5 days ago

Release 2.3.1

Update files for new development

Created at 5 days ago
chrisroberts delete tag v2.3.1
Created at 5 days ago

Secret interactive input is now supported

ref: https://github.com/hashicorp/vagrant/issues/12865

Add link to all vagrant-go known issues

Merge pull request #12926 from soapy1/update-experimental-go-docs

Update experimental go docs

Release 2.3.1

Update files for new development

Created at 5 days ago
chrisroberts create tag v2.3.1
Created at 5 days ago

Update CHANGELOG

Created at 6 days ago

add new template for eng tasks

Update .github/ISSUE_TEMPLATE/engineering-task.md

Co-authored-by: Sophia Castellarin sophia@hashicorp.com

updates from our backlog session

go generate to pick up input color changes

remove checklists

Merge pull request #12899 from hashicorp/kc.issue-template-new

New Issue Template

Bump sdk

Merge pull request #12917 from soapy1/colored-input

Support colored input prompts

Prevent trailing space character on user agent

Return errors when box metadata is unavailable or invalid

Bump sdk

Merge pull request #12919 from soapy1/box-metadata-errors

Return errors when box metadata is unavailable or invalid

Update CHANGELOG.md

Merge pull request #12925 from chrisroberts/fix-user-agent

Fix downloader user agent

Update CHANGELOG

Created at 6 days ago

Prevent trailing space character on user agent

Merge pull request #12925 from chrisroberts/fix-user-agent

Fix downloader user agent

Created at 6 days ago
delete branch
chrisroberts delete branch fix-user-agent
Created at 6 days ago
closed issue
User-Agent string violates RFC9113

Downloading an image with HTTP/2 results in a message:

HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

I tracked down the issue to the user-agent string that ends with a whitespace character. It is defined in downloader.rb, line 24 as

USER_AGENT = "Vagrant/#{VERSION} (+https://www.vagrantup.com; #{RUBY_ENGINE}#{RUBY_VERSION}) #{ENV['VAGRANT_USER_AGENT_PROVISIONAL_STRING']}".freeze

If no VAGRANT_USER_AGENT_PROVISIONAL_STRING is set, a whitespace is the last character. This violates RFC 9113, Section 8.2.1:

  • A field value MUST NOT start or end with an ASCII whitespace character (ASCII SP or HTAB, 0x20 or 0x09).

    | Note: An implementation that validates fields according to the | definitions in Sections 5.1 and 5.5 of [HTTP] only needs an | additional check that field names do not include uppercase | characters.

    A request or response that contains a field that violates any of these conditions MUST be treated as malformed (Section 8.1.1). In particular, an intermediary that does not process fields when forwarding messages MUST NOT forward fields that contain any of the values that are listed as prohibited above.

Created at 6 days ago
pull request closed
Fix downloader user agent

Prevents a space from being included on the end of the user agent string for the downloader.

Fixes #12921

Created at 6 days ago
pull request opened
Fix downloader user agent

Prevents a space from being included on the end of the user agent string for the downloader.

Fixes #12921

Created at 6 days ago
create branch
chrisroberts create branch fix-user-agent
Created at 6 days ago