-
Notifications
You must be signed in to change notification settings - Fork 4
Pilem bonds restart #25
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
base: main
Are you sure you want to change the base?
Conversation
btravouillon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So sorry I missed this one when we were working together @pilem. 😕
tasks/main.yml
Outdated
| item['configure'] and | ||
| config_interface['changed'] | ||
|
|
||
| - name: Restarting Network Bonds |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this restart before the bridges?
I guess there is a highest chance that a bridge requires a bond to exist than the opposite.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch. I'll swap the restart order.
tasks/main.yml
Outdated
| when: (ifupdown_network_interfaces | length > 0 or ifupdown_network_vlans | length > 0 or | ||
| ifupdown_network_bridges | length > 0 or ifupdown_network_bonds | length > 0 or | ||
| ifupdown_ovs_bridges | length > 0 or ifupdown_ovs_bonds | length > 0 or | ||
| ifupdown_ovs_interfaces | length > 0 or ifupdown_ovs_ports | length > 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this when clause makes sense. I would remove it and execute this task at each run.
I mean, I can't see no obvious reason to use this role if not to configure /etc/network/interfaces. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense. I'll remove this condition.
| dns-search {{ ifupdown_dns_search }} | ||
| {% endif %} | ||
|
|
||
| source /etc/network/interfaces.d/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please make it a condition to not change the default behaviour?
| source /etc/network/interfaces.d/* | |
| {% if ifupdown_source_interfaces_d | bool %} | |
| source /etc/network/interfaces.d/* | |
| {% endif %} |
- add this to
defaults/main.yml:
ifupdown_source_interfaces_d: false
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, not a problem.
…art, made sourcing interfaces.d content optional
btravouillon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. 👍
ping @pbouchez 😺
|
fwiw 2 workflows are awaiting approval from a maintainer (which I'm not anymore 😢) |
I ran them and the checks are now failing :( |
|
And #27 for molecule tests. |
|
@pilem : Do you have a working GPG key associated to your GitHub account? |
Restarting Network Bonds added
Conditions to configure defined interfaces added
source /etc/network/interfaces.d/* added