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

No longer finding interface config scripts in CentOS #39

Closed
Aethylred opened this issue May 22, 2013 · 4 comments
Closed

No longer finding interface config scripts in CentOS #39

Aethylred opened this issue May 22, 2013 · 4 comments

Comments

@Aethylred
Copy link

Since the resolving #36 and #37 the network module no longer seems to be detecting interface configuration files in CentOS 6.4.

err: Could not prefetch network_config provider 'redhat': No resource and no name in property hash in redhat instance
notice: /Stage[main]//Node[login.tamaki.test.nesi.org.nz]/Network_config[eth0]/ensure: created
err: /Stage[main]//Node[login.tamaki.test.nesi.org.nz]/Network_config[eth0]: Could not evaluate: No resource and no name in property hash in redhat instance
err: /Stage[main]//Node[login.tamaki.test.nesi.org.nz]/Network_config[eth1]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
@ericsakowski
Copy link
Contributor

I could not reproduce this error using a puppet 2.7 client connecting to a puppet 2.7 master.

I was able to reproduce by connecting the 2.7 client on CentOS 6.3 to a puppet 3.0 master on RHEL 6.3, though:

err: Could not prefetch network_config provider 'redhat': No resource and no name in property hash in redhat instance
notice: /Stage[main]/Profile::Proxy_dev/Network_config[lo:6]/ensure: created
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:6]: Could not evaluate: No resource and no name in property hash in redhat instance
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:3]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:1]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:2]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:7]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:5]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
err: /Stage[main]/Profile::Proxy_dev/Network_config[lo:4]/ensure: change from absent to present failed: Puppet::Type::Network_config::ProviderRedhat is in an error state
notice: Finished catalog run in 0.18 seconds

Hope this helps narrow it down a bit.

@ericsakowski
Copy link
Contributor

ok that was a red herring...after all this i went back and tested 2.7 node on 2.7 master and still get the same 'error state' and prefetch errors.

@Aethylred
Copy link
Author

It seemed to run fine the first time, and then entered the error state.

Puppet master seems to be running 2.7.12 on Ubuntu 11.10 with kernel 3.0.0-24. This is the puppet package distributed from the Ubuntu package repository (well... our local mirror)

The client in question is running Puppet 2.6.18 on CentOS 6.4 with kernel 2.6.32-258. This is the puppet package currently distributed via the EPEL repository.

We don't really want to add the Puppetlabs repository and jump to Puppet 3.x (yet).

@Aethylred
Copy link
Author

Resolved by #40! Awesome.

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