Skip to content

[NXOS] fix: requeue when interface is operationally down#228

Draft
nikatza wants to merge 1 commit intomainfrom
fix-interface
Draft

[NXOS] fix: requeue when interface is operationally down#228
nikatza wants to merge 1 commit intomainfrom
fix-interface

Conversation

@nikatza
Copy link
Contributor

@nikatza nikatza commented Mar 12, 2026

No description provided.

After a new Port-channel is created on a device, its  member interfaces
transition from `down` to `link-up` to `up`. When the port-channel
reconciles, it triggers a reconciliation of its members. This can happen
before the member reaches the `up` state, causing the controller to
report it as down and not recheck for up to an hour.

Requeue after 5 seconds when the interface is operationally down instead
of waiting for the full requeue interval. This allows the controller to
quickly pick up the final `up` state.
@github-actions
Copy link

Merging this branch will decrease overall coverage

Impacted Packages Coverage Δ 🤖
github.com/ironcore-dev/network-operator/internal/controller/core 62.72% (-0.33%) 👎

Coverage by file

Changed files (no unit tests)

Changed File Coverage Δ Total Covered Missed 🤖
github.com/ironcore-dev/network-operator/internal/controller/core/interface_controller.go 74.87% (ø) 394 295 99

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

@hardikdr hardikdr added the area/metal-automation Automation processes within the Metal project. label Mar 13, 2026
@hardikdr hardikdr added this to Roadmap Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/metal-automation Automation processes within the Metal project.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants