Issue #2908 has been updated by Luke Kanies. Status changed from Unreviewed to Accepted
In general it shouldn't be a problem if a resource is untagged. The only time I can think where it would be a problem is if it's an exported resource and you're using --tags on a client that collects that resource - in that case, the resource wouldn't match tags that it might otherwise. As to how a resource wouldn't have tags, it should be relatively easy to figure out by watching each resource as it's added to the database -- is it the first one? last one? etc. It quite likely has something to do with the CacheAccumulator module that's used to find the tag list, or something about how rails resources are saved. ---------------------------------------- Bug #2908: Rails resources are sometimes untagged http://projects.reductivelabs.com/issues/2908 Author: Markus Roberts Status: Accepted Priority: Normal Assigned to: Category: Rails Target version: Affected version: 0.25.1 Keywords: Branch: Several sites have reported rails resources with no tags, though it is not clear how or why this happens or how to reproduce it. This caused the problem observed (and fixed) #2863 but is itself unexplained. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
