Skip to content

[BUG][Debian11][resolvconf] Please update symlink path for debian11/resolvconf #36

@Yoda-BZH

Description

@Yoda-BZH

Your setup

Formula commit hash / release tag

Using formula at 57fca1d

Versions reports (master & minion)

$ salt-minion --versions-report
Salt Version:
          Salt: 3002.6
 
Dependency Versions:
          cffi: Not Installed
      cherrypy: Not Installed
      dateutil: 2.8.1
     docker-py: Not Installed
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 2.11.3
       libgit2: Not Installed
      M2Crypto: 0.37.1
          Mako: Not Installed
       msgpack: 1.0.0
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     pycparser: Not Installed
      pycrypto: Not Installed
  pycryptodome: 3.9.7
        pygit2: Not Installed
        Python: 3.9.2 (default, Feb 28 2021, 17:03:44)
  python-gnupg: Not Installed
        PyYAML: 5.3.1
         PyZMQ: 20.0.0
         smmap: Not Installed
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.3.4
 
System Versions:
          dist: debian 11 bullseye
        locale: utf-8
       machine: x86_64
       release: 5.10.0-6-amd64
        system: Linux
       version: Debian GNU/Linux 11 bullseye

Salt syndic:

# salt --versions-report
Salt Version:
          Salt: 3002.6
 
Dependency Versions:
          cffi: Not Installed
      cherrypy: Not Installed
      dateutil: 2.7.3
     docker-py: Not Installed
         gitdb: 2.0.5
     gitpython: 2.1.11
        Jinja2: 2.10
       libgit2: Not Installed
      M2Crypto: 0.31.0
          Mako: Not Installed
       msgpack: 0.5.6
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     pycparser: Not Installed
      pycrypto: 2.6.1
  pycryptodome: 3.6.1
        pygit2: Not Installed
        Python: 3.7.3 (default, Jan 22 2021, 20:04:44)
  python-gnupg: Not Installed
        PyYAML: 3.13
         PyZMQ: 17.1.2
         smmap: 2.0.5
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.3.1
 
System Versions:
          dist: debian 10 buster
        locale: UTF-8
       machine: x86_64
       release: 4.19.0-16-amd64
        system: Linux
       version: Debian GNU/Linux 10 buster

Pillar / config used

{% set use_resolvconf = false %}
{% if __grains__.get('os') == 'Debian' %}
{%   if __grains__.get('osmajorrelease', 0) >= 11 %}
{%     set use_resolvconf = true %}
{%   endif %}
{% endif %}


{% if use_resolvconf %}
states:
  list:
    - resolver.ng
{% endif %}

resolver:

  domain: example.com
  nameservers: {{ dnsservers | json }}

Bug details

Describe the bug

When applying:

local:
----------
          ID: resolv-file
    Function: file.managed
        Name: /etc/resolvconf/resolv.conf.d/base
      Result: True
     Comment: File /etc/resolvconf/resolv.conf.d/base updated
     Started: 13:06:06.671173
    Duration: 25.268 ms
     Changes:   
              ----------
              diff:
                  --- 
                  +++ 
                  @@ -1,5 +1,6 @@
                  -# THIS FILE IS MANAGED BY SALTSTACK
                  -# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
                  +# Dynamic resolv.conf(5) file for glibc resolver(3) generated by salt-minion(1)
                  +#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
                   domain example.com
                  +search example.com 
                   nameserver 192.0.2.1
                   nameserver 192.0.2.2
----------
          ID: resolv-update
    Function: cmd.run
        Name: resolvconf -u
      Result: True
     Comment: Command "resolvconf -u" run
     Started: 13:06:06.699972
    Duration: 21.766 ms
     Changes:   
              ----------
              pid:
                  36785
              retcode:
                  0
              stderr:
                  /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
              stdout:

$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 31 May 18 11:56 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf

Steps to reproduce the bug

Expected behaviour

in debian 11 with resolvconf, managed symlink should point to /run/resolvconf/resolv.conf

Attempts to fix the bug

forcing with:

resolver:
  ng:
    resolvconf:
      file: /run/resolvconf/resolv.conf

should work, but it should be automatic.

Additional context

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions