View Issue Details

IDProjectCategoryView StatusLast Update
0016666CentOS-7Cloud-Imagespublic2019-10-28 13:30
Reporterlittlesandra88 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version7.7-1908 
Target VersionFixed in Version 
Summary0016666: Reproducable "could not resolve host" on Linux with libvirt and virtualbox
DescriptionI can reproduce the bug mentioned in point 4 in the release notes for CentOS Vagrant Images Available (v1905.01) on both Vagrant with libvirt and VirtualBox.

Some people reported "could not resolve host" errors when running the centos/7 image for VirtualBox on Windows hosts. We don't have access to any Windows computer, but some people reported that adding the following line to the Vagrantfile fixed the problem:

vb.customize ["modifyvm", :id, "--natdnshostresolver1", "off"]

https://blog.centos.org/2019/07/updated-centos-vagrant-images-available-v1905-01/
Steps To ReproduceFor Vagrant with libvirt use

```
Vagrant.configure("2") do |config|

  config.vm.provider :libvirt do |libvirt|
    libvirt.driver = "kvm"
    libvirt.host = 'localhost'
    libvirt.uri = 'qemu:///system'
    libvirt.management_network_device = 'virbr0'

    libvirt.storage_pool_name = "default"
  end

  config.vm.define "test1" do |vm1|
     vm1.vm.box = "centos/7"
     vm1.vm.hostname = "vm1.example.com"
     vm1.vm.provider :libvirt do |domain|
       domain.memory = 1024
       domain.cpus = 1
     end

     vm1.vm.network :private_network,
                    :ip => '192.168.122.15',
                    :libvirt__netmask => '255.255.255.0',
                    :libvirt__network_name => 'default',
                    :libvirt__forward_mode => 'none'
  end
end
```

For Vagrant with VirtualBox use

```
Vagrant.configure("2") do |config|
  config.vm.box = "centos/7"

  config.vm.define "test1" do |vm1|
     vm1.vm.hostname = "vm1.example.com"
     vm1.vm.provider 'virtualbox' do |domain|
       domain.memory = 1024
       domain.cpus = 1
     end

     vm1.vm.network 'private_network', ip: "192.168.234.229"
  end

end
```

In each of them execute
```
curl https://github.com/docker/compose/releases/download/1.23.2/docker-compose-Linux-x86_64
```

approx 15 times, and you will notice the DNS is extremely slow and sometimes can't resolve at all.

Using an Ubuntu image instead with the same Vafrantfile's works perfectly.
Additional InformationHost machine default Fedora 30.
Tagsvagrant
abrt_hash
URL

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-10-28 13:30 littlesandra88 New Issue
2019-10-28 13:30 littlesandra88 Tag Attached: vagrant