-
Notifications
You must be signed in to change notification settings - Fork 137
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
bond slaves no default mac address #34
Comments
GitHub was acting up last night. :-( I believe it is because NIC MACs start to change once more than one interface becomes a slave to a bond. |
I have been reading the kernel docs on bonding and whilst the bonding module does change the mac addresses of the slave devices it doesnt cause an issue for facter, it still reports the actual physical mac... ifconfig eth0 Link encap:Ethernet HWaddr 00:50:56:B1:62:82 eth1 Link encap:Ethernet HWaddr 00:50:56:B1:62:82 facter | grep macaddress_ I have been using a forked version of your code with the patch applied and everything works fine |
That is good news. May I ask what versions of Puppet and Facter you are using? |
puppet-3.4.2-1.el6.noarch |
For the life of me, I can not remember why I left that feature out. Feel free to send a PR against the |
hopefully that PR is better, still getting used to github |
👍 for this PR |
I started a pull request for this but github hates me and it went horribly wrong. Anyway, I note that some resources (eg network::if::static) auto set the mac address of an interface based on the macaddress_ethX fact. Is there a reason this is not done for the network::bond::slave resource?
The text was updated successfully, but these errors were encountered: