Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title
Tristan Helmich commented on an issue
Re: Puppet 3.6.x future parser introduces dependency cycles
Andy Parker Is it already known when Puppet 3.7.0 will be released?
Add Comment
Puppet / PUP-2839
Puppet 3.6.x future parser introduces dependency cycles
In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --...
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/d/optout.
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Tristan Helmich commented on an issue Re: Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Hey is there some estimation available when this will be fixed? The new behavior makes it impossible to use the current version since my automatic module deployment is now broken. Thanks! Add Comment Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Since Puppet 3.6.0 the module tool is unable to install new modules if an already existing modules version does not conform to the MAJOR.MINOR.PATCH format. I believe this behaviour was introduced with the dependency resolver ( https://github.com/puppetlabs/puppet/commit/6fa68b54ac621d60dbf1b062f8dd66b186d1a87f ) How to reproduce problem: * Place a... 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
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title Tristan Helmich created an issue Puppet / PUP-2838 Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names Issue Type: Bug Affects Versions: 3.6.2, 3.6.1 Assignee: Unassigned Attachments: graph_fail.png Created: 25/Jun/14 5:30 AM Priority: Normal Reporter: Tristan Helmich Puppet generates invalid .dot files. If a resource name contains a quoted string the name is not escaped in the .dot file. Example content generated by puppet: Postgresql_psql[GRANT ALL ON DATABASE puppetdb TO puppetdb] [ fontsize = 8, label = Postgresql_psql[GRANT ALL ON DATABASE puppetdb TO puppetdb] ] resulting in something like this: The behavior has been reproduced with Puppet 3.6.1 and 3.6.2
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title
Tristan Helmich updated an issue
Puppet / PUP-2838
Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Change By:
Tristan Helmich
Puppetgeneratesinvalid.dotfiles.Ifaresourcenamecontainsaquotedstringthenameisnotescapedinthe.dotfile.Examplecontentgeneratedbypuppet:{code}Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb]]{code} resultinginsomethinglikethis:!graph_fail.png|thumbnail! Correctlyescapeditwouldlooklikethis:{code}Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\]]{code} resultinginsomethinglikethis: !graph_fail.png|thumbnail! ThebehaviorhasbeenreproducedwithPuppet3.6.1and3.6.2
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/d/optout.
Jira (PUP-2838) Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Title: Message Title
Tristan Helmich updated an issue
Puppet / PUP-2838
Puppet generates invalid .dot files due to missing escapes of quoted strings in resource names
Change By:
Tristan Helmich
Puppetgeneratesinvalid.dotfiles.Ifaresourcenamecontainsaquotedstringthenameisnotescapedinthe.dotfile.Examplecontentgeneratedbypuppet:{code}Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASEpuppetdbTOpuppetdb]]{code} Correctlyescapeditwouldlooklikethis:{code}Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\][fontsize=8,label=Postgresql_psql[GRANTALLONDATABASE\puppetdb\TO\puppetdb\]]{code} resultinginsomethinglikethis:!graph_fail.png|thumbnail!ThebehaviorhasbeenreproducedwithPuppet3.6.1and3.6.2
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/d/optout.
Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles
Title: Message Title Tristan Helmich created an issue Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles Issue Type: Bug Affects Versions: 3.6.2, 3.6.1, 3.6.0 Assignee: Andy Parker Components: DSL Created: 25/Jun/14 7:33 AM Labels: 3.6.0 future-parser Priority: Critical Reporter: Tristan Helmich In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): puppet apply --graph --modulepath /vagrant/modules/ --parser future futureparser_dependency_cycle.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /root//puppet/lib/puppet/settings.rb:1069:in `each') Notice: Compiled catalog for
Jira (PUP-2800) Ternary operator string match behavior change (future parser)
Title: Message Title
Tristan Helmich created an issue
Puppet / PUP-2800
Ternary operator string match behavior change (future parser)
Issue Type:
Bug
Affects Versions:
3.6.2, 3.6.0, 3.5.1
Assignee:
Unassigned
Created:
18/Jun/14 2:50 AM
Labels:
future-parser
Priority:
Blocker
Reporter:
Tristan Helmich
Hi,
the string matching behavior when using the ternary operator ('?') has changed sometime between versions 3.3.1 and 3.5.1 (future parser)
Before: Strings matched whether they are capitalized or not. (e.g. Debian and debian)
Now: Only lower case is matched (e.g. debian)
Problem: This breaks many existing puppet modules! Many modules match facts like ::osfamily. They will fail because the capitalized fact no longer matches.
Some example code illustrating the problem is available at https://gist.github.com/fadenb/a785f40de0c6c7567928
If you need futher information please do not hesitate to contact me (IRC is probably the fastest way)
Jira (PUP-2800) Selector string match behavior change (future parser)
Title: Message Title
Tristan Helmich updated an issue
Puppet / PUP-2800
Selector string match behavior change (future parser)
Change By:
Tristan Helmich
Summary:
Ternaryoperator Selector stringmatchbehaviorchange(futureparser)
Hi,thestringmatchingbehaviorwhenusing theternaryoperator('?') aselectorstatement haschangedsometimebetweenversions3.3.1and3.5.1(futureparser)*Before:*Stringsmatchedwhethertheyarecapitalizedornot.(e.g.Debiananddebian)*Now:*Onlylowercaseismatched(e.g.debian)*Problem:*Thisbreaksmanyexistingpuppetmodules!Manymodulesmatchfactslike::osfamily.Theywillfailbecausethecapitalizedfactnolongermatches.Someexamplecodeillustratingtheproblemisavailableathttps://gist.github.com/fadenb/a785f40de0c6c7567928Ifyouneedfutherinformationpleasedonothesitatetocontactme(IRCisprobablythefastestway)
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/d/optout.
Jira (PUP-2752) Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format
Title: Message Title Tristan Helmich created an issue Puppet / PUP-2752 Module tool fails to install new modules if some existing modules version is not Major.Minor.Patch format Issue Type: Bug Affects Versions: 3.6.2, 3.6.1, 3.6.0 Assignee: Pieter van de Bruggen Components: PMT Created: 11/Jun/14 1:20 AM Labels: moduletool pmt Priority: Critical Reporter: Tristan Helmich Since Puppet 3.6.0 the module tool is unable to install new modules if an already existing modules version does not conform to the MAJOR.MINOR.PATCH format. I believe this behaviour was introduced with the dependency resolver ( https://github.com/puppetlabs/puppet/commit/6fa68b54ac621d60dbf1b062f8dd66b186d1a87f ) How to reproduce problem: Place a module that does not conform with the X.Y.Z version format in your module folder (e.g. https://github.com/mrintegrity/puppet-pound ). To simulate this with another module just edit the metadata.json
Jira (PUP-1336) FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml
Title: Message Title Tristan Helmich commented on an issue Re: FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml Charlie Sharpsteen Should this migrated ticket be assigned to you? 6 Months ago during the Triage-a-thon I was told to assign it to you. Add Comment Puppet / PUP-1336 FWIW, puppetmaster doesn't notice changes to /etc/puppet/hiera.yaml pre If you change the :hierarchy: in /etc/puppet/hiera.yaml to add or remove a file foo (eg: foo.yaml) puppetmaster and it's clients won't notice this until you restart it. Ideally it would notice this with a mechanism such as inotify or similar. This can be an issue if you've added a classname::param: value entry in a new file, and you now expect t... 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
