Bug ID 1115000
Summary cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Cloud:Tools
Assignee public-cloud-maintainers@suse.de
Reporter rbrown@suse.com
QA Contact qa-bugs@suse.de
CC kubic-bugs@opensuse.org
Found By ---
Blocker ---

cloud-init do not seem to correctly populate /etc/resolv.conf 

After a boot of Kubic with the kubeadm system role, the resulting
/etc/resolv.conf has "; Created by cloud-init on instance boot automatically,
do not edit" followed by the usual "### /etc/resolv.conf file autogenerated by
netconfig" preamble, but has no name resolver configured

This results in a system that has no working name resolution

https://openqa.opensuse.org/tests/788925#step/first_boot/23

All other networking seems to behave fine

EXPECTED BEHAVIOUR
cloud-init should correctly populate /etc/resolv.conf when configuring the
network of a system

WORKAROUND
docker automatically disables cloud-inits network configuration by editing
/etc/cloud/cloud.cfg.d/01-network.cfg - for non-docker runtimes Kubic intends
to do something similar until this bug is fixed at least.


You are receiving this mail because: