Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

state for network.system fails #11164

Closed
drzero42 opened this issue Mar 12, 2014 · 40 comments
Closed

state for network.system fails #11164

drzero42 opened this issue Mar 12, 2014 · 40 comments
Labels
Bug broken, incorrect, or confusing behavior severity-low 4th level, cosemtic problems, work around exists stale
Milestone
Approved

Comments

@drzero42
Copy link
Contributor

I am testing out network management in Salt 2014.1.0 on Ubuntu 12.04 machines. I have pretty much just grabbed the examples from the documentation:

system:
  network.system:
    - enabled: True
    - hostname: thinclient-admin.dsl.lan
    - gateway: 10.17.4.1
    - gatewaydev: eth0
    - nozeroconf: True
    - require_reboot: True

eth0:
  network.managed:
    - enabled: True
    - type: eth 
    - proto: none
    - ipaddr: 10.17.4.9
    - netmask: 255.255.255.0
    - dns:
      - 10.16.4.4

The system stanza fails with this traceback:

          ID: system
    Function: network.system
      Result: False
     Comment: An exception occurred in this state: Traceback (most recent call last):
                File "/usr/lib/pymodules/python2.7/salt/state.py", line 1371, in call
                  **cdata['kwargs'])
                File "/usr/lib/pymodules/python2.7/salt/states/network.py", line 380, in system
                  new = __salt__['ip.build_network_settings'](**kwargs)
                File "/usr/lib/pymodules/python2.7/salt/modules/debian_ip.py", line 1461, in build_network_settings
                  opts = _parse_network_settings(settings, current_network_settings)
                File "/usr/lib/pymodules/python2.7/salt/modules/debian_ip.py", line 1002, in _parse_network_settings
                  opts['networking'] = current['networking']
              KeyError: 'networking'
@basepi
Copy link
Contributor

basepi commented Mar 14, 2014

Thanks for the report, we'll investigate.

Just FYI, the Debian/Ubuntu network support is very new (has only been out for the 2014.1.0 release) and may still have some bugs to work out.

@basepi basepi added this to the Outstanding Bugs milestone Mar 14, 2014
@drzero42
Copy link
Contributor Author

I am fully aware that it is still listed as being new and not at all mature. It is just a feature I have been waiting for, and thus wanted to test it right away, when it was introduced.

@basepi
Copy link
Contributor

basepi commented Mar 19, 2014

Awesome! We love people who are willing to test new features! Just wanted to make sure you were aware. =)

@drzero42
Copy link
Contributor Author

No problem. Let me know if I can do anything to help debug the problem.

@garethgreenaway
Copy link
Contributor

Will check this out.

@garethgreenaway
Copy link
Contributor

Found the cause. I'm an idiot :) the network.system bit didn't get finished. Looking at finishing it now.

@garethgreenaway garethgreenaway mentioned this issue Mar 21, 2014
Merged
@garethgreenaway
Copy link
Contributor

@drzero42 Would you be able to test the latest develop branch and see if the issue was resolved?

@jleroy
Copy link
Contributor

jleroy commented Mar 24, 2014

@garethgreenaway Pull request #11401 has resolved this issue on my minions.

@garethgreenaway
Copy link
Contributor

Awesome!

@drzero42
Copy link
Contributor Author

Sorry for the delay. I have now tested and it partially fixed the problem. Now I get this output:

      ID: system
Function: network.system
  Result: False
 Comment: /etc/default/networking cannot be written. /etc/default/networking does not exist
 Changes:

It is true that /etc/default/networking. This file is not present on any of the Ubuntu 12.04 systems that I have checked. Perhaps the way to configure networking on Debian isn't exactly the same as on Ubuntu?

@garethgreenaway
Copy link
Contributor

Thanks. Will spin up an ubuntu and test.

On March 25, 2014 6:31:49 AM PDT, Anders Bruun Olsen notifications@github.com wrote:

Sorry for the delay. I have now tested and it partially fixed the
problem. Now I get this output:

     ID: system

Function: network.system
Result: False
Comment: /etc/default/networking cannot be written.
/etc/default/networking does not exist
Changes:

It is true that /etc/default/networking. This file is not present on
any of the Ubuntu 12.04 systems that I have checked. Perhaps the way to
configure networking on Debian isn't exactly the same as on Ubuntu?

Reply to this email directly or view it on GitHub:
#11164 (comment)

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

@garethgreenaway
Copy link
Contributor

Looks like Ubuntu moved away from having /etc/default/networking, looking into what it was replaced with.

@garethgreenaway garethgreenaway mentioned this issue Mar 25, 2014
Merged
@garethgreenaway
Copy link
Contributor

No replacement for /etc/default/networking so when networking is disabled I'm disabling networking related services, eg. NetworkManager and networking.

@garethgreenaway
Copy link
Contributor

Merged into latest develop. @drzero42 Can you test again? Thanks!

@drzero42
Copy link
Contributor Author

It works now. Although it creates /etc/default/networking, which is kind of pointless on an Ubuntu system. Should default not be to NOT create it, if it isn't there?

@garethgreenaway
Copy link
Contributor

Older Ubuntu system which are still supported still use that file. Its benign on the newer systems.

On March 27, 2014 2:01:47 AM PDT, Anders Bruun Olsen notifications@github.com wrote:

It works now. Although it creates /etc/default/networking, which is
kind of pointless on an Ubuntu system. Should default not be to NOT
create it, if it isn't there?

Reply to this email directly or view it on GitHub:
#11164 (comment)

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

@drzero42
Copy link
Contributor Author

Fair enough. I just figured that if a system uses /etc/default/networking, it would exist already when salt is run. Meaning that a default of not creating it, if it does not exist, seems smarter to me. But since it is indeed benign, I won't push the issue :)

@garethgreenaway
Copy link
Contributor

True. Going to look at this more, having files left over that aren't used isn't good practice either.

@basepi basepi modified the milestones: Approved, Outstanding Bugs Apr 21, 2014
@westurner
Copy link
Contributor

@garethgreenaway
Will these bugfixes ( #11522 , #11401 ) make it into Helium and/or a 2014.1.4?

@westurner
Copy link
Contributor

I could template these out myself, but this is a major blocker for me.

@garethgreenaway
Copy link
Contributor

Can chat with some folks tomorrow and see if they can make there way into 2014.1.4 though it sounds like Helium isn't far off.

@garethgreenaway
Copy link
Contributor

@westurner #11522 made it into 2014.1.3, #11401 should make it into 2013.1.4.

@cachedout
Copy link
Contributor

@garethgreenaway Thanks as always for your great work here! The release concerns aside, is this issue ready to be closed?

@garethgreenaway
Copy link
Contributor

@cachedout Should be ready to be closed. The original issue was fixed as reported byt @drzero42 and the issue of straggling files was fixed as well.

@cachedout
Copy link
Contributor

@garethgreenaway Thanks for your quick response here. I'll go ahead and close this. If there are lingering concerns from anybody, please feel free to leave a comment on this issue and we can re-open it if necessary. Thanks all!

@westurner
Copy link
Contributor

network.system doesn't fail, but runs every time.

  • Ubuntu 12.04 latest
  • Salt develop branch
  • Vagrant shell provisioner
  • NAT, Bridged, Internal Host Only

With this:

system:
  network.system:
    - enabled: True
    - hostname: hostname.example
    - gateway: 10.10.10.10
    - gatewaydev: eth1
    - nozeroconf: True
    - nisdomain: hostname.example
    - require_reboot: True

I have this output with every invocation:

----------
          ID: system
    Function: network.system
      Result: True
     Comment: Global network settings are up to date.
     Changes:   
              ----------
              network_settings:
                  --- 
                  +++ 
                  @@ -2,7 +2,7 @@
                   # the boot sequence

                   # Set to 'no' to skip interfaces configuration on boot
                  -CONFIGURE_INTERFACES=no
                  +CONFIGURE_INTERFACES=yes

                   # Don't configure these interfaces. Shell wildcards supported/
                   #EXCLUDE_INTERFACES=

Afterwards:

  • /etc/default/networking does not exist (it doesn't need to w/ 12.04)
  • The default gateway route is not set
  • Every invocation of network.system returns True

@westurner
Copy link
Contributor

Thanks @garethgreenaway!

@westurner
Copy link
Contributor

In debian_ip, I will finish up patches to add dns-search, fix "bridgeing -> bridging", and this issue.

@drzero42
Copy link
Contributor Author

I just tried out networking in states with Salt 2014.1.5. /etc/default/networking got created on Ubuntu 12.04, which it shouldn't be. Also gateway does not get set, making network states useless on Ubuntu still. Should I create a new issue for this, or should this issue be reopened?

@garethgreenaway
Copy link
Contributor

@drzero42 alot of the fixes have gone into develop and should be in the Helium release. If possible could you test develop and see if your issue is resolved?

@timwsuqld
Copy link

@drzero42 @garethgreenaway
My testing of 2016.3.2 suggests that this still hasn't been fixed for Ubuntu. I get no gateway route.

@westurner
Copy link
Contributor

@timwsuqld can you paste cfg that causes the error,
and then run with debug logging in order to get the traceback around the network.system calls?

@timwsuqld
Copy link

My State

system:
  network.system:
    - enabled: True
    - hostname: test1.suqld.org.au
    - require_reboot: True
    - gateway: 10.1.37.254
    - gatewaydev: ens192

/etc/hostname:
  file.managed:
    - contents: test1
    - backup: false

Docs suggest (and it works on Centos machines) that I can define gateway and gatewaydev here. Doing so doesn't give me a default route under Ubuntu.

Debug output

sudo salt-call -l debug state.sls networking.hostname
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf'
[DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf
[DEBUG   ] Configuration file path: /etc/salt/minion
[WARNING ] Insecure logging configuration detected! Sensitive data may be logged.
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf'
[DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf
[DEBUG   ] Please install 'virt-what' to improve results of the 'virtual' grain.
[WARNING ] /usr/lib/python2.7/dist-packages/salt/grains/core.py:1493: DeprecationWarning: The "osmajorrelease" will be a type of an integer.

[DEBUG   ] Connecting to master. Attempt 1 of 1
[DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506')
[DEBUG   ] Generated random reconnect delay between '1000ms' and '11000ms' (1428)
[DEBUG   ] Setting zmq_reconnect_ivl to '1428ms'
[DEBUG   ] Setting zmq_reconnect_ivl_max to '11000ms'
[DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506', 'clear')
[DEBUG   ] Decrypting the current master AES key
[DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[DEBUG   ] Determining pillar cache
[DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506', 'aes')
[DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506')
[DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[DEBUG   ] LazyLoaded jinja.render
[DEBUG   ] LazyLoaded yaml.render
[DEBUG   ] LazyLoaded state.sls
[DEBUG   ] LazyLoaded saltutil.is_running
[DEBUG   ] LazyLoaded grains.get
[DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506', 'aes')
[DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506')
[DEBUG   ] Determining pillar cache
[DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506', 'aes')
[DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506')
[DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[INFO    ] Loading fresh modules for state activity
[DEBUG   ] LazyLoaded jinja.render
[DEBUG   ] LazyLoaded yaml.render
[DEBUG   ] In saltenv 'base', looking at rel_path 'networking/hostname.sls' to resolve 'salt://networking/hostname.sls'
[DEBUG   ] In saltenv 'base', ** considering ** path '/var/cache/salt/minion/files/base/networking/hostname.sls' to resolve 'salt://networking/hostname.sls'
[INFO    ] Fetching file from saltenv 'base', ** skipped ** latest already in cache 'salt://networking/hostname.sls'
[DEBUG   ] compile template: /var/cache/salt/minion/files/base/networking/hostname.sls
[DEBUG   ] Jinja search path: ['/var/cache/salt/minion/files/base']
[DEBUG   ] LazyLoaded pillar.get
[PROFILE ] Time (in seconds) to render '/var/cache/salt/minion/files/base/networking/hostname.sls' using 'jinja' renderer: 0.00820112228394
[DEBUG   ] Rendered data from file: /var/cache/salt/minion/files/base/networking/hostname.sls:

system:
  network.system:
    - enabled: True
    - hostname: test1.suqld.org.au
    - require_reboot: True
    - gateway: 10.1.37.254
    - gatewaydev: ens192

/etc/hostname:
  file.managed:
    - contents: test1
    - backup: false

[DEBUG   ] LazyLoaded config.get
[DEBUG   ] Results of YAML rendering:
OrderedDict([('system', OrderedDict([('network.system', [OrderedDict([('enabled', True)]), OrderedDict([('hostname', 'test1.suqld.org.au')]), OrderedDict([('require_reboot', True)]), OrderedDict([('gateway', '10.1.37.254')]), OrderedDict([('gatewaydev', 'ens192')])])])), ('/etc/hostname', OrderedDict([('file.managed', [OrderedDict([('contents', 'test1')]), OrderedDict([('backup', False)])])]))])
[PROFILE ] Time (in seconds) to render '/var/cache/salt/minion/files/base/networking/hostname.sls' using 'yaml' renderer: 0.00796318054199
[DEBUG   ] LazyLoaded ip.get_interface
[DEBUG   ] LazyLoaded network.system
[INFO    ] Running state [system] at time 14:36:21.951625
[INFO    ] Executing state network.system for system
[DEBUG   ] LazyLoaded service.available
[DEBUG   ] LazyLoaded cmd.run
[INFO    ] Executing command ['systemctl', 'status', 'networking.service', '-n', '0'] in directory '/root'
[DEBUG   ] output: * networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           `-50-insserv.conf-$network.conf
   Active: active (exited) since Thu 2016-09-01 10:44:01 AEST; 3h 52min ago
     Docs: man:interfaces(5)
 Main PID: 3328 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/networking.service
[INFO    ] Executing command ['systemctl', 'is-active', 'networking.service'] in directory '/root'
[DEBUG   ] output: active
[INFO    ] Executing command ['systemctl', 'status', 'NetworkManager.service', '-n', '0'] in directory '/root'
[DEBUG   ] output: * NetworkManager.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
[INFO    ] Executing command ['systemctl', 'is-enabled', 'networking.service'] in directory '/root'
[DEBUG   ] output: enabled
[DEBUG   ] Service 'networking' is not masked
[DEBUG   ] sysvinit script 'lxcfs' found, but systemd unit 'lxcfs.service' already exists
[DEBUG   ] sysvinit script 'single' found, but systemd unit 'single.service' already exists
[DEBUG   ] sysvinit script 'ssh' found, but systemd unit 'ssh.service' already exists
[DEBUG   ] sysvinit script 'atd' found, but systemd unit 'atd.service' already exists
[DEBUG   ] sysvinit script 'rsyslog' found, but systemd unit 'rsyslog.service' already exists
[DEBUG   ] sysvinit script 'urandom' found, but systemd unit 'urandom.service' already exists
[DEBUG   ] sysvinit script 'screen-cleanup' found, but systemd unit 'screen-cleanup.service' already exists
[DEBUG   ] sysvinit script 'iscsid' found, but systemd unit 'iscsid.service' already exists
[DEBUG   ] sysvinit script 'rcS' found, but systemd unit 'rcS.service' already exists
[DEBUG   ] sysvinit script 'kmod' found, but systemd unit 'kmod.service' already exists
[DEBUG   ] sysvinit script 'umountfs' found, but systemd unit 'umountfs.service' already exists
[DEBUG   ] sysvinit script 'killprocs' found, but systemd unit 'killprocs.service' already exists
[DEBUG   ] sysvinit script 'rsync' found, but systemd unit 'rsync.service' already exists
[DEBUG   ] sysvinit script 'resolvconf' found, but systemd unit 'resolvconf.service' already exists
[DEBUG   ] sysvinit script 'salt-minion' found, but systemd unit 'salt-minion.service' already exists
[DEBUG   ] sysvinit script 'php7.0-fpm' found, but systemd unit 'php7.0-fpm.service' already exists
[DEBUG   ] sysvinit script 'reboot' found, but systemd unit 'reboot.service' already exists
[DEBUG   ] sysvinit script 'cryptdisks' found, but systemd unit 'cryptdisks.service' already exists
[DEBUG   ] sysvinit script 'avahi-daemon' found, but systemd unit 'avahi-daemon.service' already exists
[DEBUG   ] sysvinit script 'acpid' found, but systemd unit 'acpid.service' already exists
[DEBUG   ] sysvinit script 'open-vm-tools' found, but systemd unit 'open-vm-tools.service' already exists
[DEBUG   ] sysvinit script 'halt' found, but systemd unit 'halt.service' already exists
[DEBUG   ] sysvinit script 'plymouth-log' found, but systemd unit 'plymouth-log.service' already exists
[DEBUG   ] sysvinit script 'cryptdisks-early' found, but systemd unit 'cryptdisks-early.service' already exists
[DEBUG   ] sysvinit script 'zabbix-agent' found, but systemd unit 'zabbix-agent.service' already exists
[DEBUG   ] sysvinit script 'keyboard-setup' found, but systemd unit 'keyboard-setup.service' already exists
[DEBUG   ] sysvinit script 'lvm2-lvmpolld' found, but systemd unit 'lvm2-lvmpolld.service' already exists
[DEBUG   ] sysvinit script 'networking' found, but systemd unit 'networking.service' already exists
[DEBUG   ] sysvinit script 'dbus' found, but systemd unit 'dbus.service' already exists
[DEBUG   ] sysvinit script 'cron' found, but systemd unit 'cron.service' already exists
[DEBUG   ] sysvinit script 'rc' found, but systemd unit 'rc.service' already exists
[DEBUG   ] sysvinit script 'console-setup' found, but systemd unit 'console-setup.service' already exists
[DEBUG   ] sysvinit script 'lxd' found, but systemd unit 'lxd.service' already exists
[DEBUG   ] sysvinit script 'mysql' found, but systemd unit 'mysql.service' already exists
[DEBUG   ] sysvinit script 'plymouth' found, but systemd unit 'plymouth.service' already exists
[DEBUG   ] sysvinit script 'udev' found, but systemd unit 'udev.service' already exists
[DEBUG   ] sysvinit script 'open-iscsi' found, but systemd unit 'open-iscsi.service' already exists
[DEBUG   ] sysvinit script 'rc.local' found, but systemd unit 'rc.local.service' already exists
[DEBUG   ] sysvinit script 'lvm2' found, but systemd unit 'lvm2.service' already exists
[DEBUG   ] sysvinit script 'uuidd' found, but systemd unit 'uuidd.service' already exists
[DEBUG   ] sysvinit script 'lvm2-lvmetad' found, but systemd unit 'lvm2-lvmetad.service' already exists
[DEBUG   ] sysvinit script 'sendsigs' found, but systemd unit 'sendsigs.service' already exists
[DEBUG   ] sysvinit script 'procps' found, but systemd unit 'procps.service' already exists
[DEBUG   ] sysvinit script 'umountroot' found, but systemd unit 'umountroot.service' already exists
[DEBUG   ] sysvinit script 'ufw' found, but systemd unit 'ufw.service' already exists
[DEBUG   ] sysvinit script 'unattended-upgrades' found, but systemd unit 'unattended-upgrades.service' already exists
[INFO    ] Executing command ['systemd-run', '--scope', 'systemctl', 'enable', 'networking.service'] in directory '/root'
[DEBUG   ] output: Running scope as unit run-re081af14bfba4e8e8b56c169420a92b4.scope.
Synchronizing state of networking.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable networking
[INFO    ] Global network settings are up to date.
[INFO    ] Completed state [system] at time 14:36:22.718206 duration_in_ms=766.581
[DEBUG   ] LazyLoaded file.managed
[INFO    ] Running state [/etc/hostname] at time 14:36:22.721261
[INFO    ] Executing state file.managed for /etc/hostname
[DEBUG   ] LazyLoaded file.check_managed_changes
[INFO    ] File /etc/hostname is in the correct state
[INFO    ] Completed state [/etc/hostname] at time 14:36:22.752791 duration_in_ms=31.53
[DEBUG   ] File /var/cache/salt/minion/accumulator/139954863957520 does not exist, no need to cleanup.
[DEBUG   ] LazyLoaded config.option
[DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506', 'aes')
[DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'test1', 'tcp://192.168.0.20:4506')
[DEBUG   ] LazyLoaded highstate.output
local:
----------
          ID: system
    Function: network.system
      Result: True
     Comment: Global network settings are up to date.
     Started: 14:36:21.951625
    Duration: 766.581 ms
     Changes:
----------
          ID: /etc/hostname
    Function: file.managed
      Result: True
     Comment: File /etc/hostname is in the correct state
     Started: 14:36:22.721261
    Duration: 31.53 ms
     Changes:

Summary for local
------------
Succeeded: 2
Failed:    0
------------
Total states run:     2
Total run time: 798.111 ms

Not the best solution, but I currently have a workaround in my network.managed section to detect the gateway interface and apply an extra gateway option. This adds the correct gateway line to /etc/network/interfaces so that I do get a gateway route.

@jgmchan
Copy link

jgmchan commented Oct 31, 2016 •
edited
Loading

I have the same problem on 2016.3.3 using salt-ssh to a Ubuntu 14.04.5 machine, I have this in my config:

system_network:
  network.system:
    - enabled: True
    - gateway: X.X.X.X
    - gatewaydev: eth1

salt runs fine but nothing actually happens and I can't see any entries into /etc/network/interfaces

@timwsuqld
Copy link

@cachedout @westurner Can we have someone respond or reopen this issue please?

@garethgreenaway
Copy link
Contributor

@timwsuqld @jgmchan Apologies. Missed your message back in August. I'll spin up an Ubuntu machine and test this out.

@timwsuqld
Copy link

@garethgreenaway Thanks. I probably should have done an @ mention back then.

@garethgreenaway
Copy link
Contributor

@timwsuqld no worries 😀

@basepi basepi reopened this Oct 31, 2016
@garethgreenaway
Copy link
Contributor

@timwsuqld @jgmchan Apologies for the delay in responding on this one. I remember dealing with this before and the root of the issue was the major differences with how networking is handled on Debian based machines vs. Red Hat machines.

On RH machines the gateway is definable in a separate location than the interfaces, whereas on Debian machines it's defined with the interfaces. This gets tricky when you're trying to manage things like the gateway without managing the interface as well.

Because of this the network.system state module function works quite differently on a Debian based machine vs. a Red Hat based machine. For managing the gateway I'd recommend using the network.managed or the network.routes state module functions.

@stale
Copy link

stale bot commented Jul 20, 2018

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.

@stale stale bot added the stale label Jul 20, 2018
@stale stale bot closed this as completed Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug broken, incorrect, or confusing behavior severity-low 4th level, cosemtic problems, work around exists stale
Projects
None yet
Milestone
Approved
Development

No branches or pull requests
8 participants
@westurner @cachedout @jleroy @basepi @garethgreenaway @drzero42 @jgmchan @timwsuqld