[PDB-5338] Fix PuppetDB storage of catalogs with resource kind attribute - Puppet Jira Server

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: PDB 6.19.1, PDB 7.7.1
Component/s: PuppetDB
Labels:
- jira_escalated

Acceptance Criteria:
Hide

Drop unrecognized attributes with a warning

Drop kind attribute without a warning - this is an Agent/Server communication implementation detail that we don't need to store

Update catalog test example data to include kind attribute

Update benchmark dataset to include kind
Show
Drop unrecognized attributes with a warning Drop kind attribute without a warning - this is an Agent/Server communication implementation detail that we don't need to store Update catalog test example data to include kind attribute Update benchmark dataset to include kind
Team:
HA
Story Points:
3
Sprint:
HA 2021-11-03
Method Found:
Automated Test

Zendesk Ticket IDs:
49770
Zendesk Ticket Count:
1

Release Notes:
Security Fix
Release Notes Summary:
due to a security fix in PuppetDB, catalog resources have an additional field. This was not handled by previous versions of PuppetDB, which will be incompatible with Puppet Agent catalogs that contain the additional field.

QA Risk Assessment:
Needs Assessment

Description

To fix a CVE, resources now have a kind attribute. Catalogs with this attribute cause PuppetDB to error on command storage.

To allow the Puppet Agent to make additions to the Catalog without needing a simultaneous upgrade of PuppetDB to add a database column, we should ignore unrecognized catalog resource attributes.

Attachments

Activity

People

Assignee:: Austin Blatt

Reporter:: Austin Blatt

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2021/10/19 4:53 PM

Updated:: 2022/09/29 8:25 AM

Resolved:: 2021/11/01 3:13 PM