[NX-OS] Separate feature activation from configuration#155
Merged
felix-kaestner merged 1 commit intomainfrom Jan 20, 2026
Merged
[NX-OS] Separate feature activation from configuration#155felix-kaestner merged 1 commit intomainfrom
felix-kaestner merged 1 commit intomainfrom
Conversation
felix-kaestner
force-pushed
the
nxos-feature-activation
branch
from
9c86dea to
47ac8d7
Compare
hardikdr
added
the
area/metal-automation
felix-kaestner
force-pushed
the
nxos-feature-activation
branch
2 times, most recently
from
1459984 to
bfe6337
Compare
NX-OS versions prior to 10.6(3) have an issue where YANG configuration is not persisted when feature activation is mixed with dependent configuration in the same gNMI request. The configuration shows up in YANG queries but not in the running config. This implements a workaround by separating feature activation from dependent configuration into separate gNMI transactions for affected versions. Relates to #148
felix-kaestner
force-pushed
the
nxos-feature-activation
branch
from
bfe6337 to
16a3a8a
Compare
Merging this branch will decrease overall coverage
Coverage by fileChanged files (no unit tests)
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. Changed unit test files
|
felix-kaestner
added a commit
that referenced
this pull request
Jan 26, 2026
NX-OS versions prior to 10.6(3) have an issue where YANG configuration is not persisted when feature activation is mixed with dependent configuration in the same gNMI request. The configuration shows up in YANG queries but not in the running config. This implements a workaround by separating feature activation from dependent configuration into separate gNMI transactions for affected versions. Relates to #148
swagner-de
pushed a commit
that referenced
this pull request
Jan 27, 2026
NX-OS versions prior to 10.6(3) have an issue where YANG configuration is not persisted when feature activation is mixed with dependent configuration in the same gNMI request. The configuration shows up in YANG queries but not in the running config. This implements a workaround by separating feature activation from dependent configuration into separate gNMI transactions for affected versions. Relates to #148
hardikdr
added
the
area/switch-automation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
NX-OS versions prior to 10.6(3) have an issue where YANG configuration is not persisted when feature activation is mixed with dependent configuration in the same gNMI request. The configuration appears in YANG queries but not in the running config.
Solution
This PR implements a workaround by separating feature activation from dependent configuration into separate gNMI transactions for affected versions (≤10.6(2)).
Relates to #148