Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title David Kramer updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: David Kramer Sprint: FF 2016-10-19 , FF 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Labels: maintenance Team: Foundational Features Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Sprint: Hopper FF 2016-10-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3064
PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Issue Type:
Bug
Affects Versions:
PDB 4.2.2
Assignee:
Unassigned
Created:
2016/09/21 3:55 PM
Priority:
Normal
Reporter:
Wyatt Alt
This is a bug with corrective_change being required for some events thing. The problem is somewhere in the reports command version translation code.
2016-09-21 15:53:11,646 ERROR [o.a.a.ActiveMQMessageConsumer] ID:mbp.local-64396-1474498387723-6:1:3:1 Exception while processing message: ID:mbp.local-60682-1474498266238-8:1:21:1:91
clojure.lang.ExceptionInfo: Value does not match schema: {:resources [{:corrective_change missing-required-key, :events [{:corrective_change missing-required-key}]} {:corrective_change missing-required-key, :events [{:corrective_change missing-required-key}]} {:corrective_change missing-required-key, :events [{:corrective_change missing-required-key}]} {:correct
