vagrant/plugins/guests/suse
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
..
cap explicitly test the hostname we'll be setting 2019-11-01 15:41:04 +01:00
guest.rb guests/suse: Do not require vagrant in guest 2016-06-06 11:58:43 -04:00
plugin.rb Use symbols for defining guest capabilities 2016-06-17 19:55:04 -04:00