RHINENG-2867: fix store to advisory metadata and system advisories when update does not have an erratum #1337
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.
When vmaas (or yum_updates) reports an update without erratum, then this erratum is returned as
''
bygetReportedAdvisories
and in turngetAdvisoriesFromDB
creates emptyAdvisoryMetadata{}
due to an issue with slice initialization. EmptyAdvisoryMetadata
hasID: 0
which cannot be stored tosystem_advisories
since advisory with id=0 does not exist inadvisory_metadata
table.Secure Coding Practices Checklist GitHub Link
Secure Coding Checklist