Salt 2016.11.0 does not accept link-local IPv6 address in resolv.conf

[Deewiant]

Description of Issue/Question

Some servers of mine have link-local IPv6 addresses in resolv.conf, i.e. lines like nameserver fe80::1234:5678:9abc:def0%eth0. As of 2016.11.0 both master and minion log complaints like the following:

[ERROR   ] /etc/resolv.conf: 'fe80::21b:21ff:fe34:d66a%bond0' does not appear to be an IPv4 or IPv6 address

It doesn't seem to be breaking anything so far, though — just spamming logs. (Perhaps such nameserver addresses were never supported, but now it's more visible?)

Setup

See description

Steps to Reproduce Issue

See description

Versions Report

Salt Version:
           Salt: 2016.11.0

Dependency Versions:
           cffi: Not Installed
       cherrypy: 8.1.2
       dateutil: 2.6.0
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: 0.24.0
           Mako: 1.0.6
   msgpack-pure: Not Installed
 msgpack-python: 0.4.8
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
         pygit2: Not Installed
         Python: 2.7.12 (default, Nov  7 2016, 11:55:55)
   python-gnupg: Not Installed
         PyYAML: 3.12
          PyZMQ: 16.0.0
           RAET: Not Installed
          smmap: Not Installed
        timelib: Not Installed
        Tornado: 4.4.2
            ZMQ: 4.1.5

System Versions:
           dist:
        machine: x86_64
        release: 4.8.6-1-ARCH
         system: Linux
        version: Not Installed

[Ch3LL]

okay it looks like it was added with this pr #22691

It seems that there is some issue with feature compatibiliy generally with using ipv6 local link addresses in /etc/resolv.conf as explained here: http://www.gossamer-threads.com/lists/nsp/ipv6/51213

So it seems we might need to add on our end the ability to support this format of an ipv6 address. Thanks

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[Deewiant]

I still see the exact same error message in the logs with 2018.3.2.

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[isbm]

The fix is not exactly trivial, but... possible: #49705

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.