Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: PUP 3.4.0
    • Fix Version/s: PUP 3.4.3
    • Component/s: Catalog Application
    • Labels:
      None
    • Template:
    • Story Points:
      2
    • Sprint:
      Week 2014-1-29 to 2014-2-05, Week 2014-2-5 to 2014-2-12

      Description

      I'm noticing a series of duplicate events from failed resources being raised by PuppetDB users (see PDB-349) this seems to have been caused by a patch as shown from the bisect here:

      https://gist.github.com/kbarber/8653842

      The net effect is that properties are getting logged twice in the event log for PuppetDB, in the store and even on the console. The net result for PuppetDB is that these reports are not being stored, because a duplicate event forces the transaction to rollback, which as you can imagine is a bad thing (tm).

      The example manifest I used to replicate this looks like:

      package {"asdf": }
      

      And the duplication ends up looking like this:

      root@puppetdb1:~/Development/puppet# RUBYLIB=~/Development/puppet/lib:~/Development/facter/lib ./bin/puppet agent -t
      Info: Retrieving plugin
      Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
      Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
      Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
      Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
      Info: Loading facts in /etc/puppet/modules/concat/lib/facter/concat_basedir.rb
      Info: Loading facts in /etc/puppet/modules/firewall/lib/facter/ip6tables_version.rb
      Info: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables_version.rb
      Info: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rb
      Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
      Info: Caching catalog for puppetdb1.vm
      Info: Applying configuration version '1390845262'
      Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install asdfasdf' returned 100: Reading package lists...
      Building dependency tree...
      Reading state information...
      E: Unable to locate package asdfasdf
       
      Error: /Stage[main]//Package[asdfasdf]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install asdfasdf' returned 100: Reading package lists...
      Building dependency tree...
      Reading state information...
      E: Unable to locate package asdfasdf
       
      Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install asdfasdf' returned 100: Reading package lists...
      Building dependency tree...
      Reading state information...
      E: Unable to locate package asdfasdf
       
      Error: /Stage[main]//Package[asdfasdf]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install asdfasdf' returned 100: Reading package lists...
      Building dependency tree...
      Reading state information...
      E: Unable to locate package asdfasdf
       
      ^CNotice: Caught INT; calling stop
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ken Ken Barber
              • Votes:
                1 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support