Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6614

Puppet 4.6.0 Error transactionstore is corrupt

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 4.6.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Windows 2012r2, Puppet Agent 1.6.0, puppetlabs/acl module

    • Template:
    • Team:
      Agent

      Description

      With the new transaction store feature, we've encountered an issue where the transactionstore.yaml file can't be read back in.

      The puppet run does continue, but the red error is making my team flip out because its red and not white or yellow.

      Info: Using configured environment 'production'
      Info: Retrieving pluginfacts
      Info: Retrieving plugin
      Info: Loading facts
      Info: Caching catalog for testserver.example.com
      Error: Transaction store file C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml is corrupt (wrong number of arguments (0 for 1..2)); replacing
      Error: Transaction state file C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml is valid YAML but not returning a hash. Check the file for corruption, or remove it before continuing.
      Info: Applying confiugration version '1471272929'
      Notice: Applied catalog in 34.12 seconds
      

      When i try to load the yaml with irb, it fails due to not finding `Puppet::Type::Acl` and my transactionstore.yaml contains multiple lines of `- !ruby/hash:Puppet::Type::Acl::Ace {}` on the each Acl resource at parameters/permissions/system_value location.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ruckc Curtis Ruck
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support