Jira (PUP-1968) Duplicate resources can make re-usable Forge modules difficult
Title: Message Title redmine.exporter created an issue Puppet / PUP-1968 Duplicate resources can make re-usable Forge modules difficult Issue Type: New Feature Assignee: Unassigned Created: 18/Mar/14 5:38 AM Labels: redmine Priority: Normal Reporter: redmine.exporter [EDIT] Re-working this description based on feedback in comment #7. User installs module A to provide a web application. User installs module B to provide a database server. Both module A and module B declare a package resource for foo. User declares classes from both module A and B on the same node. User receives duplicate resource declaration error, Puppet run fails. I wish to prevent customers of Forge and Puppet from experiencing this frustration, when both classes really do need that package for their functionality but cannot be used together as-is. I'd love direct questions if you need to understand this better from my perspective. Add
Jira (PUP-1969) puppet exec resource does not give clue about the error when the requested user does not exist
Title: Message Title
David Portabella created an issue
Puppet / PUP-1969
puppet exec resource does not give clue about the error when the requested user does not exist
Issue Type:
Bug
Affects Versions:
3.3.2
Assignee:
Unassigned
Created:
18/Mar/14 6:26 AM
Environment:
OSX 10.9.2
Priority:
Normal
Reporter:
David Portabella
exec { test:
command = /bin/echo hello,
user = 'non_existing_user'
}
$ sudo puppet apply test.pp
Notice: Compiled catalog for mac4c.local in environment production in 0.09 seconds
Error: /bin/echo hello returned 1 instead of one of [0]
Error: /Stage[main]//Exec[test]/returns: change from notrun to 0 failed: /bin/echo hello returned 1 instead of one of [0]
Notice: Finished catalog run in 0.05 seconds
It does not give any clue about the error! in this case, the problem is that the user does not exist.
executing the command with trace/debug/verbose options does not help neither.
sudo puppet apply --trace --debug --verbose a.pp
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
Tyler Parsons well thats mysterious, FYI no one else has complained of this (we have about 4000 confirmed installs).
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
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
Jira (PUP-1970) regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user
Title: Message Title
David Portabella created an issue
Puppet / PUP-1970
regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Unassigned
Created:
18/Mar/14 6:54 AM
Priority:
Normal
Reporter:
David Portabella
exec { test:
command = /bin/echo hello; exit 1,
user = 'user1'
}
$ sudo puppet apply test.pp
Notice: Compiled catalog for ##host##.example.com in environment production in 0.06 seconds
Notice: /Stage[main]/Main/Exec[test]/returns: hello
Error: /bin/echo hello; exit 1 returned 1 instead of one of [0]
Error: /Stage[main]/Main/Exec[test]/returns: change from notrun to 0 failed: /bin/echo hello; exit 1 returned 1 instead of one of [0]
Notice: Finished catalog run in 0.25 seconds
This works as expected (puppet 3.3.2 on OSX).
However, on puppet 3.4.3 (puppet entreprise 3.2.0) on readhat 6, when executing the previous code, this line does not appear:
Notice: /Stage[main]/Main/Exec[test]/returns: hello
the line appears again if I remove the user paramater, or I set user = 'root'.
adding --trace --debug --verbose does not help neither.
Jira (PUP-1971) puppet apply --debug does not provide stdout and stderr log of puppet exec
Title: Message Title
David Portabella created an issue
Puppet / PUP-1971
puppet apply --debug does not provide stdout and stderr log of puppet exec
Issue Type:
Bug
Affects Versions:
3.3.2
Assignee:
Unassigned
Created:
18/Mar/14 7:05 AM
Priority:
Normal
Reporter:
David Portabella
compare this:
exec { test:
command = /bin/echo hello; exit 1,
}
$ puppet apply test.pp
Notice: Compiled catalog for mac4c.local in environment production in 0.09 seconds
Notice: /Stage[main]//Exec[test]/returns: hello
Error: /bin/echo hello; exit 1 returned 1 instead of one of [0]
Error: /Stage[main]//Exec[test]/returns: change from notrun to 0 failed: /bin/echo hello; exit 1 returned 1 instead of one of [0]
Notice: Finished catalog run in 0.06 seconds
with:
exec { test:
command = /bin/echo hello; exit 0,
}
$ puppet apply test.pp
Notice: Compiled catalog for mac4c.local in environment production in 0.10 seconds
Notice: /Stage[main]//Exec[test]/returns: executed successfully
Notice: Finished catalog run in 0.08 seconds
We see that in this case we don't get this line:
Jira (PDB-510) ERROR: duplicate key value violates unique constraint catalogs_pkey
Title: Message Title
Kenneth Barber commented on an issue
Re: ERROR: duplicate key value violates unique constraint catalogs_pkey
Tyler Parsons what about your postgresql logs? Anything strange in there during the upgrade period? Or later?
Perhaps this happened post migration, it would seem more logical that way. Those existing ~1800 records wouldn't have received ID's for no reason - I'd guess the sequence was working fine at that point. Without having the ability to see what changes might have occurred to the sequence however its hard to guess. Are you sure someone didn't just change the sequence? It would have to be very deliberate.
There is also the possibility this is a bug in PostgreSQL, but that seems very unlikely.
Add Comment
PuppetDB / PDB-510
ERROR: duplicate key value violates unique constraint catalogs_pkey
We receive these errors every few minutes. Our logs indicate that these error began to occurring once our puppetdb instance was upgraded from 1.5.2 - 1.6.2. {code} 2014-03-12 15:33:03,107 ERROR [command-proc-82] [puppetdb.command] [7b979257-dda8-4d46-b8b2-242b88611523] [replace catalog] Retrying after attempt 12, due to: org.postgresql.util.PSQLEx...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1972) pkgdmg can fail when ejecting disk images
Title: Message Title Keith Duncan created an issue Puppet / PUP-1972 pkgdmg can fail when ejecting disk images Issue Type: Bug Affects Versions: 3.x Assignee: Andy Parker Components: Modules Created: 18/Mar/14 7:28 AM Priority: Normal Reporter: Keith Duncan When ejecting disk images, if processes still have files open on the volume then the eject fails and anything that depends on the package will also fail to install. I was able to capture the processes using the packages on the volume using `lsof`. ``` COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME mds 43 root 15r DIR 1,4 238 2 /private/tmp/dmg.uQT3Dp installd 691 root 4r REG 1,4 30079000 132 /private/tmp/dmg.uQT3Dp/Packages/MacOSX10_9_SDK.pkg installd 691 root 5r REG 1,4 30079000 132 /private/tmp/dmg.uQT3Dp/Packages/MacOSX10_9_SDK.pkg installer 3164 root 4r REG 1,4 657793 130 /private/tmp/dmg.uQT3Dp/Command Line Tools (OS X 10.9).pkg ``` I’ve opened https://github.com/puppetlabs/puppet/pull/2366 to address the issue.
Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly
Title: Message Title
Daniele Sluijters created an issue
Puppet / PUP-1973
futurepaser doesn't bind variables in templates correctly
Issue Type:
Bug
Affects Versions:
3.5.0 RC
Assignee:
Henrik Lindberg
Created:
18/Mar/14 7:37 AM
Priority:
Major
Reporter:
Daniele Sluijters
If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten{{ on {{nil:NilClass{{ in the ntp.conf template.
This happens because for some reason {{@restrict{{ and every other variable in the template isn't bound, ergo nil.
If I explicitly add a $restricted = $::ntp::restricted to config.pp it works.
Add Comment
Jira (PUP-1974) Mechanism for securing sensitive catalog data
Title: Message Title Patrick Mooney created an issue Puppet / PUP-1974 Mechanism for securing sensitive catalog data Issue Type: Improvement Affects Versions: 3.x Assignee: Kylo Ginsberg Components: Types and Providers Created: 18/Mar/14 7:39 AM Priority: Normal Reporter: Patrick Mooney Sensitive information such as passwords or key files contained within Puppet catalogs leaks into locations such as PuppetDB or syslog. This elevates the necessary security that must be enforced on these external systems. It would be valuable to give manifest/module authors the ability to specify resource properties (such as attributes or titles) which are sensitive. Components downstream from the catalog compiler could then choose how to handle sensitive data. For example, the master could redact such fields from the catalog before sending it to PuppetDB. The agent could be configured to obscure sensitive resource titles from the log when they are acted upon. One possible way to do this would be the addition of a sensitive resource type that is compiled into the catalog. Each instance would specific resource fields to be selected and the preferred means of redaction.
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Gerrard Geldenhuis commented on an issue Re: Using 'ip addr' over ifconfig I don't think there is any valid argument any more for using ifconfig as default. ifconfig has been marked as deprecated for quite a while and we all should really just use ip and so should facter. That being said I have yet to get into the habit of using ip myself. Add Comment Facter / FACT-184 Using 'ip addr' over ifconfig pre # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:85: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: /sbin/ifconfig -a /usr/bin/facter:54: command not found: dnsdomainname /usr/bin/facter:54: command not found: domainname /usr/bin/facter:54: command not found: /sbin/ifconfig architecture = i386 domain = int... 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
Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly
Title: Message Title
Daniele Sluijters commented on an issue
Re: futurepaser doesn't bind variables in templates correctly
I've come to understand that this is intended behaviour, dynamic scoping is explicitly turned 'off' in future evaluator. However, there's puppetlabs modules that (ab)use this feature right now.
Add Comment
Puppet / PUP-1973
futurepaser doesn't bind variables in templates correctly
If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten{{ on {{nil:NilClass{{ in the ntp.conf template. This happens because for some reason {{@restrict{{ and every other variable in the template isn't bound, ergo nil. If I explicitly add a {{$restricted = $::ntp::restricted}} to co...
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
Jira (PUP-1585) PR (2342) cron resources with target specified generate duplicate entries
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1585 PR (2342) cron resources with target specified generate duplicate entries Change By: Kurt Wall Assignee: TonyVu KurtWall 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-1585) PR (2342) cron resources with target specified generate duplicate entries
Title: Message Title
Kurt Wall commented on an issue
Re: PR (2342) cron resources with target specified generate duplicate entries
The behavior described in this bug is fixed in
# cat cron.pp
cron { 'cron-test':
ensure = present,
month = '11',
command = '/bin/true',
target = 'vagrant',
}
# crontab -l -u vagrant
no crontab for vagrant
# puppet apply cron.pp
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.04 seconds
Notice: /Stage[main]/Main/Cron[cron-test]/ensure: created
Notice: Finished catalog run in 0.06 seconds
# crontab -l -u vagrant
# HEADER: This file was autogenerated at Tue Mar 18 09:05:47 -0700 2014 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: cron-test
* * * 11 * /bin/true
# puppet apply cron.pp
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.04 seconds
Notice: Finished catalog run in 0.05 seconds
# crontab -l -u vagrant
# HEADER: This file was autogenerated at Tue Mar 18 09:05:47 -0700 2014 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: cron-test
* * * 11 * /bin/true
Note that the duplicate entry is not created. Tony Vu is there a reason not to mark this Resolved?
Add Comment
Puppet / PUP-1585
PR (2342) cron resources with target specified generate duplicate entries
The following resource
Jira (HI-225) allow interleaved querying of backends
Title: Message Title
Kjetil Torgrim Homme created an issue
Hiera / HI-225
allow interleaved querying of backends
Issue Type:
New Feature
Assignee:
Adrien Thebo
Components:
Community
Created:
18/Mar/14 9:13 AM
Environment:
any
Priority:
Normal
Reporter:
Kjetil Torgrim Homme
Original Estimate:
4 hours
Remaining Estimate:
1 hour
When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend.
Given a hiera.yaml like
:hierarchy:
site-%{::site}
Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-1973
futurepaser doesn't bind variables in templates correctly
Change By:
Hunter Haugen
Ifyourunthepuppetlabs-ntpmodulewithparser=futureon3.5.0-rc1itwillbreakcomplainingthatitcan'tcall{{flatten {{ }} on{{nil:NilClass {{ }} inthentp.conftemplate.Thishappensbecauseforsomereason{{@restrict {{ }} andeveryothervariableinthetemplateisn'tbound,ergonil.IfIexplicitlyadda{{$restricted=$::ntp::restricted}}toconfig.ppitworks.
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-1585) PR (2342) cron resources with target specified generate duplicate entries
Title: Message Title
Tony Vu commented on an issue
Re: PR (2342) cron resources with target specified generate duplicate entries
I agree Kurt Wall, the behavior is fixed; my only concern is that Charlie Sharpsteen thought that this and PUP-1624 should be tested in tandem, and I am unsure if I can pass PUP-1624; my comment in that ticket is not exactly specific to that bug's writeup, but seems related enough to warrant a discussion about whether to fix it in that issue or create a new ticket.
Add Comment
Puppet / PUP-1585
PR (2342) cron resources with target specified generate duplicate entries
The following resource results in duplicate cron entry added with each puppet run: {noformat} cron { 'bacula_vacuumdb': ensure = present, minute = '00', hour = '12', command = 'vacuumdb --analyze -U postgres bacula', target = 'postgres', }{noformat} Example of Cron: {noformat}~# crontab -l ...
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
Jira (PUP-1749) Puppet module tool does not work on Solaris
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-1749 Puppet module tool does not work on Solaris Change By: Tony Vu Assignee: TonyVu 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 (FACT-383) Create 1.7.5 packages
Title: Message Title Moses Mendoza created an issue Facter / FACT-383 Create 1.7.5 packages Issue Type: Sub-task Assignee: Moses Mendoza Created: 18/Mar/14 9:54 AM Priority: Normal Reporter: Moses Mendoza 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 (FACT-382) Release Facter 1.7.5 for Ubuntu Trusty 14.04
Title: Message Title Moses Mendoza created an issue Facter / FACT-382 Release Facter 1.7.5 for Ubuntu Trusty 14.04 Issue Type: Task Affects Versions: 1.7.5 Assignee: Eric Sorenson Created: 18/Mar/14 9:54 AM Priority: Normal Reporter: Moses Mendoza 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
Jira (FACT-385) ship packages to production
Title: Message Title Moses Mendoza created an issue Facter / FACT-385 ship packages to production Issue Type: Sub-task Affects Versions: 1.7.5 Assignee: Unassigned Created: 18/Mar/14 9:55 AM Priority: Normal Reporter: Moses Mendoza 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
Jira (PUP-1973) futurepaser doesn't bind variables in templates correctly
Title: Message Title
Henrik Lindberg commented on an issue
Re: futurepaser doesn't bind variables in templates correctly
The restriction is implemented as a solution to
PUP-1220
- investigating if this restricted too much of the visibility.
Add Comment
Puppet / PUP-1973
futurepaser doesn't bind variables in templates correctly
If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten}} on {{nil:NilClass}} in the ntp.conf template. This happens because for some reason {{@restrict}} and every other variable in the template isn't bound, ergo nil. If I explicitly add a {{$restricted = $::ntp::restricted}} to co...
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.
Jira (FACT-384) smoke-test packages
Title: Message Title Moses Mendoza created an issue Facter / FACT-384 smoke-test packages Issue Type: Sub-task Affects Versions: 1.7.5 Assignee: Eric Sorenson Created: 18/Mar/14 9:55 AM Priority: Normal Reporter: Moses Mendoza 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
Jira (FACT-387) CLONE - Create 1.7.5 packages
Title: Message Title Moses Mendoza created an issue Facter / FACT-387 CLONE - Create 1.7.5 packages Issue Type: Sub-task Assignee: Moses Mendoza Created: 18/Mar/14 9:56 AM Priority: Normal Reporter: Moses Mendoza 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 (HI-228) CLONE - smoke-test packages
Title: Message Title Moses Mendoza moved an issue Hiera / HI-228 CLONE - smoke-test packages Change By: Moses Mendoza Affects Version/s: 1.7.5 Key: FACT HI - 388 228 Project: Facter Hiera 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 (HI-227) Create 1.3.2 packages
Title: Message Title Moses Mendoza updated an issue Hiera / HI-227 Create 1.3.2 packages Change By: Moses Mendoza Summary: CLONE- Create1. 7 3 . 5 2 packages 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 (FACT-386) Release Hiera 1.3.2 for Ubuntu Trusty 14.04
Title: Message Title Moses Mendoza created an issue Facter / FACT-386 Release Hiera 1.3.2 for Ubuntu Trusty 14.04 Issue Type: Task Affects Versions: 1.7.5 Assignee: Eric Sorenson Created: 18/Mar/14 9:56 AM Priority: Normal Reporter: Moses Mendoza 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
Jira (FACT-388) CLONE - smoke-test packages
Title: Message Title Moses Mendoza created an issue Facter / FACT-388 CLONE - smoke-test packages Issue Type: Sub-task Affects Versions: 1.7.5 Assignee: Eric Sorenson Created: 18/Mar/14 9:56 AM Priority: Normal Reporter: Moses Mendoza 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.
Jira (HI-228) smoke-test packages
Title: Message Title Moses Mendoza updated an issue Hiera / HI-228 smoke-test packages Change By: Moses Mendoza Summary: CLONE- smoke-testpackages 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 (HI-227) CLONE - Create 1.7.5 packages
Title: Message Title Moses Mendoza moved an issue Hiera / HI-227 CLONE - Create 1.7.5 packages Change By: Moses Mendoza Key: FACT HI - 387 227 Project: Facter Hiera 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 (HI-229) CLONE - ship packages to production
Title: Message Title Moses Mendoza moved an issue Hiera / HI-229 CLONE - ship packages to production Change By: Moses Mendoza Affects Version/s: 1.7.5 Key: FACT HI - 389 229 Project: Facter Hiera 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 (HI-226) Release Hiera 1.3.2 for Ubuntu Trusty 14.04
Title: Message Title Moses Mendoza moved an issue Hiera / HI-226 Release Hiera 1.3.2 for Ubuntu Trusty 14.04 Change By: Moses Mendoza Affects Version/s: 1.7.5 Affects Version/s: 1.3.2 Key: FACT HI - 386 226 Project: Facter Hiera 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 (FACT-389) CLONE - ship packages to production
Title: Message Title Moses Mendoza created an issue Facter / FACT-389 CLONE - ship packages to production Issue Type: Sub-task Affects Versions: 1.7.5 Assignee: Unassigned Created: 18/Mar/14 9:56 AM Priority: Normal Reporter: Moses Mendoza 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
Jira (HI-229) ship packages to production
Title: Message Title Moses Mendoza updated an issue Hiera / HI-229 ship packages to production Change By: Moses Mendoza Summary: CLONE- shippackagestoproduction 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-1975) Environment is not passed to facts indirector during compilation
Title: Message Title Kenneth Barber created an issue Puppet / PUP-1975 Environment is not passed to facts indirector during compilation Issue Type: Bug Assignee: Unassigned Created: 18/Mar/14 10:07 AM Priority: Normal Reporter: Kenneth Barber The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector. We utilise this call as part of the PuppetDB terminus to save facts. The problem however, is that the environment is not passed through to the indirector, which means we cannot preserve facts with the environment they were created from so we can complete PDB-453. I have a patch that remedies this, and it is forthcoming. Eric Sorenson, Andy Parker ... I'm not sure if this is strictly a bug or non-feature, what do you think? I simply ask because I'm not sure what branch/fix version to target this for. Add Comment
Jira (PUP-1975) Environment is not passed to facts indirector during compilation
Title: Message Title Kenneth Barber commented on an issue Re: Environment is not passed to facts indirector during compilation PR is here: https://github.com/puppetlabs/puppet/pull/2444 Add Comment Puppet / PUP-1975 Environment is not passed to facts indirector during compilation The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector. We utilise this call as part of the PuppetDB terminus to save facts. The problem however, is that the environment is not passed through to the indirector, which means we cannot prese... 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 (HI-225) allow interleaved querying of backends
Title: Message Title Adrien Thebo updated an issue Hiera / HI-225 allow interleaved querying of backends Change By: Adrien Thebo Component/s: Community 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 (HI-225) allow interleaved querying of backends
Title: Message Title Adrien Thebo updated an issue Hiera / HI-225 allow interleaved querying of backends Change By: Adrien Thebo Assignee: AdrienThebo 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 (HI-174) PR (175): (CPR-12) Ensure hiera works with alternatives on debian - haus
Title: Message Title Adrien Thebo assigned an issue to Unassigned Hiera / HI-174 PR (175): (CPR-12) Ensure hiera works with alternatives on debian - haus Change By: Adrien Thebo Assignee: AdrienThebo 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 (HI-175) PR (176): (CPR-12) Ensure hiera works with alternatives on debian - haus
Title: Message Title Adrien Thebo assigned an issue to Unassigned Hiera / HI-175 PR (176): (CPR-12) Ensure hiera works with alternatives on debian - haus Change By: Adrien Thebo Assignee: AdrienThebo 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-1973) futurepaser doesn't bind variables in templates correctly
Title: Message Title
Henrik Lindberg commented on an issue
Re: futurepaser doesn't bind variables in templates correctly
PUP-1220
accidentally turns off access to inherited scope (as a consequence of turning off dynamic scope).
Add Comment
Puppet / PUP-1973
futurepaser doesn't bind variables in templates correctly
If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten}} on {{nil:NilClass}} in the ntp.conf template. This happens because for some reason {{@restrict}} and every other variable in the template isn't bound, ergo nil. If I explicitly add a {{$restricted = $::ntp::restricted}} to co...
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
Jira (PUP-1973) future parser doesn't bind variables from inherited scope
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1973 future parser doesn't bind variables from inherited scope Change By: Henrik Lindberg Summary: futurepaser futureparser doesn'tbindvariables intemplatescorrectly frominheritedscope 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-1973) future parser doesn't bind variables from inherited scope
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1973 future parser doesn't bind variables from inherited scope Change By: Henrik Lindberg Component/s: DSL Story Points: 1 Fix Version/s: 3.5.0 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-1975) Environment transaction_uuid is not passed to facts indirector during compilation
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-1975 Environment transaction_uuid is not passed to facts indirector during compilation Change By: Kenneth Barber Summary: Environment transaction_uuid isnotpassedtofactsindirectorduringcompilation 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-1973) future parser doesn't bind variables from inherited scope
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1973 future parser doesn't bind variables from inherited scope Change By: Henrik Lindberg Sprint: Week2014-3-12to2014-3-19 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-1975) Environment transaction_uuid is not passed to facts indirector during compilation
Title: Message Title Kenneth Barber commented on an issue Re: Environment transaction_uuid is not passed to facts indirector during compilation After talking to Andy Parker we've decided to extend this to transaction_uuid also, since the information may be useful later on when we start doing more intelligent data marriage between facts/catalogs/reports in PuppetDB. Add Comment Puppet / PUP-1975 Environment transaction_uuid is not passed to facts indirector during compilation The class Puppet::Indirector::Catalog::Compiler contains a method 'extract_facts_from_request' which extracts facts from the request to be stored in a cache indirector. We utilise this call as part of the PuppetDB terminus to save facts. The problem however, is that the environment is not passed through to the indirector, which means we cannot prese... 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
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Pieter van de Bruggen created an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Issue Type: Improvement Affects Versions: 3.6.0 Assignee: Pieter van de Bruggen Created: 18/Mar/14 10:37 AM Priority: Normal Reporter: Pieter van de Bruggen `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecation warning. Let's call this the legacy build process. If the user provides a metadata.json file at the root of their module, PMT will use it exclusively to build the release. Let's call this the v3 build process. If the user providers both a Modulefile and metadata.json, PMT will use the v3 build process, ignoring the Modulefile but issuing a warning against including both files in the module root. The legacy build process will issue a deprecation warning but will otherwise behave as it does today.
Jira (PUP-1624) PR (2342) Cron handles crontab's equality of target and user strangely
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: PR (2342) Cron handles crontab's equality of target and user strangely
Thanks for looking into this Tony!
I think the real heart of this issue is that the user and target properties are redundant. Both properties try to manage which crontab a job gets written into. Given the redundancy, users shouldn't be setting both user and target on a single job and definitely shouldn't be setting them to different values — we need to update the docs to make this clear. I've created DOCUMENT-53 to track this task.
I think this patch still resolves the main symptom: setting target alone was buggy and caused the resource to loop or flicker.
Add Comment
Puppet / PUP-1624
PR (2342) Cron handles crontab's equality of target and user strangely
When managing the target property of a cronjob, the user property uses its default instead (which is the user running puppet). To the crontab provider, these are basically the same, and there is code to handle them equally. Through the mixtures of defaults and actual supplied values, though, bizarre behaviors come up: {code} # HEADER: This file was au...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Pieter van de Bruggen created an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Issue Type: Improvement Affects Versions: 3.6.0 Assignee: Pieter van de Bruggen Created: 18/Mar/14 10:40 AM Priority: Normal Reporter: Pieter van de Bruggen Since we're moving away from the Modulefile as the canonical source of metadata, we should do our users the favor of no longer generating a Modulefile – instead, we should generate the metadata.json file we expect them to use. Add Comment This message
Jira (PUP-1978) future parser doesn't accept empty array as title
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-1978 future parser doesn't accept empty array as title Issue Type: Bug Affects Versions: 3.5.0 RC Assignee: Henrik Lindberg Created: 18/Mar/14 10:41 AM Priority: Major Reporter: Daniele Sluijters When passed an empty array the future parser ends up giving an unhelpful error message Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail' /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PResourceType' /usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:74:in `visit_this_2' /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:25:in `access' /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:484:in `eval_AccessExpression' /usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:64:in `visit_this_1' The current parser accepts an empty array as an regiment to Group (I have no idea what it does with it though).
Jira (HI-225) allow interleaved querying of backends
Title: Message Title
Kjetil Torgrim Homme commented on an issue
Re: allow interleaved querying of backends
as indicated by Time Tracking, I have a patch ready, but I haven't updated the rspec tests yet. will add pull request when tests pass again
Add Comment
Hiera / HI-225
allow interleaved querying of backends
When Hiera processes the sources, it will iterate through them completely, first with the first backend, then the next backend. Given a hiera.yaml like :hierarchy: - site-%{::site} - common :backends: - yaml - json and the files site-external.json and common.yaml, the value in common.yaml will override the value in site-e...
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-1975) Environment transaction_uuid is not passed to facts indirector during compilation
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-1975 Environment transaction_uuid is not passed to facts indirector during compilation Change By: Kenneth Barber Affects Version/s: 3.5.0RC Fix Version/s: 3.5.0 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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Assignee: PietervandeBruggen 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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Fix Version/s: 3.6.0 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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Affects Version/s: 3.6.0 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-1979) future parser class reference inside class doesn't work
Title: Message Title
Daniele Sluijters created an issue
Puppet / PUP-1979
future parser class reference inside class doesn't work
Issue Type:
Bug
Affects Versions:
3.5.0 RC
Assignee:
Henrik Lindberg
Created:
18/Mar/14 10:56 AM
Priority:
Normal
Reporter:
Daniele Sluijters
If you have a class that does something like this:
class { '::iptables::packages': } -
class { '::iptables::configs': } -
class { '::iptables::update': } -
class { '::iptables::services': } -
Class['::iptables']
This works with current parser and avoid the need to use an explicit anchor resource. However, future parser doesn't accept this and throws the following error:
Debug: Adding relationship from Class[Iptables::Configs] to Class[Iptables::Services] with 'before'
Error: Could not find resource 'Class[::Iptables]' for relationship from 'Class[Iptables::Services]' on node super-secret-foo
Jira (PUP-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Change By: Michelle Johansen Affects Version/s: 3.6.0 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Change By: Michelle Johansen Fix Version/s: 3.6.0 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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Pieter van de Bruggen commented on an issue Re: `puppet module build` should use `metadata.json` as input format Code can be found in https://github.com/puppetlabs/puppet/pull/2436. Add Comment Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati... 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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Component/s: PE 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Change By: Michelle Johansen Component/s: PE 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Change By: Michelle Johansen Assignee: PietervandeBruggen 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: `puppet module build` should create `metadata.json` instead of `Modulefile`
Code for this can be found in https://github.com/puppetlabs/puppet/pull/2440.
Add Comment
Puppet / PUP-1977
`puppet module build` should create `metadata.json` instead of `Modulefile`
Since we're moving away from the {{Modulefile}} as the canonical source of metadata, we should do our users the favor of no longer generating a {{Modulefile}} – instead, we should generate the {{metadata.json}} file we expect them to use.
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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Fix Version/s: 3.6.0 Fix Version/s: 3.5.1 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Change By: Michelle Johansen Fix Version/s: 3.6.0 Fix Version/s: 3.5.1 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 (PDB-516) Store transaction_uuid with fact submission
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-516 Store transaction_uuid with fact submission Issue Type: New Feature Assignee: Unassigned Created: 18/Mar/14 11:08 AM Priority: Normal Reporter: Kenneth Barber With PUP-1975 we discovered that environment and transaction_uuid was not being sent to the terminus. This FR covers the inclusion of transaction_uuid during fact submission so we can marry facts/catalogs/reports later on. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1892) PR (2420) Puppet remote fileserver facility for file resources.
Title: Message Title Roger Spencer commented on an issue Re: PR (2420) Puppet remote fileserver facility for file resources. I've been banging my head on this bug for a few days until I realized the file_content was going to the wrong master. If I downgrade the client to 2.7.22 the remote master file source works. Apparently anything 3.x doesn't work. Add Comment Puppet / PUP-1892 PR (2420) Puppet remote fileserver facility for file resources. As of current release, due to the use of source_or_content.full_path, the hostname is stripped from attempts to handle file_content calls in type/file.rb. Because of this, it correctly calls file_metadata from the proper server, but then calls the puppetmaster instead of the remote fileserver for content retrieval, which fails. This resolution might st... 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
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Adrien Thebo updated an issue Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host Change By: Adrien Thebo Story Points: 3 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-1570) Puppet Agent hanging on applying configuration
Title: Message Title Eric Sorenson commented on an issue Re: Puppet Agent hanging on applying configuration I'm going to mark this closed/wontfix unless someone is experiencing the problem and can NOT trace it to network connections from facts. I think the relevant issue and place to fix it is PUP-179, so I'm marking this related; please add yourself as a watcher there to see this through to resolution. Add Comment Puppet / PUP-1570 Puppet Agent hanging on applying configuration Probably worth noting, I run a setup with a puppetmaster and the agents connecting to that to get their manifests. My puppet agents get stuck applying configuration every once and awhile. For example: root 769 0.0 2.8 42616 29292 ? S Jan16 0:02 puppet agent: applying configurat root 28554 0.4 2.5 38244 25996 ? Ss... 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
Jira (PUP-179) Puppet needs to delegate all fact loading to Facter
Title: Message Title Eric Sorenson commented on an issue Re: Puppet needs to delegate all fact loading to Facter As noted in PUP-1570 , a fix for this should take into account the unreliability of facter's returning facts in a timely way. Add Comment Puppet / PUP-179 Puppet needs to delegate all fact loading to Facter 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-1978) future parser doesn't accept empty array as title
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-1978
future parser doesn't accept empty array as title
Change By:
Daniele Sluijters
Whenpassedanemptyarraythefutureparserendsupgivinganunhelpfulerrormessage{{Error:EvaluationError:Group[]accepts1argument.Got0onnodesuper-secret-foo}}{noformat}/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in`fail'/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in`access_PResourceType'/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:74:in`visit_this_2'/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:25:in`access'/usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:484:in`eval_AccessExpression'/usr/lib/ruby/vendor_ruby/puppet/pops/visitor.rb:64:in`visit_this_1'{noformat}Thecurrentparseracceptsanemptyarrayasan regiment argument toGroup(Ihavenoideawhatitdoeswithitthough ,probablyignoresit ).
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-1978) future parser doesn't accept empty array as title
Title: Message Title
Daniele Sluijters commented on an issue
Re: future parser doesn't accept empty array as title
I was mostly hoping it would be possible for Puppet to tell me where this is being triggered from. Similar to evaluator a manifest/line or a 'calling resource' that triggered this.
Add Comment
Puppet / PUP-1978
future parser doesn't accept empty array as title
When passed an empty array the future parser ends up giving an unhelpful error message {{Error: Evaluation Error: Group[] accepts 1 argument. Got 0 on node super-secret-foo}} {noformat} /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:19:in `fail' /usr/lib/ruby/vendor_ruby/puppet/pops/evaluator/access_operator.rb:443:in `access_PRe...
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
Jira (PUP-1978) future parser doesn't accept empty array as title
Title: Message Title Daniele Sluijters updated an issue Puppet / PUP-1978 future parser doesn't accept empty array as title Change By: Daniele Sluijters Priority: Major Normal 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-1979) future parser class reference inside class doesn't work
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-1979
future parser class reference inside class doesn't work
Change By:
Daniele Sluijters
Ifyouhaveaclassthatdoessomethinglikethis:{noformat}class iptables { class{ '::iptables::packages':}-class{'::iptables::configs':}-class{'::iptables::update':}-class{'::iptables::services':}-Class['::iptables'] } {noformat}Thisworkswithcurrentparserandavoidtheneedtouseanexplicitanchorresource.However,futureparserdoesn'tacceptthisandthrowsthefollowingerror:{noformat}Debug:AddingrelationshipfromClass[Iptables::Configs]toClass[Iptables::Services]with'before'Error:Couldnotfindresource'Class[::Iptables]'forrelationshipfrom'Class[Iptables::Services]'onnodesuper-secret-foo{noformat}
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-1973) future parser doesn't bind variables from inherited scope
Title: Message Title
Henrik Lindberg commented on an issue
Re: future parser doesn't bind variables from inherited scope
Also merged to master: eb09ae7dd2e7946796a27ab428f5c660459e368d
Add Comment
Puppet / PUP-1973
future parser doesn't bind variables from inherited scope
If you run the puppetlabs-ntp module with parser=future on 3.5.0-rc1 it will break complaining that it can't call {{flatten}} on {{nil:NilClass}} in the ntp.conf template. This happens because for some reason {{@restrict}} and every other variable in the template isn't bound, ergo nil. If I explicitly add a {{$restricted = $::ntp::restricted}} to co...
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-1980) Uppercase tags in exported resource
Title: Message Title
Frank Grtzner created an issue
Puppet / PUP-1980
Uppercase tags in exported resource
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Unassigned
Created:
18/Mar/14 12:38 PM
Environment:
Linux
Priority:
Normal
Reporter:
Frank Grtzner
Hi!
As already mentioned in this 4 years old bug https://projects.puppetlabs.com/issues/3045 (for some reason it's not possible to export it to Jira), it's still not possible to use tags with uppercase characters with exported resources.
You can test this easily by applying the following class to multiple nodes - if the tag contains uppercase characters, the exporting node will never realize it's own exported file.
class test {
@@file { /tmp/export-$ {fqdn}
: content = 'a', tag = tEst, }
File | tag == tEst |
}
Jira (PUP-1978) future parser doesn't accept empty array as title
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1978 future parser doesn't accept empty array as title Change By: Henrik Lindberg Fix Version/s: 3.5.0 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-1975) Environment transaction_uuid is not passed to facts indirector during compilation
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-1975 Environment transaction_uuid is not passed to facts indirector during compilation Change By: Kenneth Barber TheclassPuppet::Indirector::Catalog::Compilercontainsamethod'extract_facts_from_request'whichextractsfactsfromtherequesttobestoredinacacheindirector. Weutilisethis This call aspartof isusedin the flowforthe PuppetDBterminustosavefacts.Theproblemhowever,isthattheenvironmentisnotpassedthroughtotheindirector,whichmeanswecannotpreservefactswiththeenvironmenttheywerecreatedfromsowecancompletePDB-453.Ihaveapatchthatremediesthis,anditisforthcoming.[~eric.sorenson],[~andy]...I'mnotsureifthisisstrictlyabugornon-feature,whatdoyouthink?IsimplyaskbecauseI'mnotsurewhatbranch/fixversiontotargetthisfor. 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 (PDB-453) Update terminus to include environment information
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-453 Update terminus to include environment information Change By: Kenneth Barber Terminusdatasubmissionshould :-Include include environmentinsubmitted catalogs-Includeenvironmentinsubmitted facts ,catalogsandreports. 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-1979) future parser class reference inside class doesn't work
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1979 future parser class reference inside class doesn't work Change By: Henrik Lindberg Fix Version/s: 3.5.0 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-1979) future parser Class reference with leading :: doesn't work
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1979 future parser Class reference with leading :: doesn't work Change By: Henrik Lindberg Summary: futureparser class Class reference insideclass withleading:: doesn'twork 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-1979) future parser Class reference with leading :: doesn't work
Title: Message Title
Henrik Lindberg commented on an issue
Re: future parser Class reference with leading :: doesn't work
reproducible with:
class foo::f1 {
notify { 'me first': }
}
class foo {
class { 'foo::f1': } -
Class['::foo']
notify { 'me last': }
}
include foo
Add Comment
Puppet / PUP-1979
future parser Class reference with leading :: doesn't work
If you have a class that does something like this: {noformat} class iptables { class { '::iptables::packages': } - class { '::iptables::configs': } - class { '::iptables::update': } - class { '::iptables::services': } - Class['::iptables'] } {noformat} This works with current parser and avoid the need to use an explicit ...
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-1979) future parser Class reference with leading :: doesn't work
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1979 future parser Class reference with leading :: doesn't work Change By: Henrik Lindberg Component/s: DSL Story Points: 1 Assignee: HenrikLindberg 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-1603) puppet apply failure if puppet is upgraded
Title: Message Title Dan Carley commented on an issue Re: puppet apply failure if puppet is upgraded This makes upgrading to = 3.4 a bit of a pain. I've also seen it fail to backup files, although I can't reproduce it reliably. We're using the following hack to workaround it during our upgrade: https://gist.github.com/dcarley/9630094 Add Comment Puppet / PUP-1603 puppet apply failure if puppet is upgraded I am testing an update from puppet 3.2.4 to 3.4.2 and I am receiving a failure that I have found in a few different places on the internet but that has no bug and no reproducer (for reference, I believe these are related links: https://groups.google.com/forum/#!topic/puppet-users/318TmfkO9Js and https://github.com/purpleidea/puppet-puppet/commit/8b7dae5ca... 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
Jira (PUP-1979) future parser Class reference with leading :: doesn't work
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1979 future parser Class reference with leading :: doesn't work Change By: Henrik Lindberg Sprint: Week2014-3-12to2014-3-19 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-1981) Can't use :: in contain
Title: Message Title
Daniele Sluijters created an issue
Puppet / PUP-1981
Can't use :: in contain
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Henrik Lindberg
Created:
18/Mar/14 2:56 PM
Priority:
Major
Reporter:
Daniele Sluijters
Works:
class test {
class { '::test::a': }
contain test::a
}
class test::a {
notice('a')
}
include ::test
Fails:
class test {
class { '::test::a': }
contain ::test::a
}
class test::a {
notice('a')
}
include ::test
Add Comment
Jira (PUP-1981) Can't use :: in contain
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-1981
Can't use :: in contain
Change By:
Daniele Sluijters
Works:{noformat}classtest{class{'::test::a':}containtest::a}classtest::a{notice('a')}include::test{noformat}Fails:{noformat}classtest{class{'::test::a':}contain::test::a}classtest::a{notice('a')}include::test{noformat}
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-1981) Can't use :: in contain
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-1981
Can't use :: in contain
Change By:
Daniele Sluijters
Works:{noformat}classtest{class{'::test::a':}containtest::a}classtest::a{notice('a')}include::test } {noformat}Fails:{noformat}classtest{class{'::test::a':}contain::test::a}classtest::a{notice('a')}include::test } {noformat}
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-1981) Can't use :: in contain
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-1981
Can't use :: in contain
Change By:
Daniele Sluijters
Works:{noformat}classtest{class{'::test::a':}containtest::a } classtest::a{notice('a')}include::test}{noformat}Fails:{noformat}classtest{class{'::test::a':}contain::test::a } classtest::a{notice('a')}include::test}{noformat}
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-1981) Can't use :: in contain
Title: Message Title
Daniele Sluijters updated an issue
Puppet / PUP-1981
Can't use :: in contain
Change By:
Daniele Sluijters
Works:{noformat}classtest{class{'::test::a':}containtest::aclasstest::a{notice('a')} } include::test } {noformat}Fails:{noformat}classtest{class{'::test::a':}contain::test::aclasstest::a{notice('a')} } include::test } {noformat}
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-1981) Can't use :: in contain
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1981 Can't use :: in contain Change By: Henrik Lindberg Component/s: DSL 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-1981) Can't use :: in contain
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1981 Can't use :: in contain Change By: Henrik Lindberg Assignee: HenrikLindberg 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-1981) Can't use :: in contain
Title: Message Title
Henrik Lindberg commented on an issue
Re: Can't use :: in contain
This is probably related to PUP-1279 (same problem as in PUP-1279 even if that is for the future parser). The lookup basically does not handle class references starting with ::. The contain function should either just strip them (and document that references are absolute), or resolve them against the context it is in.
Add Comment
Puppet / PUP-1981
Can't use :: in contain
Works: {noformat} class test { class { '::test::a': } contain test::a class test::a { notice('a') } } include ::test {noformat} Fails: {noformat} class test { class { '::test::a': } contain ::test::aclass test::a { notice('a') } } include ::test {noformat}
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,
Jira (PUP-1981) Can't use :: in contain
Title: Message Title
Daniele Sluijters commented on an issue
Re: Can't use :: in contain
I would prefer a solution that strips them. include and class are fine with ::, as is calling a defined type with :: and I'm betting it's also working for native types. It would get confusing if contain doesn't.
Add Comment
Puppet / PUP-1981
Can't use :: in contain
Works: {noformat} class test { class { '::test::a': } contain test::a class test::a { notice('a') } } include ::test {noformat} Fails: {noformat} class test { class { '::test::a': } contain ::test::aclass test::a { notice('a') } } include ::test {noformat}
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-748) PR (2067): Zypper provider install options - darix
Title: Message Title Peter Huene updated an issue Puppet / PUP-748 PR (2067): Zypper provider install options - darix Change By: Peter Huene Issue Type: Task Bug 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-1751) PR (2383): Suse chkconfig --check boot.service always returns 1 whether the service is enabled/disabled. - m4ce
Title: Message Title Peter Huene updated an issue Puppet / PUP-1751 PR (2383): Suse chkconfig --check boot.service always returns 1 whether the service is enabled/disabled. - m4ce Change By: Peter Huene Issue Type: Task Bug 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-1979) future parser Class reference with leading :: doesn't work
Title: Message Title
Henrik Lindberg commented on an issue
Re: future parser Class reference with leading :: doesn't work
merged to stable: dc41d16c95c009bfb05f5f5a5cf2ebe12cc0e966 merged to master: e427904ae286efce18118480f6f75636418c6fc5
Add Comment
Puppet / PUP-1979
future parser Class reference with leading :: doesn't work
If you have a class that does something like this: {noformat} class iptables { class { '::iptables::packages': } - class { '::iptables::configs': } - class { '::iptables::update': } - class { '::iptables::services': } - Class['::iptables'] } {noformat} This works with current parser and avoid the need to use an explicit ...
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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Fix Version/s: 3.5.1 Fix Version/s: 3.6.0 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-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format Change By: Michelle Johansen Story Points: 1 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1977 `puppet module build` should create `metadata.json` instead of `Modulefile` Change By: Michelle Johansen Fix Version/s: 3.5.1 Fix Version/s: 3.6.0 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-1210) authentication_authority key is not set when managing root's password using the puppet user provider
Title: Message Title
Andy Parker commented on an issue
Re: authentication_authority key is not set when managing root's password using the puppet user provider
I haven't been able to reproduce the problem where either the root user or any other user, can log in via the GUI, but not any command line. What I have been able to reproduce, I think, is the issue that is provided in the pe-users thread linked to by Eric Sorenson. What seems to be happening there is that on 10.8 and 10.9 all three of password, salt, and iterations need to be provided in order to end up with a working password. I've confirmed this with the following working manifest, which creates a user with the password of puppet:
Valid user
user { 'otheruser':
ensure = 'present',
comment= 'Puppet Test User',
gid= '20',
groups = ['com.apple.sharepoint.group.1'],
home = '/Users/otheruser',
iterations = '25641',
password = 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
salt = 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
shell = '/bin/bash',
uid= '503',
}
Variations on this all end up creating user accounts that can't be logged into.
Invalid user (iterations given, salt missing)
user { 'iterationsuser':
ensure = 'present',
comment= 'Iterations Test User',
gid= '20',
groups = ['com.apple.sharepoint.group.1'],
home = '/Users/iterationsuser',
iterations = '25641',
password = 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
#salt = 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
shell = '/bin/bash',
uid= '506',
}
Invalid user (salt given, iterations missing)
user { 'saltuser':
ensure = 'present',
comment= 'Salt Test User',
gid= '20',
groups = ['com.apple.sharepoint.group.1'],
home = '/Users/saltuser',
password = 'b876573f7c16c2e6ff541b7b41e4749daff39da335c76f0348ad8820aab8aa0ce1eb2e8b11c8b0fd801025e601832c3040a25ea1dc0cc532496919d8c601da71c4780d056a7c1fe0cc073ee70b1c9bead9282feaaa3dcdb8bd981150535f918b096adcdf258ef0f7b56379568e2ca53c98ce9cdd80dc8e8babb4a94132a6cdd7',
salt = 'ae4752864f88f934365109b5ac4e65cf1d0ac8a13b778e5e1a2354e54c320b31',
shell = '/bin/bash',
uid= '507',
}
