vagrant/plugins/guests/suse/cap
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
..
change_host_name.rb explicitly test the hostname we'll be setting 2019-11-01 15:41:04 +01:00
configure_networks.rb guests/linux: Add shared cap for listing network interfaces 2016-07-18 21:12:54 -04:00
halt.rb guests: Prevent ssh disconnect from causing error on halt 2016-08-12 13:25:39 -07:00
network_scripts_dir.rb Fixed and extended suse guest capabilities 2014-09-11 17:07:49 +02:00
nfs_client.rb Update nfs & service daemon names for suse based hosts 2019-09-18 23:28:18 +02:00
rsync.rb guests/suse: Configure rsync in one command 2016-06-06 11:58:42 -04:00