vagrant/test/unit/plugins
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
..
commands Update tests for checksum and filechecksum 2019-10-08 11:23:48 -07:00
communicators Always ensure remote destination directory exists 2019-02-26 08:54:49 -08:00
guests explicitly test the hostname we'll be setting 2019-11-01 15:41:04 +01:00
hosts Ensure nfsd call is mocked up in BSD NFS test 2019-10-25 09:02:30 -07:00
kernel_v2/config Merge pull request #10664 from chrisroberts/f-plugin-config-format 2019-02-12 10:00:14 -08:00
providers Add test for listing interfaces with docker networks 2019-10-10 11:38:57 -07:00
provisioners Update tests for checksum and filechecksum 2019-10-08 11:23:48 -07:00
pushes Provide custom error when attempting to push too many files with FTP 2018-06-26 08:28:01 -07:00
synced_folders Fixes #10966: Ensure all subdirectory files are watched 2019-09-26 08:29:37 -07:00