-
Notifications
You must be signed in to change notification settings - Fork 23
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
issue:4273572 Add NDT plugin upgrade flow #292
Open
alextabachnik
wants to merge
9
commits into
main
Choose a base branch
from
issue/4273572_create_empty_upgrade_script_ndt_plugin
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
issue:4273572 Add NDT plugin upgrade flow #292
alextabachnik
wants to merge
9
commits into
main
from
issue/4273572_create_empty_upgrade_script_ndt_plugin
Conversation
This file contains 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
issue:4274215 support duplicated node description report in case no other errors detected (bug fix) Signed-off-by: Alex Tabachnik <atabachnik@nvidia.com>
need for ci as it is not running as root Signed-off-by: Alex Tabachnik <atabachnik@nvidia.com>
bot:retest |
kedeme
reviewed
Feb 3, 2025
@@ -0,0 +1,4 @@ | |||
#!/bin/bash | |||
# upgrade flow not implemented for NDT plugin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not? don't we need to upgrade the NDT plugin configuration?
… master node (#291) * Making the script run on master * Fix condition for master/standby * ruff * Adding more info to the readme and renaming * updating the readme * readme * PR comments * PR comments
….sh upgrade command fails (#296)
…om multiple telemetry endpoints. (#293)
Signed-off-by: Alex Tabachnik <atabachnik@nvidia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
issue:4274215 support duplicated node description report in case no other errors detected (bug fix)
What
implement upgrade.sh script that could be used for upgrade flow if need
handle option for merger report when node description duplication error is an only error in report (buf fix bug )
Why ?
Fix a bug and add functionality (upgrade)
How ?
Implemented empty upgrade.sh script as this script required by upgrade flow.
Added functionality for duplicated node description report if it is the only error in fabric
Testing ?
Tested manually
Special triggers
Use the following phrases as comments to trigger different runs
bot:retest
rerun Jenkins CI (to rerun GitHub CI, use "Checks" tab on PR page and rerun all jobs)bot:upgrade
run additional update tests