vagrant/test/unit
Christoph Moench-Tegeder 6f6e58f4ae explicitly test the hostname we'll be setting
getent queries the system resolver for the hostname - but it's not
the resolver we're interested in. In fact, the hostname-to-be-set
may already exist in DNS (becuase DNS really is a nifty thing and
can do a lot of things which are not that possible with /etc/hosts
alone), in which case getent will "not fail" and vagrant will believe
the hostname had already been set.
Instead, query hostnamectl for the "static" hostname - that's the
one we will be setting, so we're ok IFF hostnamectl returns exactly
what we would be setting.
2019-11-01 15:41:04 +01:00
..
bin Add coverage on vagrantfile_name stubbing behavior 2018-07-18 10:50:41 -07:00
plugins explicitly test the hostname we'll be setting 2019-11-01 15:41:04 +01:00
support Remove virtualbox context from docker tests 2019-09-11 07:46:40 -07:00
templates Add ipv6 network config templates for SUSE based distributions 2019-08-09 17:23:46 +02:00
vagrant Add coverage on new behavior of FileChecksum 2019-10-08 11:23:48 -07:00
base.rb Only run tests that require bsdtar if it is available 2019-06-19 15:29:55 -07:00
vagrant_test.rb add `Vagrant.version?` helper method 2018-09-07 11:37:30 +02:00