Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-332 Tags not included in catalog hash Change By: Russell Mull Assignee: RussellMull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-332 Tags not included in catalog hash Change By: Kenneth Barber Fix Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-332 Tags not included in catalog hash Change By: Ryan Senior Sprint: PuppetDB2015-02-25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title David Lutterkort commented on PDB-332 Re: Tags not included in catalog hash This is an actual issue for app mgmt: resources that one node produces for consumption by other nodes right now are tagged with the type and title of the application they belong to. There are things that users can do to their manifest, like renaming an application instance, that only changes the tags on those resources but nothing else in the catalog. With this bug, consuming nodes would fail to find them. It's not clear yet whether we will continue to rely on tags to scope producers and consumers by application instance; if we do, this issue becomes very important. If we don't, we most likely don't care. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-332 Tags not included in catalog hash Issue Type: Bug Affects Versions: 1.5.X Assignee: Unassigned Created: 16/Jan/14 9:28 AM Priority: Normal Reporter: Ryan Senior While working on PDB-313, I found that tags in the resource metadata are not being included in the catalog's hash. Talking with Kenneth Barber, it sounds like it would be pretty unlikely that a user could have a changed tag without something else changing along with it. If the user had a new explicit tag, the parameters would have changed too (causing the hash to change). If the user had a new implicit tag, there would have been other changes to that resource metadata (not just the tag), causing the hash change. Add Comment
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-332 Tags not included in catalog hash Change By: Ryan Senior WhileworkingonPDB-313,Ifoundthattagsintheresourcemetadataarenotbeingincludedinthecatalog'shash.Talkingwith[~ken],itsoundslikeitwouldbeprettyunlikelythatausercouldhaveachangedtagwithoutsomethingelsechangingalongwithit.Iftheuserhadanewexplicittag,theparameterswouldhavechangedtoo(causingthehashtochange).Iftheuserhadanewimplicittag,therewouldhavebeenotherchangestothatresourcemetadata(notjustthetag),causingthehashchange. Looksliketheissuegoesbackto1.5,thecodeinquestionis[here|https://github.com/puppetlabs/puppetdb/blob/1.5.x/src/com/puppetlabs/puppetdb/scf/storage.clj#L429] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
