This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
postNodeUpgrade won't upgrade standard-package-repo on tce (#1760) #1768
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.
This change updates the upgradeAddonPostNodeUpgrade method to exclude
updating the standard-package-repo when the cluster is a TCE cluster.
The standard-package-repo does not exist on TCE clusters.
Co-authored-by: Nick Tenczar ntenczar@vmware.com
What this PR does / why we need it
Backport of PR 1760
Which issue(s) this PR fixes
Fixes #1749
Describe testing done for PR
I created a vSphere management cluster setting the build edition to TCE. I then ran management-cluster upgrade with log level nine. I confirmed in the logs that all of the required packages were upgraded and that the standard-package-repo was not upgrade.
Release note
PR Checklist
Additional information
Special notes for your reviewer