Jira (PUP-4456) postrun_command causes puppet to ignore timeout
Title: Message Title Jay Wallace created an issue Puppet / PUP-4456 postrun_command causes puppet to ignore timeout Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Created: 2015/04/22 1:58 PM Labels: customer Priority: Critical Reporter: Jay Wallace Just tested puppet with postrun_command = sleep inf and the process is never released. No runs can occur, because it never times out. It seems puppet is waiting on a `0` or `non-zero` exit code before the run is complete. This is problematic in scenario where a command hangs indefinitely.
Jira (HI-371) Command line argument to print all hiera key/values for a given search
Title: Message Title Jay Wallace created an issue Hiera / HI-371 Command line argument to print all hiera key/values for a given search Issue Type: New Feature Affects Versions: HI 1.3.4 Assignee: Unassigned Created: 2015/04/20 2:04 PM Labels: customer Priority: Normal Reporter: Jay Wallace Command line argument to print all hiera key/values for a given node: Example: hiera EVERYTHING -c /etc/puppetlabs/puppet/hiera.yaml ::environment=production ::app_role=mywebserver ::app_tier=dev Ideally a user would want to know all of the key values based on the filters
Jira (PUP-3883) Support for user resource with a DOMAIN\User title
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-3883
Support for user resource with a DOMAIN\User title
Issue Type:
New Feature
Affects Versions:
PUP 3.7.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2015/01/21 1:00 PM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
User resource with a DOMAIN\User title should be supported behavior with Puppet. Puppet is not inherently aware of domain style names when defining a user in such a manner. For this to even theoretically work, the account that Puppet is running on would have to have domain administration credentials for this to ever work properly.
user { domain\\bud:
Jira (FACT-757) Facts that use shell scripts to return values via Puppet spawns new processes indefinitely
Title: Message Title Jay Wallace created an issue Facter / FACT-757 Facts that use shell scripts to return values via Puppet spawns new processes indefinitely Issue Type: Bug Affects Versions: FACT 1.7.5 Assignee: Eric Sorenson Created: 2014/11/13 1:55 PM Labels: customer Priority: Normal Reporter: Jay Wallace Facts that use shell scripts to return values via Puppet spawns new processes indefinitely. This was discovered when creating the following fact (/etc/puppetlabs/facter/facts.d/env.sh): #!/bin/bash echo env=`/opt/puppet/bin/puppet agent --configprint environment`
Jira (HI-294) Traverse hiera with a fact that returns an array
Title: Message Title Jay Wallace created an issue Hiera / HI-294 Traverse hiera with a fact that returns an array Issue Type: New Feature Affects Versions: HI 1.3.4 Assignee: Unassigned Created: 02/Oct/14 11:16 AM Labels: customer Priority: Normal Reporter: Jay Wallace Users would like hiera to be able to traverse a fact that returns an array. If one were to have an array (eg fact = [test1,test2,test3]) hiera would itterate over each element of the array when reading the hierarchy. Example: --- :backends:
Jira (PUP-3353) file resource stats all files in subdirectories when using recursion even if recursion is set to false in subdirectory
Title: Message Title Jay Wallace created an issue Puppet / PUP-3353 file resource stats all files in subdirectories when using recursion even if recursion is set to false in subdirectory Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 26/Sep/14 2:00 PM Environment: Centos 6.5 x86_64 Labels: customer Priority: Major Reporter: Jay Wallace It seems when using recursion, the file provider stats the contents of all subdirectories, even where the subdirectory has recursion explicitly set to false. This causes runs to take much longer than necessary in scenarios where a subdirectory has a large number of files. Example:
Jira (PUP-3326) Sun package provider versionable
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-3326
Sun package provider versionable
Issue Type:
New Feature
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
22/Sep/14 7:42 AM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
If one runs
puppet resource package packagename
a resource similar to a versionable one is returned, though the sun package provider is currently not versionable.
Example:
# /opt/puppet/bin/puppet resource package SUNWxvnc
package { 'SUNWxvnc':
ensure = '6.6.2.0500,REV=0.2008.02.15',
}
Jira (PUP-3263) Architecture Parameter for Package Resource
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-3263
Architecture Parameter for Package Resource
Issue Type:
New Feature
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
16/Sep/14 3:01 PM
Labels:
customer
Priority:
Major
Reporter:
Jay Wallace
Users would like to be able to specify the specific architecture for a given package using the yum provider. Unfortunately, this does not function properly. See below:
package{libxml2-devel.i686: ensure = 2.7.6-14.el6_5.2}
This works, but installs the 32-bit version of the package:
# This works, and installs the 32-bit libxml2 development files
package{libxml2-devel.i686: ensure = installed}
Jira (PUP-3184) Exec resource executed even though warning reports it being skipped
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-3184
Exec resource executed even though warning reports it being skipped
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
04/Sep/14 2:17 PM
Environment:
Centos 6.5 (PE 3.3.1)
Labels:
customer
Priority:
Critical
Reporter:
Jay Wallace
It looks like refresh is triggered and the exec resource is being executed even though it reports the resource being skipped. This appears to be exclusive when notifying a resource with a require.
Example:
file { '/tmp/foo': content = test, notify = Exec['/bin/touch /tmp/bar'] }
exec {
Jira (PUP-3184) Exec resource executed even though warning reports it being skipped
Title: Message Title
Jay Wallace updated an issue
Puppet / PUP-3184
Exec resource executed even though warning reports it being skipped
Change By:
Jay Wallace
Itlookslikerefreshistriggeredandtheexecresourceisbeingexecutedeventhoughitreportstheresourcebeingskipped.Thisappearstobeexclusivewhennotifyingaresourcewitharequire.Example:{code}file{'/tmp/foo':content=test,notify=Exec['/bin/touch/tmp/bar']}exec{'config':command='/bin/false'}exec{'/bin/touch/tmp/bar':refreshonly=true,require=Exec['config']}{code}Inthistestboth`/tmp/bar`and`/tmp/foo`getcreated.Thisisnotexpectedbehavior.Onewouldexpectthefileresourcetonotifythe`/bin/touch/tmp/bar`,skipthisresourceduetodependencies,andfailwhen`/bin/false`returnsanon-zeroexitcode. Error:{code}Notice:Compiledcatalogforpe-331-master.puppetdebug.vlaninenvironmentproductionin0.16secondsError:/bin/falsereturned1insteadofoneof[0]Error:/Stage[main]/Main/Exec[config]/returns:changefromnotrunto0failed:/bin/falsereturned1insteadofoneof[0]Notice:/Stage[main]/Main/Exec[/bin/touch/tmp/bar]:DependencyExec[config]hasfailures:trueWarning:/Stage[main]/Main/Exec[/bin/touch/tmp/bar]:Skippingbecauseoffaileddependencies{code} Ihavebeenabletoworkaroundthisusing:{code}file{'/tmp/foo':content=test,notify=Exec['/bin/touch/tmp/bar'],require=Exec['config']}exec{'config':command='/bin/false'}exec{'/bin/touch/tmp/bar':refreshonly=true,}{code}
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
Jira (HI-284) Specifying stages within hiera
Title: Message Title Jay Wallace created an issue Hiera / HI-284 Specifying stages within hiera Issue Type: New Feature Affects Versions: 1.3.4 Assignee: Aaron Armstrong Components: PE Created: 12/Aug/14 2:19 PM Labels: customer Priority: Normal Reporter: Jay Wallace Users should be able to specify stages in hiera when using hiera_include. Currently, You cannot assign a class to a run stage when declaring it with the include function and are forced to use the resource-like class declaration syntax with stages. It is not uncommon for a user to want to include several classes via and specify the stage.
Jira (PUP-2991) User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
Title: Message Title Jay Wallace created an issue Puppet / PUP-2991 User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10 Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 30/Jul/14 8:32 AM Environment: Solaris 10 Labels: customer solaris Priority: Major Reporter: Jay Wallace Summary https://github.com/puppetlabs/puppet/commit/73b0c2b0f59db920a14d4d0951b1f1c40d603cb4. Seems to have broken the shell parameter for the user type in Solaris. One is now unable to specify a user's shell after the user has been created. This currently affects all users utilizing Puppet 3.6.2. Test Code:
Jira (PUP-2991) User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
Title: Message Title
Jay Wallace commented on an issue
Re: User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
In Solaris 11, it appears the shell parameter is being failed to be set even when the user is initially created. It simply sets the shell to /usr/bin/bash upon user creation and no changes are made on subsequent runs.
Add Comment
Puppet / PUP-2991
User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
h4.Summary https://github.com/puppetlabs/puppet/commit/73b0c2b0f59db920a14d4d0951b1f1c40d603cb4. Seems to have broken the shell parameter for the user type in Solaris. One is now unable to specify a user's shell after the user has been created. This currently affects all users utilizing Puppet 3.6.2. h4.Test Code: {code} user { 'jay': ensure ...
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-628) facter returns incorrect value for `facter virtual` for Ldoms due to how the fact is added in Solaris.
Title: Message Title Jay Wallace created an issue Facter / FACT-628 facter returns incorrect value for `facter virtual` for Ldoms due to how the fact is added in Solaris. Issue Type: Bug Affects Versions: 1.7.5 Assignee: Eric Sorenson Components: PE Created: 23/Jul/14 2:14 PM Labels: customer Priority: Normal Reporter: Jay Wallace Whenever you execute facter with no arguments it loads both ldom.rb and virtual.rb, and virtual fact value is set properly. However, in the scenario where you execute facter virtual it loads only virtual.rb and given this fact is not explicitly set for Ldoms it defaults to setting the value as physical. Below is an excerpt from ldom.rb where the virtual fact is added for Solaris: Facter.add(virtual) do confine :ldom_domainrole_control = 'false' has_weight 10 setcode do Facter.value(:ldom_domainrole_impl) end end
Jira (PUP-2911) Resources metatype needs to include way to effectively purge non-managed services
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-2911
Resources metatype needs to include way to effectively purge non-managed services
Issue Type:
New Feature
Affects Versions:
3.4.3
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
08/Jul/14 1:49 PM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
Some users have reported they would like to have a way to purge all un-managed service resources. Something like:
resources { 'service': purge = true }
I am not entirely sure purge is the best attribute for encapsulating this functionality, as nothing is actually being purged in this case, but agree that a similar attribute needs to exist exclusively for services for the resources metatype.
Essentially the attribute would ensure all unmanaged services had both:
Jira (PUP-2823) Allow class names with underscores preceeded by an uppercase character
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-2823
Allow class names with underscores preceeded by an uppercase character
Issue Type:
New Feature
Affects Versions:
3.4.3
Assignee:
Aaron Armstrong
Components:
PE
Created:
23/Jun/14 2:37 PM
Environment:
Centos 6.4 64-bit PE 3.2.3
Priority:
Normal
Reporter:
Jay Wallace
Seems Puppet is unable to locate classes that have underscores followed by and upper case character. This is better shown, then described. See below:
class test_Jay {
notify { This is a test: }
}
with
include test_Jay
for a node, results in:
Jira (PUP-2778) Issues with Cron resource type creating duplicate crons
Title: Message Title Jay Wallace created an issue Puppet / PUP-2778 Issues with Cron resource type creating duplicate crons Issue Type: Bug Affects Versions: 3.4.3 Assignee: Kylo Ginsberg Components: Types and Providers Created: 13/Jun/14 4:16 PM Environment: Tested in AIX and Centos 6.3 Labels: cron customer Priority: Normal Reporter: Jay Wallace It seems there is an issue where the cron resource type creates duplicate crons. If you begin managing a cron that already exists in crontab, Puppet does nothing. This is likely the source of the issue, as Puppet is initially indexing via the command. If you change the command, Puppet creates a new cron with the new command and the title provided. After the title is created, Puppet begins indexing on this title.
Jira (FACT-549) serialnumber fact for AIX
Title: Message Title Jay Wallace created an issue Facter / FACT-549 serialnumber fact for AIX Issue Type: New Feature Affects Versions: 1.7.5 Assignee: Eric Sorenson Components: PE Created: 12/Jun/14 10:46 AM Environment: AIX 7.1 Labels: customer Priority: Normal Reporter: Jay Wallace Currently facter does not return the serialnumber fact for AIX boxes by default. This can be obtained via: uname -u
Jira (PUP-2773) Schedule type needs more granularity
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-2773
Schedule type needs more granularity
Issue Type:
New Feature
Affects Versions:
3.4.3
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
12/Jun/14 10:58 AM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
The schedule type currently is not specific enough. For example a user is only able to schedule a resource to be applied the first Tuesday of the month.
schedule { 'maint':
range = 2 - 4,
weekday = 'Tuesday',
period = 'Monthly',
repeat = 1,
}
If a user wants to schedule the resource to be applied on the second Tuesday of the month, the type falls short in this regard.
You are only able to specify the weekday and how many times it runs within it's period. Unfortunately this falls short of some users expectations.
Jira (PDB-129) Make puppet node clean --unexport work with PuppetDB
Title: Message Title Jay Wallace commented on an issue Re: Make puppet node clean --unexport work with PuppetDB Referencing Nick Lewis: Possible workaround: I’m not fond of any solution that involves modifying the data in PuppetDB. I think similar functionality could be achieved through a function whose purpose is to collect deactivated exported resources and set ensure = absent, so that’s the solution I would lean toward. The one change that requires to PuppetDB would be to add back the ability to query for resources of deactivated nodes. Alternately, you could leave the nodes active and use the standard collection syntax with an ensure = absent resource override, if you have a way to identify the set of resources you want to do that for. Obviously that option depends on the particular case, since you may or may not have a single identifying characteristic for your deactivated nodes. Add Comment PuppetDB / PDB-129 Make puppet node clean --unexport work with PuppetDB The current node face has an --unexport option that tells clean to flag resources previously exported for a node to flip to ensure = absent (I think). We should see if the existing implementation already works with PuppetDB (does it simply store a revised catalog or something), or if we need to implement our own support for this. A good use case wo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
