-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
-
None
Description of problem:
When bonding or bridging fails, there is no visual cue in the UI to indicate where the failure occurred. Users are forced to dig into logs or YAML output to identify problems.
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Frequently.
Steps to Reproduce:
1.Configure a bonded or bridged network setup with intentional misconfiguration (e.g., missing interfaces). 2. Apply the configuration and observe feedback.
Actual results:
No visual indication in the UI; failure must be deduced manually via logs or CLI.
Expected results:
UI should flag specific components (nodes, interfaces, bonds) where the configuration failed.
Additional info:
Could maybe benefit from red/yellow warning badges or messages in a topology/network map view.