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

Correct network playbook reboot debian #447

Merged
merged 9 commits into from
Mar 22, 2024

Conversation

eroussy
Copy link
Member

@eroussy eroussy commented Mar 21, 2024

Reload systemd-network only when the configuration has changed.
Correct a bug where timemaster could wait for a interface that would be created later in the playbook.

eroussy added 5 commits March 21, 2024 14:13
If the timemaster configuration has changed, it could mean the ptp
interface has changed. In that case, we need to reload systemd.

Signed-off-by: Erwann Roussy <[email protected]>
The timemaster service could use interfaces defined during the
systemd-network role run.
A reload of systemd-network only happen if the variable
`apply_network_config` is set to true.
Thus, the restart of the timemaster service must only happen if the
variable `apply_network_config` is set to true.

Signed-off-by: Erwann Roussy <[email protected]>
Apply the last commit of ansible-role-systemd-networkd.
Pass the variable `systemd_networkd_apply_config` to it.

With this modification, the hypervisor will reboot (or reload
systemd-networkd) if network configuration has changed.

Signed-off-by: Erwann Roussy <[email protected]>
This case is already handled by the systemd-network role

Signed-off-by: Erwann Roussy <[email protected]>
Virtual Machines don't need to reboot and can apply their network config
directly in the playbook.
This commit avoids the use of `apply_network_config` in the VM inventory
by putting it to true directly in the playbook.

Signed-off-by: Erwann Roussy <[email protected]>
@eroussy eroussy force-pushed the correct_network_playbook_reboot_debian branch 2 times, most recently from b72689f to c48e5c9 Compare March 21, 2024 16:29
eroussy added 4 commits March 22, 2024 09:22
udev needs to be restarted when link files are added.
It is better to do that in the systemd-neworkd role than directly in the
profile.

Signed-off-by: Erwann Roussy <[email protected]>
- Network changes made on VMs don't need to reboot
- Standalone machines will be rebooted at the end of the
  cluster_setup_debian.yaml playbook, just after network.

Signed-off-by: Erwann Roussy <[email protected]>
Remove the network implementation variables of the examples and add
them to the README.
These variables should not be used by SEAPATH beginners, thus they should
not be mentionned in the examples.

Signed-off-by: Erwann Roussy <[email protected]>
The URL was not the right one.

Signed-off-by: Erwann Roussy <[email protected]>
@eroussy eroussy force-pushed the correct_network_playbook_reboot_debian branch from c48e5c9 to 518a42e Compare March 22, 2024 09:20
@eroussy eroussy marked this pull request as ready for review March 22, 2024 11:18
@eroussy eroussy merged commit f428d49 into debian-main Mar 22, 2024
3 checks passed
@eroussy eroussy deleted the correct_network_playbook_reboot_debian branch March 22, 2024 12:44
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

Successfully merging this pull request may close these issues.

Error during cluster_setup_network playbook execution with dedicated interface for PTP
2 participants