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

Bridge ports are not set to up after bouncing bridge #164

Open
jovial opened this issue Sep 27, 2024 · 0 comments · May be fixed by #168
Open

Bridge ports are not set to up after bouncing bridge #164

jovial opened this issue Sep 27, 2024 · 0 comments · May be fixed by #168

Comments

@jovial
Copy link

jovial commented Sep 27, 2024

OS: Rocky 9.4

I've configured a bridge with a single bridge port. After setting the firewalld zone and rerunning the role, the role attempts to bounce my bridge (fair enough as the config file has changed), but after doing so, the bridge port is left in the down state. This causes a loss of connectivity and the role fails. To recover I can manually run:

nmcli c up ensf4f1np1

Where ensf41np1 is my bridge port. I guess the issue is that the templated config for the bridge port did not change and as such was not bounced when the bridge was reconfigured.

jovial added a commit to stackhpc/ansible-role-interfaces that referenced this issue Sep 27, 2024
@jovial jovial changed the title Bridge ports are set to up after bouncing bridge Bridge ports are not set to up after bouncing bridge Oct 1, 2024
jovial added a commit to stackhpc/ansible-role-interfaces that referenced this issue Nov 8, 2024
@jovial jovial linked a pull request Nov 8, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant