vagrant-go global-status does not output anything but the Experimental Warning

[JasonD94]

Debug output

Debug output can be found in this gist: https://gist.github.com/JasonD94/9342270bc722444ea9035dafe3c25291

Expected behavior

Vagrant global status output, like from the normal vagrant global-status command, should be outputted to the console.

Actual behavior

All that is outputted is:

This is an experimental version of Vagrant. Please note that some things may
not work as you expect and this version of Vagrant is not compatible with the
stable version of Vagrant. For more information about vagrant-go read the docs
at https://www.vagrantup.com/docs/experimental/vagrant_go. To disable this
warning set the environment variable 'VAGRANT_SUPPRESS_GO_EXPERIMENTAL_WARNING'.

Reproduction information

Vagrant version

Vagrant 2.4.1

Host operating system

Fedora Linux 40 (KDE Plasma) running Linux 6.8.9-300.fc40.x86_64

Guest operating system

None involved for this command, but I use Rocky VMs for development.

Steps to reproduce

1. Run vagrant-go global-status like shown on the vagrant-go docs page: https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go
2. See that the "Experimental Warning" is printed out:

This is an experimental version of Vagrant. Please note that some things may
not work as you expect and this version of Vagrant is not compatible with the
stable version of Vagrant. For more information about vagrant-go read the docs
at https://www.vagrantup.com/docs/experimental/vagrant_go. To disable this
warning set the environment variable 'VAGRANT_SUPPRESS_GO_EXPERIMENTAL_WARNING'.

3. But nothing further prints, even after waiting a few minutes. Using --debug, see that warnings and logs about context cancelled and plugin exited are printed like:

2024-05-17T10:07:15.250-0400 [INFO]  vagrant.server.grpc: /hashicorp.vagrant.Vagrant/FindBasis response: error="rpc error: code = NotFound desc = failed to locate basis (record not found)" duration="141.327µs"
2024-05-17T10:07:15.250-0400 [WARN]  vagrant-go: context cancelled, stopping interrupt listener loop
2024-05-17T10:07:15.250-0400 [DEBUG] vagrant.plugin.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-05-17T10:07:15.250-0400 [DEBUG] vagrant.plugin.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-05-17T10:07:15.250-0400 [DEBUG] vagrant.plugin.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: read unix @->/tmp/plugin503719700: read: connection reset by peer"
2024-05-17T10:07:15.251-0400 [DEBUG] vagrant.plugin.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-05-17T10:07:15.252-0400 [INFO]  vagrant.plugin: plugin process exited: path=/opt/vagrant/bin/vagrant-go pid=21018
2024-05-17T10:07:15.252-0400 [DEBUG] vagrant.plugin: plugin exited
2024-05-17T10:07:15.252-0400 [INFO]  vagrant.plugin: plugin process exited: path=/opt/vagrant/bin/vagrant-go pid=21041
2024-05-17T10:07:15.252-0400 [DEBUG] vagrant.plugin: plugin exited
2024-05-17T10:07:15.252-0400 [INFO]  vagrant.plugin: plugin process exited: path=/opt/vagrant/bin/vagrant-go pid=20993
2024-05-17T10:07:15.253-0400 [DEBUG] vagrant.plugin: plugin exited
2024-05-17T10:07:15.253-0400 [INFO]  vagrant.plugin: plugin process exited: path=/opt/vagrant/bin/vagrant-go pid=20972
2024-05-17T10:07:15.253-0400 [DEBUG] vagrant.plugin: plugin exited
2024-05-17T10:07:17.255-0400 [WARN]  vagrant.legacy: plugin failed to exit gracefully

Vagrantfile

I ran this command in my home (~/) directory, so no vagrantfile is present. Output from vagrant global-status works just fine this way:

jdowning@fedora:jdowning$ vagrant global-status
id       name   provider   state    directory
---------------------------------------------------------------------------
d015610  dev    virtualbox running  /home/jdowning/Git/<repo>
782db75  cm_dev virtualbox poweroff /home/jdowning/Git/<repo>
7f892b2  dev    virtualbox poweroff /home/jdowning/Git/<repo>
cd485b2  dev    virtualbox poweroff /home/jdowning/Git/<repo>
7a5af9e  dev    virtualbox poweroff /home/jdowning/Git/<repo>
c68cb5c  dev    virtualbox poweroff /home/jdowning/Git/<repo>
f5d80b7  dev    virtualbox poweroff /home/jdowning/Git/<repo>
fb6f4da  dev    virtualbox running  /home/jdowning/Git/<repo>

The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"

[JasonD94]

I think I did not fully read the docs: https://developer.hashicorp.com/vagrant/docs/experimental/vagrant_go#data-directories

But, I would also expect to get an error if I failed to setup a basis. I would think an error log in here would help: https://github.com/hashicorp/vagrant/blob/main/internal/cli/base.go#L271

Will play around with this a bit more.