vagrant/test
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
..
acceptance Add box from local path and use generic name 2017-03-09 12:44:10 -08:00
config Add `rake acceptance:boxes` to download required boxes for tests 2011-11-13 13:37:30 -08:00
support Spelling fixes 2018-03-14 14:41:04 +00:00
unit explicitly test the hostname we'll be setting 2019-11-01 15:41:04 +01:00
vagrant-spec Extend assert retries to allow for slow setup 2018-10-11 13:00:44 -07:00