Opened 5 years ago

Closed 5 years ago

#333 closed defect (worksforme)

host_name does not exist anymore in Vagrantfile v2

Reported by: greiner Assignee:
Priority: P2 Milestone:
Module: Infrastructure Keywords: vagrant
Cc: Blocked By:
Blocking: Platform:
Ready: no Confidential: no
Tester: Verified working: no
Review URL(s):

Description

Environment

Ubuntu 13.10
infrastructure rev436
Vagrant 1.2.2
VirtualBox 4.2.16

How to reproduce

  1. Get infrastructure repository
  2. Run vagrant up filter1 in the repository directory

Observed behaviour

Startup stopped and getting an error message instead:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The following settings don't exist: host_name

Expected behaviour

Vagrant starts filter1.

Approach

Vagrantfile v2 renamed config.vm.host_name to config.vm.hostname which was not included when we made the switch to v2.

Change History (2)

comment:1 Changed 5 years ago by poz2k4444

I've tried to reproduce the error in this changeset, which is the last one in the official mercurial repo

changeset: 436:9c195d8d3453

With my enviornment:

Ubuntu 12.04.3
VirtualBox 4.1.12
Vagrant 1.5.1

And it runs without problems, maybe it's already fixed

comment:2 Changed 5 years ago by philll

  • Resolution set to worksforme
  • Status changed from new to closed

Same here, no issues at all when starting up filter1 with
Debian wheezy
Vagrant 1.5.2
Virtualbox 4.1.18

Feel free to reopen the issue if more information about the reliable reporoducability is available.

Note: See TracTickets for help on using tickets.