Invalid Vagrantfile path and error line number reported, error reporting inconsistent

[ferenczy]

Vagrant is reporting errors in Vagrantfile inconsistently and in some cases, the Vagrantfile path and the error line number are reported wrong.

Vagrant version

2.2.5 (64-bit)

Host operating system

Windows 7 Ultimate 64-bit

Vagrantfile

I have tested 4 different contents of the Vagrantfile. All of them contain an error of using an undefined variable or a syntax error, each time in a different scope, each time producing different (and in 2 cases wrong) Vagrantfile path and error line number report.

Case 1

vb.memory = "4096"

Case 2

Vagrant.configure("2") do |config|
  vb.memory = "4096"
end

Case 3

Vagrant.configure("2") do |config|
  config.vm.provider "virtualbox" do |vb|
      xvb.memory = "4096"
  end
end

Case 4

# test
abcd(

Expected behavior

Both the Vagrantfile path and the error line number are properly reported and ideally in the same format.

Actual behavior

Case 1

In this case, both the Vagrantfile path and the error line number are properly reported:

$ vagrant status
Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: D:/work/memsource/vagrant/Vagrantfile
Line number: 1
Message: NameError: undefined local variable or method `vb' for main:Object

Case 2

In this case, the error line number is reported right, but Vagrantfile path is not:

$ vagrant status
Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
an invalid or undefined variable.

Path: D
Line number: 2
Message: undefined local variable or method `vb'

Case 3

In this case, both the Vagrantfile path and the error line number seems to be wrong. The path looks like a code block specification where the error occurred and the error line number contains a broken Vagrantfile path (the proper path would be D:/work/memsource/vagrant/Vagrantfile as reported in the Case 1):

$ vagrant status
Vagrant failed to initialize at a very early stage:

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: <provider config: virtualbox>
Line number: /work/memsource/vagrant/Vagrantfile
Message: NameError: undefined local variable or method `xvb' for main:Object

Case 4

This time, both Vagrantfile path and the error line number are right, but together with the error message, they're reported differently:

$ vagrant status
Vagrant failed to initialize at a very early stage:

There is a syntax error in the following Vagrantfile. The syntax error
message is reproduced below for convenience:

D:/work/memsource/vagrant/Vagrantfile:2: syntax error, unexpected end-of-input, expecting ')'

Steps to reproduce

1. Create a Vagrantfile
2. Run vagrant status in the same directory

[briancain]

Hi @ferenczy - thanks for the detailed report!

I think case 2 is covered by #10924, but from the looks of it these cases can also be included in the fix since they are probably related/in the same area of code.

[ferenczy]

OK, thank you for the information @briancain. Good to hear the fix is on its way :)

BTW similar issue (#6445) also has been reported and fixed about 4 years ago.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.