Public bug reported:
[cloud-init] "/etc/resolv.conf" is out of control of netconfig after
done cloud-init GOSC on SLES15SP1
Before GOSC, "/etc/resolv.conf" is link file
"/run/netconfig/resolv.conf", in control by netconfig. After done cloud-
init GOSC, this file become real file not link file, total different
from "/run/netconfig/resolv.conf".
cloud-init version is 19.4.
```
pek2-gosv-16-dhcp83:~ # cloud-init -v
/usr/bin/cloud-init 19.4
```
Before GOSC:
```
pek2-gosv-16-dhcp83:~ # ll /etc/resolv.conf
lrwxrwxrwx 1 root root 26 Feb 10 23:33 /etc/resolv.conf ->
/run/netconfig/resolv.conf
```
After GOSC:
```
pek2-gosv-16-dhcp83:~ # ll /etc/resolv.conf
-rw-r--r-- 1 root root 153 Feb 11 09:46 /etc/resolv.conf
pek2-gosv-16-dhcp83:~ # ll /run/netconfig/resolv.conf
-rw-r--r-- 1 root root 707 Feb 14 06:10 /run/netconfig/resolv.conf
```
cloud-init.log is attached.
Steps:
1. Deploy SLES15SP1 VM
2. Power off VM and Deploy GOSC
```
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: FOUND CATEGORY = 'NETWORK'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|NETWORKING' = 'yes'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|BOOTPROTO' = 'dhcp'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|HOSTNAME' = 'gosc-dhcp-vm-01'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|DOMAINNAME' = 'eng.vmware.com'
...
```
3. Power on VM and check GOSC resolve, expect /etc/resolv.conf is still link to
/run/netconfig/resolv.conf and DNS setting is saved into this file.
** Affects: cloud-init
Importance: Undecided
Status: New
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/bugs/1863203/+attachment/5328104/+files/cloud-init.log
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1863203
Title:
[cloud-init] "/etc/resolv.conf" is out of control of netconfig after
done cloud-init GOSC on SLES15SP1
Status in cloud-init:
New
Bug description:
[cloud-init] "/etc/resolv.conf" is out of control of netconfig after
done cloud-init GOSC on SLES15SP1
Before GOSC, "/etc/resolv.conf" is link file
"/run/netconfig/resolv.conf", in control by netconfig. After done
cloud-init GOSC, this file become real file not link file, total
different from "/run/netconfig/resolv.conf".
cloud-init version is 19.4.
```
pek2-gosv-16-dhcp83:~ # cloud-init -v
/usr/bin/cloud-init 19.4
```
Before GOSC:
```
pek2-gosv-16-dhcp83:~ # ll /etc/resolv.conf
lrwxrwxrwx 1 root root 26 Feb 10 23:33 /etc/resolv.conf ->
/run/netconfig/resolv.conf
```
After GOSC:
```
pek2-gosv-16-dhcp83:~ # ll /etc/resolv.conf
-rw-r--r-- 1 root root 153 Feb 11 09:46 /etc/resolv.conf
pek2-gosv-16-dhcp83:~ # ll /run/netconfig/resolv.conf
-rw-r--r-- 1 root root 707 Feb 14 06:10 /run/netconfig/resolv.conf
```
cloud-init.log is attached.
Steps:
1. Deploy SLES15SP1 VM
2. Power off VM and Deploy GOSC
```
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: FOUND CATEGORY = 'NETWORK'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|NETWORKING' = 'yes'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|BOOTPROTO' = 'dhcp'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|HOSTNAME' = 'gosc-dhcp-vm-01'
2020-02-11 08:46:34,797 - config_file.py[DEBUG]: ADDED KEY-VAL ::
'NETWORK|DOMAINNAME' = 'eng.vmware.com'
...
```
3. Power on VM and check GOSC resolve, expect /etc/resolv.conf is still link
to /run/netconfig/resolv.conf and DNS setting is saved into this file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1863203/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
