Closed fatmcgav closed 7 years ago
I think this might be related with your upgrade to Vagrant 1.8.6. I have seen a similar behavior as well. I need to investigate.
@hferentschik Cheers for the update. I'll try rolling Vagrant back to 1.8.5 and see if it resolves...
@fatmcgav could you test a gem for me. You can download it from this AppVeyor CI build - https://ci.appveyor.com/project/hferentschik/landrush-3agrx/build/artifacts
You can install it via:
$ vagrant plugin install <path to gem>
For all I can tell, this works with Vagrant 1.8.6, but I'd like to get a second opinion.
@hferentschik sure, I'll give it a go tomorrow and report back...
sure, I'll give it a go tomorrow and report back...
Awesome, thanks.
@hferentschik Sorry for the delay in testing...
Installed the 1.2.0.dev version this morning, and it starts correctly, local and VM DNS resolution works...
So big 👍 from me :)
Cheers
@fatmcgav Thanks for testing. I'll merge it asap and try to cut a new release. There is one more outstanding issue I would like to get merged.
Fixed via pull request #288
I have Vagrant v1.8.6 installed on Mac OS X v10.11 and tried to update Landrush to v1.2.0 and got the same issue described at the beginning of this issue. I ended up having to rollback Landrush to v0.19.0 in order to get it to work correctly. Can anyone confirm that v1.2.0 is actually working with Vagrant v1.8.6?
Morning all
I've just updated Landrush to v1.1.2, from a pre 1.x version. However Landrush is now failing to start, with no obvious cause.
But there's no 'landrush.log' for me to review :(
I've tried uninstalling and reinstalling Landrush with no change in behaviour. Nothing of any use in system.log.
Any pointers on how to investigate?