-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Interface config created but device is not up #86
Comments
Yeah, I'm having same issue with eth1. |
Hi, Attached is scrubbed output of facter. Thanks, Alex On Fri, May 15, 2015 at 8:16 AM, Alessandro Franceschi <
architecture => x86_64 |
scrubbed… |
Scrubbed...redacted...removed possibly sensitive info. On Wed, May 27, 2015 at 1:09 PM, Igor Galić [email protected]
|
Honestly, looking through the type and providers for |
Not sure if it helps but I came across another module which uses types and providers @inkblot it seems that his module does bring an interface up. Not sure if it helps. |
It's true, my |
I too had expected this module to bring up the newly-created interface. Is this not possible? |
Just did some digging. In theory, the However, its function is protected by the This issue has become a little unwieldy. I shall create a feature request to supersede it. Thanks everyone for your feedback! |
Hi!, I'm configuring a new loopback alias, the device is created but it's never started. I have to do a manual ifup to make the IP available.
SO: RHEL6
Puppet: 3.7.1
adrien-network: 0.4.1
File generated as:
Resource:
Is this an expected behavior?
The text was updated successfully, but these errors were encountered: