Comment # 5 on bug 1115000 from Robert Schweikert

Everything as far as cloud-init is concerned appears to be behaving as
expected.

The config at
https://build.opensuse.org/package/view_file/openSUSE:Factory/cloud-init-config-caasp/cloud.cfg?expand=1
contains:

datasource_list: [ LocalDisk, NoCloud, OpenStack, None ]

where local disk is our own DataSource implementation and carried as a patch as
have had no time yet to investigate differences to NoCloud. ANyway, the code
looks for the data sources and cannot find them, from the log:

2018-11-07 10:50:20,208 - handlers.py[DEBUG]: finish:
init-local/search-LocalDisk: SUCCESS: no local data found from
DataSourceLocalDisk

2018-11-07 10:50:20,911 - handlers.py[DEBUG]: finish:
init-local/search-NoCloud: SUCCESS: no local data found from DataSourceNoCloud

2018-11-07 10:50:20,936 - handlers.py[DEBUG]: finish:
init-local/search-OpenStackLocal: SUCCESS: no local data found from
DataSourceOpenStackLocal

2018-11-07 10:50:38,142 - cc_resolv_conf.py[DEBUG]: Skipping module named
resolv_conf, no 'manage_resolv_conf' key in configuration

And /cloud-init-config on the system in question is empty:

# ls /cloud-init-config/
# 

The cloud.cfg contains:

 - resolv_conf

as a configuration module and the module is executed as expected; from the log:

2018-11-07 10:50:38,142 - cc_resolv_conf.py[DEBUG]: Skipping module named
resolv_conf, no 'manage_resolv_conf' key in configuration

The cloud.cfg does not contain any information about how to setup resolve.conf
and since no data sources are found there is no information about resolve.conf
available form the data sources. Therefore, the template file is put in place
with no name resolution information.

Setting up name resolution is configured with the following syntax:

    manage_resolv_conf: <true/false>
    resolv_conf:
        nameservers: ['8.8.4.4', '8.8.8.8']
        searchdomains:
            - foo.example.com
            - bar.example.com
        domain: example.com
        options:
            rotate: <true/false>
            timeout: 1

>From my point of view this is a configuration issue, or a missing data source
attachment in the test scenarion, but cloud-init behaves as designed.