Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4266

Make package inventory actually sync

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 5.2.10, PDB 6.3.5, PDB 6.4.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      PuppetDB
    • Method Found:
      Needs Assessment
    • Release Notes Summary:
      (PE only) PuppetDB did not sync its package inventory which could cause factsets to sync without converging to a stable state after a restart/downtime until the next factset was submitted for that node.
    • QA Risk Assessment:
      Needs Assessment

      Description

      In pe-puppetdb theĀ :package_inventory "fact" is included in the fact data when its hash is generated but package information is then stored and queried on its own. The result is that if a fact needs to be synced to another PuppetDB, the package inventory will not be synced and the resulting fact hash will be different between the PuppetDBs. Then roughly ~50% of those factsets with mismatched hashes will sync every sync run.

      This was seen in a customers infrastructure in PDB-4072 as the HA being out of sync after a restart because while the primary PuppetDB was down facts were still being submitted to the secondary PuppetDB, so when the primary came back online it synced those facts and generated the wrong hash.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  austin.blatt Austin Blatt
                  Reporter:
                  austin.blatt Austin Blatt
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support