-
Notifications
You must be signed in to change notification settings - Fork 12
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
confd: fails removing veth pair after a multple reconfigurations #658
Comments
Nice finding, but not a blocker for v24.09.0. Also, I suggest we change the title to: "confd fails input validation of interface type". |
Core team has continued discussing this issue, it has now evolved into a blocker issue for v24.09. Root cause, reconfiguring the system multiple times after initially adding a VETH pair makes it impossible to remove the VETH pair. |
Verify a VETH pair can be removed after a couple of dummy operations to step the dagger generation past the initial where the pair is created. NOTE: Infamy currenly lacks support for removing chunks of configuraion e.g., a dut.del_config_dict(), or similar, and delete_xpath() is not valid for configurations with dependencies like VETH pairs. Issue #658 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Current Behavior
The NETCONF request provided creates a bridge
br-X
with the portethX
(mapped to a specific port on the target). In the example below, the test initializes the environment and attaches the target, then configures the bridge and its associated interface:By looking at the logs on the target we see that
confd
crashes:The issue stems from the fact that, although the request specifies a valid Ethernet type (
ethernet
) for theethX
interface, the target system expects a different type, specificallyetherlike
. However, even though there is a type mismatch, this should not cause theconfd
process to crash.The crash indicates a bug or a problem with the error handling mechanism in
confd
.Expected Behavior
Ideally, the system should reject the configuration and provide a meaningful error message, rather than crashing entirely.
Steps To Reproduce
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: