Jira (PUP-3489) $confdir/environments/production is cached on startup even if not in configured environmentpath
Title: Message Title Dan Lidral-Porter created an issue Puppet / PUP-3489 $confdir/environments/production is cached on startup even if not in configured environmentpath Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Unassigned Created: 17/Oct/14 6:11 PM Priority: Minor Reporter: Dan Lidral-Porter I have a directory environment named `production` in the default environmentpath of `/etc/puppetlabs/puppet/environments`. This directory environment does not contain any modules, and its manifest contains only the filebucket & File configuration required by PE, and an empty default node block. In the `puppet.conf`, I have configured the `environmentpath` to point to a temporary directory that contains two environments named `production` and `testing`. Both of these environments define an `echo_environment` class that simply echos the current environment. I have my ENC configured to place all nodes into a group with an agent-specified environment and assigns them this `echo_environment` class. When I start the master and then run `puppet agent -t`, the agent run fails with an error that states the `echo_environment` class could not be found. If I specify the environment to be `testing` on the command line, then the run succeeds and the notify from the `echo_environment` class is visible. If I wait a few minutes for the production environment to be evicted from the environment cache, and then run `puppet agent -t` again, this time the class is found and the run succeeds. It seems that the production environment in the default `environmentpath` is loaded when the master starts up, before the configured `environmentp
Jira (PUP-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2647 Windows user provider reports that the password is created instead of changed Change By: Eric Thompson QA Contact: Narmadha Perumal Eric Thompson QA Status: Reviewed 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-3357) Unexpected error with multiple SSH keys without comments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3357 Unexpected error with multiple SSH keys without comments Change By: Eric Thompson QA Status: Reviewed 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-3081) reported catalog run time is wildly inaccurate
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3081 reported catalog run time is wildly inaccurate Change By: Eric Thompson QA Contact: Erik Dasher Eric Thompson QA Status: Reviewed 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-3338) Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3338 Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12 Change By: Eric Thompson QA Status: Reviewed 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-3401) Type system does not handle Pattern correctly
Title: Message Title
Henrik Lindberg commented on an issue
Re: Type system does not handle Pattern correctly
Language spec has been updated with a clarification that a Pattern without parameters means any string (and thus any Pattern)
Add Comment
Puppet / PUP-3401
Type system does not handle Pattern correctly
The Pattern type has similar problems to the Enum type + it is not implemented correctly. {code} Pattern < Pattern[/.*/] # false Pattern > Pattern[/.*/] # false Pattern == Pattern[/.*/] # false {code} That is not correct and neither complies with the spec, nor the the "law of least surprise"
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-3081) reported catalog run time is wildly inaccurate
Title: Message Title William Hopper commented on an issue Re: reported catalog run time is wildly inaccurate Functional review: verified at SHA 931a1b5b (CentOS 7): On an agent run with a simple test manifest being applied: [root@b23ranzrafqh1q5 ~]# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for b23ranzrafqh1q5.delivery.puppetlabs.net Info: Applying configuration version '1413588044' Notice: /Stage[main]/Main/Node[default]/Exec[hello]/returns: executed successfully Notice: Applied catalog in 0.03 seconds As expected, we now see "Applied catalog" instead of "Finished catalog run." Add Comment
Jira (PUP-3201) Validation thinks that an Undef instance is of type Runtime
Title: Message Title
Henrik Lindberg commented on an issue
Re: Validation thinks that an Undef instance is of type Runtime
merged to stable at d1a7fbe
Add Comment
Puppet / PUP-3201
Validation thinks that an Undef instance is of type Runtime
Create a define like this: {noformat} define hey(String $x) { notice $x } {noformat} Call it like this: {noformat} hey{'heyer': x => undef } {noformat} Get the somewhat unexpected error: {noformat} Expected parameter 'x' of 'Hey[heyer]' to have type String, got Runtime[ruby, Symbol] {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-3081) reported catalog run time is wildly inaccurate
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3081 reported catalog run time is wildly inaccurate Change By: William Hopper Assignee: William Hopper 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-779) Remove deprecated process execution methods in util
Title: Message Title William Hopper commented on an issue Re: Remove deprecated process execution methods in util Functional review: the code has indeed been removed from the codebase! Add Comment Puppet / PUP-779 Remove deprecated process execution methods in util All the deprecated process execution methods in util should be removed. 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-3488) Stop overwriting the agent's facts timestamp
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3488 Stop overwriting the agent's facts timestamp Change By: Josh Cooper Fix Version/s: PUP 4.0.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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. So, we're having some new failures due in part to classification changes. Talking with Nick Lewis, the console class has been added to the default group, and this accounts for the fact that the failed reports are getting a mode change, causing ticket_5477_master_not_dectect_sitepp.rb to faile because it is expecting no resource changes. The reports should not be managed to 644, but should stay 600, and Nick opened PE-6486 for this. Similarly, the environments directories are being managed more tightly and account for similar unexpected resource changes causing failures in some of the enviornment tests. Permissions/owner were changed to align, and we're now only seeing failures on redhat based platforms where the seluser is changing; selinux. woo. Notice: /File[/etc/puppetlabs/puppet/environments/production]/seluser: seluser changed 'unconfined_u' to 'system_u' The new enc_nonexistent_directory_environment.rb needs to be updated to use a classifier group to specify the non-existent environment. I'm working on that now. There are sporadic autosign_command and certificate_extensions failures from NC-281 There are a couple of scattered failures for report_submission pluginsync and woy_cache still. And scientific6 is just fubared with 34 failures; and I think this has happened twice in row. Need to dig in further here and see what is going on. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments
Jira (PUP-3488) Stop overwriting the agent's facts timestamp
Title: Message Title Josh Cooper created an issue Puppet / PUP-3488 Stop overwriting the agent's facts timestamp Issue Type: Bug Assignee: Unassigned Created: 17/Oct/14 3:08 PM Priority: Normal Reporter: Josh Cooper The master overwrites the timestamp on the agent's facts. This change was made in 2010 (https://github.com/puppetlabs/puppet/commit/fb5f859cf4), and does the wrong thing when there is more than one puppet master. We should stop doing this. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3485) Exec "command" Attribute Only Autorequires First Path in String
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Exec "command" Attribute Only Autorequires First Path in String
Personally, I don't think Exec autorequire should attempt to be this clever. What if there are arguments between the executable and the path? How do we determine that the command line has gotten sufficiently complex that autorequire processing should give up? As a user, I would prefer explicit requires over an autorequire subject to subtle bugs and complicated edge cases.
Add Comment
Puppet / PUP-3485
Exec "command" Attribute Only Autorequires First Path in String
h1. Description If a user uses an "command" attribute with multiple paths only the first will be evaluated for autorequire. Example below: {code}exec { 'Manifest Test': command => '/bin/bash /tmp/manifest/test.sh' } file { '/tmp/manifest/test.sh': ensure => file, content => "#!/bin/bash\necho \"Super Fun\" > /tmp/manifest/test.txt", m...
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 f
Jira (PDB-971) Stop calling Facts#strip_internal deprecated method
Title: Message Title Josh Cooper created an issue PuppetDB / PDB-971 Stop calling Facts#strip_internal deprecated method Issue Type: Task Assignee: Unassigned Created: 17/Oct/14 2:47 PM Priority: Normal Reporter: Josh Cooper In puppet 4, the _timestamp hidden fact is being removed (see PUP-3130), and the Puppet::Node::Facts#strip_internal method will be deprecated or removed. The puppetdb terminus should be modified to just call Facts#values instead of https://github.com/puppetlabs/puppetdb/blob/2.2.1/puppet/lib/puppet/indirector/facts/puppetdb.rb#L23 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3338) Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12
Title: Message Title
William Hopper commented on an issue
Re: Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12
Functional review: verified at SHA adc1adcc:
Using the manifest:
package { 'apache2':
ensure => present,
allow_virtual => false
}
service { 'apache2':
ensure => running,
require => Package['apache2']
}
In SLES 12:
Jira (PUP-3338) Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12
Title: Message Title William Hopper updated an issue Puppet / PUP-3338 Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12 Change By: William Hopper Assignee: William Hopper 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-3142) exec type should allow passing of arguments as an array rather than a string
Title: Message Title Sage Imel commented on an issue Re: exec type should allow passing of arguments as an array rather than a string Sure, having the arguments as a separate parameter is absolutely not necessary. The ability to safely build up a list of command arguments is the desired feature. Add Comment Puppet / PUP-3142 exec type should allow passing of arguments as an array rather than a string The exec type takes commands and arguments as a string, (@"echo foo"@) which will then get passed to /bin/sh (@sh -c "echo foo"@) by Kernel#system. This can make things pretty awkward if the command you're trying to execute contains shell metacharacters or quotes of its own, and under appropriately pathological conditions could even be a security probl... 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-b
Jira (PUP-2647) Windows user provider reports that the password is created instead of changed
Title: Message Title
Rob Reynolds commented on an issue
Re: Windows user provider reports that the password is created instead of changed
Kudos on hunter2. So awesome.
Add Comment
Puppet / PUP-2647
Windows user provider reports that the password is created instead of changed
If you change an existing user's password on Windows, puppet reports: {noformat} Notice: /Stage[main]/Main/User[testing6]/password: created password {noformat} If the desired password doesn't match current password, the windows_adsi provider's {{#password}} method returns :absent, to force the provider to apply the new password. But this causes pu...
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-3357) Unexpected error with multiple SSH keys without comments
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3357 Unexpected error with multiple SSH keys without comments Change By: Eric Thompson Assignee: Eric Thompson 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-3338) Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3338 Systemd should be the default service provider for OpenSuSE >= 12 and SLES 12 Change By: William Hopper Assignee: William Hopper 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-2613) Change source_permissions default to :ignore
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2613 Change source_permissions default to :ignore Change By: Michael Smith Assignee: Michael Smith 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-3334) Changes to environment.conf are not being picked up, even when environment timeout is set to 0.
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3334 Changes to environment.conf are not being picked up, even when environment timeout is set to 0. Change By: Eric Thompson Assignee: Eric Thompson 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-3255) improve puppet acceptance pre-suite for more platforms and git install
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3255 improve puppet acceptance pre-suite for more platforms and git install Change By: Eric Thompson Story Points: 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-3255) improve puppet acceptance pre-suite for more platforms and git install
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3255 improve puppet acceptance pre-suite for more platforms and git install Change By: Eric Thompson Sprint: Platform Server 2014-10-29 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-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title Eric Thompson moved an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: Eric Thompson Workflow: Engineering Platform Workflow Key: QA PUP - 1657 3486 Project: Quality Assurance Puppet 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-3485) Exec "command" Attribute Only Autorequires First Path in String
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3485 Exec "command" Attribute Only Autorequires First Path in String Change By: Ryan Gard Attachment: command_before_file_autorequire.pp 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-3485) Exec "command" Attribute Only Autorequires First Path in String
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3485 Exec "command" Attribute Only Autorequires First Path in String Change By: Ryan Gard Attachment: command_before_file_autorequire.pp 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-3485) Exec "command" Attribute Only Autorequires First Path in String
Title: Message Title
Ryan Gard created an issue
Puppet / PUP-3485
Exec "command" Attribute Only Autorequires First Path in String
Issue Type:
Improvement
Affects Versions:
PUP 3.7.1
Assignee:
Josh Cooper
Attachments:
command_before_file_autorequire.pp
Components:
Types and Providers
Created:
17/Oct/14 11:06 AM
Priority:
Normal
Reporter:
Ryan Gard
Description
If a user uses an "command" attribute with multiple paths only the first will be evaluated for autorequire. Example below:
exec { 'Manifest Test':
Jira (PUP-3484) Cron hour/minute format "0-6,13-23" is not allowed
Title: Message Title
Maksym Polshcha updated an issue
Puppet / PUP-3484
Cron hour/minute format "0-6,13-23" is not allowed
Change By:
Maksym Polshcha
I need to schedule a cron job for daily running every 30 mins from 0 to 6 and from 13 to 23. I tried this code:{quote}cron \ { "MyJob": ensure => present, command => "my-cron-command", user=> 'root', hour=> "0-6,13-23", minute => '*/30', environment => "MY_ENV" \ }{quote}This fails with{quote}0-6,13-23 is not a valid hour{quote}
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-3484) Cron hour/minute format "0-6,13-23" is not allowed
Title: Message Title
Maksym Polshcha created an issue
Puppet / PUP-3484
Cron hour/minute format "0-6,13-23" is not allowed
Issue Type:
Bug
Affects Versions:
PUP 3.5.1
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
17/Oct/14 11:02 AM
Priority:
Major
Reporter:
Maksym Polshcha
I need to schedule a cron job for daily running every 30 mins from 0 to 6 and from 13 to 23. I tried this code:
cron
Unknown macro: { "MyJob"}
This fails with
0-6,13-23 is not a valid hour
Jira (PUP-2965) Remove Puppet::Plugins
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-2965 Remove Puppet::Plugins Change By: Peter Huene Assignee: Peter Huene 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Nicholas Jackson created an issue Puppet / PUP-3483 Systemd provider doesn't scan for changed units Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 17/Oct/14 9:32 AM Labels: systemd Priority: Normal Reporter: Nicholas Jackson When a package updates it's sysvinit script or systemd unit (or for that matter if I were to be manually managing a systemd unit with a file resource), nothing ever tells systemd to check for changed units. Typically you would invoke `systemctl daemon-reload` to scan for new and changed units. Add Comment
Jira (PUP-3331) Custom Types should be able to call all levels of auto* relationships.
Title: Message Title Rob Reynolds commented on an issue Re: Custom Types should be able to call all levels of auto* relationships. Merged into master at fb7e4626d Add Comment Puppet / PUP-3331 Custom Types should be able to call all levels of auto* relationships. Right now, users can only use the 'autorequires' feature in ccustom types. The following should be supported: * Autorequires * Autonotifies * Autobefore * Autosubscribes 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-3471) Windows Puppet x86 Installer on x64 system issue
Title: Message Title Baptiste Hebert commented on an issue Re: Windows Puppet x86 Installer on x64 system issue Hi Rob Reynolds, Here are some answers: Powershell version: 2.0 Windows installer version: v5.0.7601.17514 Puppet 3.6.2 did installed correctly without the issue (PATH is clean + Puppet bin) %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Progra~2\WINDOWS RESOURCE KITS\TOOLS\ C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Progra~2\WINDOWS RESOURCE KITS\TOOLS\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\SGBUILD\SCRIPTS;C:\Program Files\SGBUILD\LOGS;C:\Progra~2\CA\CA_APPSW;C:\PROGRA~2\CA\SC\CCS\CAM\bin;C:\Progra~2\CA\SC\CCS\AT\SERVICES\BIN;C:\Progra~2\CA\SC\CCS\AT\AGENTS\BIN;C:\Progra~2\Puppet Labs\Puppet\bin Add Comment Puppet / PUP-3471 Windows Puppet x86 Installer on x64 system issue When installing Puppet Agent on a x64 Windows distribution, we noticed that the PATH environment variable is corrupted afterwards. In fact, it seems that Puppet removes all %SystemRoot% references in the PATH variable in both 64 and 32 bit environme
Jira (HI-297) hiera (debian) package does not register as gem
Title: Message Title
Andreas Ntaflos commented on an issue
Re: hiera (debian) package does not register as gem
I had the same problem on my Vagrant boxes I use for Puppet module development. On the box that runs a Puppet master I had to use the --ignore-dependencies install option so that Puppet could install the hiera-file Gem without a dependency error:
package { 'hiera-file':
ensure => $hiera_file_package_ensure,
name=> $hiera_file_package_name,
provider=> 'gem',
install_options => '--ignore-dependencies',
}
So why would Puppet, when running `gem install` use a wrong GEM_PATH and not find Hiera as a Gem anywhere?
Add Comment
Jira (HI-297) hiera (debian) package does not register as gem
Title: Message Title Daniele Sluijters commented on an issue Re: hiera (debian) package does not register as gem Actually, it does: daniele.sluijters@vm0002 /v/l/g/1.9.1> dpkg -l hiera Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii hiera 1.3.4-1puppetlabs1 all A simple pluggable Hierarchical Database. daniele.sluijters@vm0002 /v/l/g/1.9.1> irb irb(main):001:0> require 'hie
Jira (HI-297) hiera (debian) package does not register as gem
Title: Message Title Daniele Sluijters updated an issue Hiera / HI-297 hiera (debian) package does not register as gem Change By: Daniele Sluijters Summary: hiere hiera (debian) package does not register as gem 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.
