-
Notifications
You must be signed in to change notification settings - Fork 344
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
t3c to use package metadata if rpm db is unhealthy #7652
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7652 +/- ##
=============================================
- Coverage 65.10% 27.20% -37.90%
Complexity 98 98
=============================================
Files 314 686 +372
Lines 12359 79755 +67396
Branches 905 90 -815
=============================================
+ Hits 8046 21701 +13655
- Misses 3961 55984 +52023
- Partials 352 2070 +1718
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 587 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
These all look fine and test okay. Definitely not broken for the current working configuration.
* adding check to verify rpmdb * added check to verify rpm db * rebase and fix conflicts * if rpmdb is unhealthy use package data in metadata * requested changes addressed. * added changelog entry * fixed spelling error and added GoDoc commnet * fixed formatting error
right now if there is an issue with RPM t3c will not be able keep the cache config up to date. this PR will address this issue.
In syncds mode t3c will attempt a check of the RPM DB files, if it succeeds t3c will continue as normal. if the check fails t3c will attempt to get package data from t3c-apply-metadata.json. if package data is available t3c will use it and make an assumption that trafficserver is installed and continue with config updates. if the package data in the metadata file is unavailable it will attempt to continue without package data.
if badass mode or --install-packages=true is selected. t3c will exit with an error if rpm db check fails as packages cannot be installed without rpm.
Which Traffic Control components are affected by this PR?
t3c
, formerly ORT)What is the best way to verify this PR?
since it is difficult and dangerous to corrupt an rpm database the best way to test is update the config such that rpmDBisOk is set to false run t3c in different modes and check the results.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist