Skip to content

Issue #22407: ConfigReload fails when RADIUS options are enabled #3860

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

anders-nexthop
Copy link

@anders-nexthop anders-nexthop commented Apr 22, 2025

What I did

Enabling RADIUS statistics adds config entries which are not valid in YANG. The option adds the True/False boolean values instead of the 'true'/'false' booleans that are defined in the YANG model, which causes failures when trying to reload/replace the config.

How I did it

Modified relevant config command to use the correct values.

How to verify it

Manually verified.

I added a test case for config radius statistics command. Note that this test follows the pattern in this file, which is not actually exercising the correct codepath (see #3754 for details).

Previous command output (if the output of a command-line utility has changed)

New command output (if the output of a command-line utility has changed)

@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@anders-nexthop anders-nexthop force-pushed the anders.radius-options-fix branch from 4f7e975 to 41d4a63 Compare April 23, 2025 06:10
@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

RADIUS statistics adds a config entry which is not valid in YANG.
The option adds the True/False boolean values instead of the
'true'/'false' booleans that YANG defines, which causes failures when
trying to reload/replace the config.
@anders-nexthop anders-nexthop force-pushed the anders.radius-options-fix branch from 41d4a63 to d69218d Compare April 23, 2025 06:14
@mssonicbld
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

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.

2 participants