Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1057735 - Error: Could not send report: Error 400 on SERVER: Could not intern from pson: uninitialized constant Puppet::Util::TagSet
Summary: Error: Could not send report: Error 400 on SERVER: Could not intern from pson...
Alias: None
Product: Fedora
Classification: Fedora
Component: puppet
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Ohad Levy
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-24 17:10 UTC by John Florian
Modified: 2015-06-30 00:52 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-30 00:52:24 UTC

Attachments (Terms of Use)

Description John Florian 2014-01-24 17:10:58 UTC
Description of problem:
Latest update seems to have broke our stable setup.  Clients fail with the error in the summary.  It looks like the catalog is getting applied though.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
puppet agent --test

Actual results:
Info: Retrieving plugin
Info: Loading facts <snip>
Info: Caching catalog for
Info: Applying configuration version '1390582838'
Notice: Finished catalog run in 7.22 seconds
Error: Could not send report: Error 400 on SERVER: Could not intern from yaml: uninitialized constant Puppet::Util::TagSet

Additional info:
This appears to be related to the tagmail feature.  If, on the puppet master, I revise "reports = tagmail,store,log" to "reports = store,log" in the [master] section, the error goes away.  Of course, we don't get our useful reports via  tagmail anymore either though.

Comment 2 Fedora End Of Life 2015-05-29 10:39:59 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-30 00:52:24 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.