Jira (HI-46) Hiera should support alternate environments
Title: Message Title Alex Harvey commented on an issue Re: Hiera should support alternate environments Add me to the 'this is a big problem that needs to be fixed' camp. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. 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-1625) Analyze unused modules
Title: Message Title Alex Harvey commented on PUP-1625 Re: Analyze unused modules Henrik Lindberg I need to develop a feature such as this for a project I'm working on, although enhancing Geppetto would take me too far afield. I'm intrigued by the idea of reusing the graphing subsystem though. If you or anyone else have any suggestions on how I could solve my problem and perhaps at the same time solve a portion of the enhancing Geppetto problem, I'd welcome the assistance and be more than happy to contribute the code. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1625) Analyze unused modules
Title: Message Title Alex Harvey commented on PUP-1625 Re: Analyze unused modules Henrik Lindberg I need to develop a feature such as this for a project I'm working on, although enhancing Geppetto would take me too far afield. I'm intrigued by the idea of reusing the graphing subsystem though. All I need is a tool that identifies classes that are defined but not declared anywhere, and I'm simply using site.pp for node classification. I then need to use that to identify data that exists in Hiera that isn't used by any class. If you or anyone else have any suggestions on how I could solve my problem and perhaps at the same time solve a portion of the enhancing Geppetto problem, I'd welcome the assistance and be more than happy to contribute the code. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1479) resources using parsedfile providers quietly move resources from default file to target
Title: Message Title Alex Harvey commented on PUP-1479 Re: resources using parsedfile providers quietly move resources from default file to target Is this the same bug or a different bug? http://ask.puppetlabs.com/question/17632/could-not-evaluate-ip-is-a-required-attribute-for-hosts/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1547) PR (2311) Undefined method `groups' for nil:NilClass
Title: Message Title
Alex Harvey commented on PUP-1547
Re: PR (2311) Undefined method `groups' for nil:NilClass
For anyone else searching for a workaround for earlier versions of Puppet, you can also add a global default in spec/fixtures/manifests/site.pp:
# workaround for https://tickets.puppetlabs.com/browse/PUP-1547
if $::operatingsystem == 'CentOS' {
User {
provider = 'useradd',
}
}
Carlos Sanchez's work around doesn't work on some earlier versions of puppet, e.g. the 3.3.1 system I'm using.
Add Comment
Jira (PUP-2076) Unit Tests Fail if not run as root (continues http://projects.puppetlabs.com/issues/16248)
Title: Message Title Alex Harvey commented on PUP-2076 Re: Unit Tests Fail if not run as root (continues http://projects.puppetlabs.com/issues/16248) A workaround for this is: In spec_helper.rb - ensure you are requiring 'puppetlabs_spec_helper/module_spec_helper' and not simply 'rspec-puppet', and then add the following: RSpec.configure do |c| ... c.before(:each) do Puppet.features.stubs(:root? = true) end end Add Comment
Jira (PUP-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Alex Harvey commented on PUP-3309 Re: puppet master --compile should be able to source facts from master inventory service I have documented the workaround on my blog here http://razorconsulting.com.au/compiling-a-puppet-catalog-on-a-workstation.html Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PUP-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-3309
puppet master --compile should be able to source facts from master inventory service
Change By:
Alex Harvey
Comment:
For anyone interested in the work around:I assume here that puppet has been installed in a bundle.{code}$ cat .bundle/config---BUNDLE_BIN: .bin{code}We won't have a puppet.conf file inside a bundle, so let's find the default value for $vardir:{code}$ ./.bin/puppet master --configprint vardir/Users/alexharvey/.puppet/var/{code}Good to read the help:{code}$ ./.bin/puppet help master{code}Note re --compile:{code}* --compile: Compile a catalogue and output it in JSON from the puppet master. Uses facts contained in the $vardir/yaml/ directory to compile the catalog.{code}This is a little confusing, because the YAML data for each node is actually expected to be in $vardir/yaml/facts/$fqdn.yaml. Be aware that Puppet provides a rather cryptic warning if this file is not found:{code}Warning: Host is missing hostname and/or domain: logdata01.example.com{code}If you see that, it really means that Puppet could find neither the $::fqdn nor $::domain facts.Here is the YAML file I created:{code}$ cat ~/.puppet/var/yaml/facts/logdata01.example.com.yaml--- values:hostname: logdata01fqdn: logdata01.example.comconcat_basedir: '/var/lib/puppet/concat'kernel: Linuxosfamily: RedHatoperatingsystem: RedHatoperatingsystemrelease: '6.5'ipaddress: '10.1.1.1'node_stream: uat1node_environment: uatnode_tier: managementnode_datacentre: cly name: logdata01.example.com{code}Now run the compile, telling Puppet on the command line locations for the module path, manifest dir, hiera config, and environment. Note I tested this using puppet 3.3.1.{code}$ ./.bin/puppet master --modulepath=spec/fixtures/modules --manifestdir=manifests --hiera_config=hiera.yaml --environment=uat1 --compile logdata01.example.com >catalog.json{code}Note that the first line of the file contained:{code}^[[mNotice: Compiled catalog for logdata01.example.com in environment uat1 in 4.79 seconds^[[0m{code}It's necessary to delete this in order to have valid JSON.
Add Comment
Jira (PUP-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Alex Harvey commented on PUP-3309 Re: puppet master --compile should be able to source facts from master inventory service For anyone interested in the work around: I assume here that puppet has been installed in a bundle. $ cat .bundle/config --- BUNDLE_BIN: .bin We won't have a puppet.conf file inside a bundle, so let's find the default value for $vardir: $ ./.bin/puppet master --configprint vardir /Users/alexharvey/.puppet/var/ Good to read the help: $ ./.bin/puppet help master Note re --compile:
Jira (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Folks, this bug means that Puppet itself is pretty much broken on RHEL & CentOS 7, probably the most popular Linux platform. How has this been allowed to remain open since 4.2.1? Every second module will use an init script style service in some place or other. Is it going to be fixed soon? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title
Alex Harvey commented on PUP-5296
Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Just to demonstrate how widely impacting this is, from a selection of 11 modules I'm using to build an ELK solution:
[root@centos-72-x64 ~]# puppet resource service network enable=true
Notice: /Service[network]/enable: enable changed 'false' to 'true'
service { 'network':
ensure => 'running',
enable => 'false',
}
[root@centos-72-x64 ~]# puppet resource service network enable=true
Notice: /Service[network]/enable: enable changed 'false' to 'true'
service { 'network':
ensure => 'running',
Jira (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Kylo Ginsberg wrote in the dev mailing list: This ticket looks like it might be addressed by (or should be considered while reviewing) two active PRs: https://github.com/puppetlabs/puppet/pull/4770 https://github.com/puppetlabs/puppet/pull/4755 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Great to hear, thanks everyone. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Kylo Ginsberg Can I up the priority on this? I don't get how this can be a normal priority. It's a blocker for me anyhow. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey updated an issue Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: Alex Harvey Affects Version/s: PUP 4.2.0 Affects Version/s: PUP 4.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Kylo Ginsberg Has this fallen off the radar again? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey updated an issue Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: Alex Harvey Affects Version/s: PUP 4.2.3 Affects Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PUP-7789) Manifest ordering not respected if resources are nested in defined types
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-7789
Manifest ordering not respected if resources are nested in defined types
Change By:
Alex Harvey
h3. Manifest ordering not always respectedWhen relying on manifest ordering to order things as they appear in the manifest, resources sometimes will not in fact be manifest-ordered if some of the resources are defined types.h3. To reproduce{code :puppet }class foo () { foo::bar { 'bar': }}define foo::bar { foo::baz { 'a': } foo::baz { 'b': } foo::baz { 'c': } File {ensure => file, } file { '/d': } file { '/e': } file { '/f': }}define foo::baz { file { "/$name": ensure => file }}include foo{code}Then:{code}$ puppet apply foo.pp --ordering=manifest --noop{code}h3. Expected resultI expect to see resources ordered as they appear in the manifest, namely:* Foo::Baz[a]* Foo::Baz[b]* Foo::Baz[c]* File[/d]* File[/e]* File[/f]h3. Actual result* File[/d]* File[/e]* File[/f]* Foo::Baz[a]* Foo::Baz[b]* Foo::Baz[c]{code}Notice: Compiled catalog for alexs-macbook-pro-2.local in environment production in 0.02 secondsNotice: /Stage[main]/Foo/Foo::Bar[bar]/File[/d]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/e]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/f]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[a]/File[/a]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[a]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[b]/File[/b]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[b]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[c]/File[/c]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[c]: Would have triggered 'refresh' from 1 eventNotice: Foo::Bar[bar]: Would have triggered 'refresh' from 6 eventsNotice: Class[Foo]: Would have triggered 'refresh' from 1 eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventNotice: Applied catalog in 0.07 seconds{code}Affects all versions of Puppet, including 3.8.7.Presumably it has always been like this. However, this is a very confusing ordering that seems to defeat the purpose of having manifest ordering at all.
Add Comment
Jira (PUP-7789) Manifest ordering not respected if resources are nested in defined types
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-7789
Manifest ordering not respected if resources are nested in defined types
Change By:
Alex Harvey
h3. Manifest ordering not always respectedWhen relying on manifest ordering to order things as they appear in the manifest, resources sometimes will not in fact be manifest-ordered if some of the resources are defined types.h3. To reproduce{code}class foo () { foo::bar { 'bar': }}define foo::bar { foo::baz { 'a': } foo::baz { 'b': } foo::baz { 'c': } File {ensure => file, } file { '/d': } file { '/e': } file { '/f': }}define foo::baz { File {ensure => file , } file { "/$name": ensure => file }}include foo{code}Then:{code}$ puppet apply foo.pp --ordering=manifest --noop{code}h3. Expected resultI expect to see resources ordered as they appear in the manifest, namely:* Foo::Baz[a]* Foo::Baz[b]* Foo::Baz[c]* File[/d]* File[/e]* File[/f]h3. Actual result* File[/d]* File[/e]* File[/f]* Foo::Baz[a]* Foo::Baz[b]* Foo::Baz[c]{code}Notice: Compiled catalog for alexs-macbook-pro-2.local in environment production in 0.02 secondsNotice: /Stage[main]/Foo/Foo::Bar[bar]/File[/d]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/e]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/f]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[a]/File[/a]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[a]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[b]/File[/b]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[b]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[c]/File[/c]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[c]: Would have triggered 'refresh' from 1 eventNotice: Foo::Bar[bar]: Would have triggered 'refresh' from 6 eventsNotice: Class[Foo]: Would have triggered 'refresh' from 1 eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventNotice: Applied catalog in 0.07 seconds{code}Affects all versions of Puppet, including 3.8.7.Presumably it has always been like this. However, this is a very confusing ordering that seems to defeat the purpose of having manifest ordering at all.
Add Comment
Jira (PUP-7789) Manifest ordering not respected if resources are nested in defined types
Title: Message Title
Alex Harvey created an issue
Puppet / PUP-7789
Manifest ordering not respected if resources are nested in defined types
Issue Type:
Bug
Affects Versions:
PUP 5.0.1, PUP 4.10.4, PUP 4.7.0
Assignee:
Unassigned
Created:
2017/07/19 8:05 PM
Priority:
Normal
Reporter:
Alex Harvey
When relying on manifest ordering to order things as they appear in the manifest, a rather confusing and unexpected ordering is observed if resources are nested within defined types.
To reproduce
class foo () {
foo::bar { 'bar': }
}
Jira (PUP-7789) Manifest ordering not respected if resources are nested in defined types
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-7789
Manifest ordering not respected if resources are nested in defined types
Change By:
Alex Harvey
h3. Manifest ordering not always respectedWhen relying on manifest ordering to order things as they appear in the manifest, resources sometimes will not in fact be manifest-ordered if some of the resources are defined types.h3. To reproduce{code}class foo () { foo::bar { 'bar': }}define foo::bar { foo::baz { 'a': } foo::baz { 'b': } foo::baz { 'c': } File {ensure => file, } file { '/d': } file { '/e': } file { '/f': }}define foo::baz { File {ensure => file, } file { "/$name": }}include foo{code}Then:{code}$ puppet apply foo.pp --ordering=manifest --noop{code}h3. Expected resultI expect to see files resources ordered as a they appear in the manifest , namely:* Foo::Baz[a]* Foo::Baz[ b , ]* Foo::Baz[ c , ]* File[/ d , ]* File[/ e , ]* File[/ f . ] h3. Actual result * File[/d]* File[/e]* File[/f]* Foo::Baz[a]* Foo::Baz[b]* Foo::Baz[c] {code}Notice: Compiled catalog for alexs-macbook-pro-2.local in environment production in 0.02 secondsNotice: /Stage[main]/Foo/Foo::Bar[bar]/File[/d]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/e]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/f]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[a]/File[/a]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[a]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[b]/File[/b]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[b]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[c]/File[/c]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[c]: Would have triggered 'refresh' from 1 eventNotice: Foo::Bar[bar]: Would have triggered 'refresh' from 6 eventsNotice: Class[Foo]: Would have triggered 'refresh' from 1 eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventNotice: Applied catalog in 0.07 seconds{code}Affects all versions of Puppet, including 3.8.7.Presumably it has always been like this. However, this is a very confusing ordering that seems to defeat the purpose of having manifest ordering at all.
Add Comment
Jira (PUP-7789) Manifest ordering not respected if resources are nested in defined types
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-7789
Manifest ordering not respected if resources are nested in defined types
Change By:
Alex Harvey
h3. Manifest ordering not always respected When relying on manifest ordering to order things as they appear in the manifest, a rather confusing and unexpected ordering is observed resources sometimes will not in fact be manifest-ordered if some of the resources are nested within defined types.h3. To reproduce{code}class foo () { foo::bar { 'bar': }}define foo::bar { foo::baz { 'a': } foo::baz { 'b': } foo::baz { 'c': } File {ensure => file, } file { '/d': } file { '/e': } file { '/f': }}define foo::baz { File {ensure => file, } file { "/$name": }}include foo{code}Then:{code}$ puppet apply foo.pp --ordering=manifest --noop{code}h3. Expected resultI expect to see files resources ordered as a, b, c, d, e, f.h3. Actual result{code}Notice: Compiled catalog for alexs-macbook-pro-2.local in environment production in 0.02 secondsNotice: /Stage[main]/Foo/Foo::Bar[bar]/File[/d]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/e]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/File[/f]/ensure: current_value 'absent', should be 'file' (noop)Notice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[a]/File[/a]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[a]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[b]/File[/b]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[b]: Would have triggered 'refresh' from 1 eventNotice: /Stage[main]/Foo/Foo::Bar[bar]/Foo::Baz[c]/File[/c]/ensure: current_value 'absent', should be 'file' (noop)Notice: Foo::Baz[c]: Would have triggered 'refresh' from 1 eventNotice: Foo::Bar[bar]: Would have triggered 'refresh' from 6 eventsNotice: Class[Foo]: Would have triggered 'refresh' from 1 eventNotice: Stage[main]: Would have triggered 'refresh' from 1 eventNotice: Applied catalog in 0.07 seconds{code}Affects all version versions of Puppet, including 3.8.7.Presumably it has always been like this. However, this is a very confusing ordering that seems to defeat the purpose of having manifest ordering at all.
Add Comment
Jira (PUP-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-3309
puppet master --compile should be able to source facts from master inventory service
Change By:
Alex Harvey
Currently ` {{ puppet master --compile ` }} requires facts to be sourced from $vardir/facts. It should either source it from the master inventory service (like puppetdb) or allow for an option to specify that it should do so.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 (PUP-9163) Lexer incorrectly identifying list starts inside heredocs
Title: Message Title Alex Harvey updated an issue Puppet / PUP-9163 Lexer incorrectly identifying list starts inside heredocs Change By: Alex Harvey Affects Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PUP-9163) Lexer incorrectly identifying list starts inside heredocs
Title: Message Title Alex Harvey updated an issue Puppet / PUP-9163 Lexer incorrectly identifying list starts inside heredocs Change By: Alex Harvey Affects Version/s: PUP 4.10.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PUP-9163) Lexer incorrectly identifying list starts inside heredocs
Title: Message Title
Alex Harvey created an issue
Puppet / PUP-9163
Lexer incorrectly identifying list starts inside heredocs
Issue Type:
Task
Affects Versions:
PUP 6.0.0, PUP 4.10.4
Assignee:
Unassigned
Created:
2018/09/24 4:05 AM
Priority:
Normal
Reporter:
Alex Harvey
Square brackets that are:
Inside heredocs
Inside an interpolation
Are sometimes being incorrectly lexed as TOKEN_LISTSTART. Simplest example Create test.pp:
$xxx = @("END")
${facts['os']['family']}
XXX XXX
END
Puppet apply it. What I expect Some text
Jira (PUP-9163) Lexer incorrectly identifying list starts inside heredocs
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-9163
Lexer incorrectly identifying list starts inside heredocs
Change By:
Alex Harvey
Square brackets that are: * Inside heredocs * Inside an interpolationAre sometimes being incorrectly lexed as TOKEN_LISTSTART.h3. Simplest exampleCreate test.pp:{code}$xxx = @("END")${facts['os']['family']}XXX XXXEND notice($xxx) {code}Puppet apply it.h3. What I expectSome text to appear showing the OS family.h3. What I actually see{code:none}Error: Could not parse for environment production: Syntax error at '[' (file: /Users/alexharvey/git/home/puppet-test/test.pp, line: 2, column: 14){code}h3. More infoNote the space inside XXX XX. That space is matching in the lexer on this line [here|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/parser/lexer2.rb#L192], leading to the '[' being lexed as TOKEN_LISTSTART.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are
Jira (PUP-9163) Lexer incorrectly identifying list starts inside heredocs
Title: Message Title
Alex Harvey updated an issue
Puppet / PUP-9163
Lexer incorrectly identifying list starts inside heredocs
Change By:
Alex Harvey
Square brackets that are:* Inside heredocs* Inside an interpolationAre sometimes being incorrectly lexed as TOKEN_LISTSTART. h3. Simplest exampleCreate test.pp: {code} $xxx = @("END")${facts['os']['family']}XXX XXXEND{code} Puppet apply it. h3. What I expectSome text to appear showing the OS family. h3. What I actually see {code:none} Error: Could not parse for environment production: Syntax error at '[' (file: /Users/alexharvey/git/home/puppet-test/ file7 test .pp, line: 2, column: 14){code} h3. More infoNote the space inside XXX XX. That space is matching in the lexer on this line [here|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/parser/lexer2.rb#L192], leading to the '[' being lexed as TOKEN_LISTSTART.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you
Jira (BOLT-1525) Add zypper implementation to package task
Title: Message Title Alex Harvey commented on BOLT-1525 Re: Add zypper implementation to package task Sorry, status change was an accident. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322358.1566923951000.129635.1570199160110%40Atlassian.JIRA.
