nameserver is not set correctly in the appliance

Bug #1496866 reported by Rosario Di Somma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Astara
New
Undecided
Unassigned

Bug Description

According to the ansible playbook the 'nameserver' option in resolv.conf should be set to 8.8.8.8 but it is instead set to value of the nameserver of the machine where the image is built.

Revision history for this message
Rosario Di Somma (mr-rods) wrote :

Seems like dib finds a resolv.conf file in the TMP_MOUNT_PATH/etc folder so it makes a copy https://github.com/openstack/diskimage-builder/blob/master/lib/common-functions#L256, uses the system configured resolv.conf if available https://github.com/openstack/diskimage-builder/blob/master/lib/common-functions#L264 and then restores the copy https://github.com/openstack/diskimage-builder/blob/master/lib/img-functions#L108. Unfortunately the restore is done after the cleanup phase so there are not available hooks to use to fix the issue cleanly.

Changed in akanda:
milestone: none → liberty-rc1
Changed in astara:
milestone: none → liberty-rc1
Changed in astara:
milestone: liberty-rc1 → 7.0.0
Changed in akanda:
milestone: liberty-rc1 → 7.0.0
Changed in astara:
milestone: 7.0.0 → none
Changed in akanda:
milestone: 7.0.0 → none
no longer affects: akanda
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.