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.

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

Interfaces are "created" every puppet run #42

Closed
ddcrjlalumiere opened this issue May 31, 2013 · 5 comments
Closed

Interfaces are "created" every puppet run #42

ddcrjlalumiere opened this issue May 31, 2013 · 5 comments

Comments

@ddcrjlalumiere
Copy link

For some reason every run of Puppet the /etc/sysconfig/network-scripts/ifcfg-* files managed by this module are "created", even if they already exist. This seems to be caused by the order of the lines in the file changing each time it is generated?

Here's a diff of one of the interface files showing how it changed between runs, although the key value pairings are all the same.

$ sudo diff --side-by-side /etc/sysconfig/network-scripts/ifcfg-lo\:1 /tmp/ifcfg-lo\:1 
DEVICE=lo:1                           | BOOTPROTO=loopback
ONBOOT=yes                          ONBOOT=yes
IPADDR=10.12.16.18                        <
NETMASK=255.255.255.255                     NETMASK=255.255.255.255
                                  >  IPADDR=10.12.16.18
HOTPLUG=yes                         HOTPLUG=yes
BOOTPROTO=loopback                        | DEVICE=lo:1

This is not causing a functional problem at the moment, however it does clutter the logs substantially.

@ddcrjlalumiere
Copy link
Author

Actually if I leave the daemon running rather than restarting it different sets of log messages pop up:

# First restart. Configs already exist, created by this module
Sun Jun 02 03:31:02 +0000 2013 Puppet (notice): Reopening log files
Sun Jun 02 03:31:02 +0000 2013 Puppet (notice): Starting Puppet client version 2.7.17
Sun Jun 02 03:31:08 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:6]/ensure (notice): created
Sun Jun 02 03:31:08 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:3]/ensure (notice): created
Sun Jun 02 03:31:12 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:1]/ensure (notice): created
Sun Jun 02 03:31:12 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:2]/ensure (notice): created
Sun Jun 02 03:31:14 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:7]/ensure (notice): created
Sun Jun 02 03:31:18 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:5]/ensure (notice): created
Sun Jun 02 03:31:19 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:4]/ensure (notice): created
Sun Jun 02 03:31:19 +0000 2013 Puppet (notice): Finished catalog run in 13.90 seconds
# Run 2 -  Seen here is a return of Issue 38
Sun Jun 02 04:01:11 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:6]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:11 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:6] (err): Could not evaluate: Unable to support multiple interfaces [lo:6,lo:6] in a single file /etc/sysconfig/network-scripts/ifcfg-lo:6
Sun Jun 02 04:01:11 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:3]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:11 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:3
Sun Jun 02 04:01:15 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:1]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:15 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:1
Sun Jun 02 04:01:15 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:2]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:15 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:2
Sun Jun 02 04:01:17 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:7]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:17 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:7
Sun Jun 02 04:01:22 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:5]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:22 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:5
Sun Jun 02 04:01:22 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:4]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:01:22 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:4
Sun Jun 02 04:01:22 +0000 2013 Puppet (notice): Finished catalog run in 14.35 seconds
# Run 3 - Interesting don't see Issue 38 on subsequent runs, but still barfing in the logs
Sun Jun 02 04:31:15 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:6]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:15 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:6
Sun Jun 02 04:31:15 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:3]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:15 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:3
Sun Jun 02 04:31:19 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:1]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:19 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:1
Sun Jun 02 04:31:19 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:2]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:19 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:2
Sun Jun 02 04:31:21 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:7]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:21 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:7
Sun Jun 02 04:31:25 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:5]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:25 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:5
Sun Jun 02 04:31:26 +0000 2013 /Stage[main]/Proxy::Dev/Network_config[lo:4]/method (notice): method changed 'static' to 'loopback'
Sun Jun 02 04:31:26 +0000 2013 Puppet::Type::Network_config::ProviderRedhat (err): redhat is in an error state, refusing to flush file /etc/sysconfig/network-scripts/ifcfg-lo:4
Sun Jun 02 04:31:26 +0000 2013 Puppet (notice): Finished catalog run in 14.44 seconds

@adrienthebo
Copy link
Member

@ddcrjlalumiere sorry for the slow response on this; which version of puppet-network are you using? Is this a recent bug that occurred when it previously worked?

@ddcrjlalumiere
Copy link
Author

I believe this behavior has been present since I started using the module (version 0.40). Presently I'm using commit 206c2d7.

@adrienthebo
Copy link
Member

@ddcrjlalumiere sorry for the delay in response... it's been a really long month. I think that the issue with interfaces constantly being renamed is due to hash ordering; are you using Ruby 1.8.7 on this machine?

And to confirm #38 has been resolved to your satisfaction, so the main issue is the ordering in the file changing?

@adrienthebo
Copy link
Member

Issue hasn't seen an update in 2 years, closing for lack of activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants