Issue #2312 has been reported by Ricky Zhou.

Bug #2312: The operatingsystemrelease fact does not account for non-integer Fedora and RHEL releases.

• Author: Ricky Zhou
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Complexity: Unknown
• Keywords:

/etc/fedora-release and /etc/redhat-release can contain non-integral releases.
For example, during the Fedora Preview Release, /etc/fedora-release contained
"Fedora release 10.93 (Leonidas)." Also, /etc/redhat-release on a RHEL 5.3
machine contains "Red Hat Enterprise Linux Server release 5.3 (Tikanga)."

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2312 has been updated by Ricky Zhou.

I'm working on getting my patch for this properly submitted.

Bug #2312: The operatingsystemrelease fact does not account for non-integer Fedora and RHEL releases.

• Author: Ricky Zhou
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Complexity: Unknown
• Keywords:

/etc/fedora-release and /etc/redhat-release can contain non-integral releases.
For example, during the Fedora Preview Release, /etc/fedora-release contained
"Fedora release 10.93 (Leonidas)." Also, /etc/redhat-release on a RHEL 5.3
machine contains "Red Hat Enterprise Linux Server release 5.3 (Tikanga)."

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2312 has been updated by Ricky Zhou.

I have a ticket/master/2312 branch at http://fedorapeople.org/gitweb?p=ricky/public_git/facter.git;a=shortlog;h=refs/heads/ticket/master/2312, you can clone that repo at git://fedorapeople.org/~ricky/facter.git.

I made an attempt at writing a test for it, but I don't know ruby, so it could probably use some cleanup from somebody more experienced. I made a few attempts to have the stub match only the /etc/redhat-release File object and yield a StringIO object instead, but I couldn't figure out how to make it handle multiple attempts to open that file.

Also, somebody might want to see if this change applies to CentOS and OEL as well. I spoke to Todd Zullinger about this, we'd both like to see facts for Fedora and all of the downstream distros consolidated so that they give consistent information.

Bug #2312: The operatingsystemrelease fact does not account for non-integer Fedora and RHEL releases.

• Author: Ricky Zhou
• Status: Unreviewed
• Priority: Normal
• Assigned to:
• Category:
• Target version:
• Complexity: Unknown
• Keywords:

/etc/fedora-release and /etc/redhat-release can contain non-integral releases.
For example, during the Fedora Preview Release, /etc/fedora-release contained
"Fedora release 10.93 (Leonidas)." Also, /etc/redhat-release on a RHEL 5.3
machine contains "Red Hat Enterprise Linux Server release 5.3 (Tikanga)."

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2309 has been updated by Luke Kanies.

• Subject changed from templates are processed too early in the compliation to Defined resources are not evaluated immediately which can cause ordering problems
• Category set to language
• Status changed from Re-opened to Accepted
• Target version set to 0.26.0

Bug #2309: Defined resources are not evaluated immediately which can cause ordering problems

• Author: Ohad Levy
• Status: Accepted
• Priority: Normal
• Assigned to:
• Category: language
• Target version: 0.26.0
• Complexity: Unknown
• Affected version: 0.24.8
• Keywords:

Because defined resources are queued as they're defined, and only evaluated when all other work is done, we can see ordering issues. In the example below, the two classes are evaluated to the level of the defined resource, and then stopped. This results in the variable modification in the defined resource not getting called until after the template is evaluated.

The correct behaviour should see the defined resource getting evaluated as soon as it is added to the catalog, rather than queueing it for later.

original description:

it seems that templates ignore variable scopes, consider this code:

node default { include a include b } class a { $dirs = "" dir{["/tmp","/tmp/a","/tmp/b"]: before => File["/tmp/dirs"]} } class b { file{"/tmp/dirs": content => $a::dirs} #file{"/tmp/dirs": content => template("/tmp/dirs.erb")} } define dir() { $a::dirs += " $name" file {$name: ensure => directory } }
using template the output of the file is "", but when dumping the variable directly, the content is correct.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2141 has been updated by Bryan Kearney.

<at> lutter: There was a conflict in the parsing logic with comparators (== and !=)> I needed a glob after them, the the current parsing logic would not support that.

let me take a look at lutters patches this morning.

Bug #2141: Augeas resource bug with single and double quotes

• Author: Avi Miller
• Status: Re-opened
• Priority: Urgent
• Assigned to: Bryan Kearney
• Category:
• Target version: 0.25.0
• Complexity: Unknown
• Affected version: 0.24.8
• Keywords:

In Puppet 0.24.7, the following Augeas resource worked fine:

augeas { "pam_remove_console": context => "/files/etc/pam.d/", changes => "rm */*[module='pam_console.so']", onlyif => "match */*[module='pam_console.so'] size > 0", }

I've upgraded to Puppet 0.24.8 and I'm now getting the following error:

(//Node[basenode]/pam/Augeas[pam_remove_console]) Failed to retrieve current state of resource: Error sending command 'rm */*[module=' with params ["pam_console.so", "]"]/Command 'rm */*[module=' is not supported

Looks like Puppet is breaking on the ' even though I opened with " -- and escaping the ' doesn't help.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2141 has been updated by Bryan Kearney.

Just checking.. why was it moved to re-opened? The example works with the submitted code, which is destined for 0.25. Is the goal to provide a patch for 24.8? Let me know.

Lutters code has some clean up stuff in it, but I would rather treat that is seperate items for a future release as opposed to tieing them to this bug.

-- bk

Bug #2141: Augeas resource bug with single and double quotes

• Author: Avi Miller
• Status: Re-opened
• Priority: Urgent
• Assigned to: Bryan Kearney
• Category:
• Target version: 0.25.0
• Complexity: Unknown
• Affected version: 0.24.8
• Keywords:

In Puppet 0.24.7, the following Augeas resource worked fine:

augeas { "pam_remove_console": context => "/files/etc/pam.d/", changes => "rm */*[module='pam_console.so']", onlyif => "match */*[module='pam_console.so'] size > 0", }

I've upgraded to Puppet 0.24.8 and I'm now getting the following error:

(//Node[basenode]/pam/Augeas[pam_remove_console]) Failed to retrieve current state of resource: Error sending command 'rm */*[module=' with params ["pam_console.so", "]"]/Command 'rm */*[module=' is not supported

Looks like Puppet is breaking on the ' even though I opened with " -- and escaping the ' doesn't help.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2141 has been updated by lutter -.

The bug was only reopened to track that the patch for this is in 0.24.x, but not master - I then kinda got carried away with some code cleanup

Bug #2141: Augeas resource bug with single and double quotes

• Author: Avi Miller
• Status: Re-opened
• Priority: Urgent
• Assigned to: Bryan Kearney
• Category:
• Target version: 0.25.0
• Complexity: Unknown
• Affected version: 0.24.8
• Keywords:

In Puppet 0.24.7, the following Augeas resource worked fine:

augeas { "pam_remove_console": context => "/files/etc/pam.d/", changes => "rm */*[module='pam_console.so']", onlyif => "match */*[module='pam_console.so'] size > 0", }

I've upgraded to Puppet 0.24.8 and I'm now getting the following error:

(//Node[basenode]/pam/Augeas[pam_remove_console]) Failed to retrieve current state of resource: Error sending command 'rm */*[module=' with params ["pam_console.so", "]"]/Command 'rm */*[module=' is not supported

Looks like Puppet is breaking on the ' even though I opened with " -- and escaping the ' doesn't help.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2141 has been updated by lutter -.

I modified my patch series to address two additional issue:

• Special characters in paths can be escaped by preceding them with a backslash (commit e6794016)
• Change the syntax for match comparison back to use '=='/'!=' instead of 'eq'/'noteq' (commit cd36949b)

Put the result in the branch dev/2141-2

Bug #2141: Augeas resource bug with single and double quotes

• Author: Avi Miller
• Status: Re-opened
• Priority: Urgent
• Assigned to: Bryan Kearney
• Category:
• Target version: 0.25.0
• Complexity: Unknown
• Affected version: 0.24.8
• Keywords:

In Puppet 0.24.7, the following Augeas resource worked fine:

augeas { "pam_remove_console": context => "/files/etc/pam.d/", changes => "rm */*[module='pam_console.so']", onlyif => "match */*[module='pam_console.so'] size > 0", }

I've upgraded to Puppet 0.24.8 and I'm now getting the following error:

(//Node[basenode]/pam/Augeas[pam_remove_console]) Failed to retrieve current state of resource: Error sending command 'rm */*[module=' with params ["pam_console.so", "]"]/Command 'rm */*[module=' is not supported

Looks like Puppet is breaking on the ' even though I opened with " -- and escaping the ' doesn't help.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2313 has been reported by Joe McDonagh.

Feature #2313: Somewhat essential hardware facts not available on OpenBSD, patch included

• Author: Joe McDonagh
• Status: Unreviewed
• Priority: Low
• Assigned to:
• Category:
• Target version:
• Complexity: Easy
• Keywords: openbsd facter

I noticed some facts that I think should be on all platforms were missing from OBSD, such as swap information, memory information, processor, and processorcount. These are all pretty trivial to get on OBSD; patch is attached. I tested this on OBSD 4.5 with both the bsd and bsd.mp kernels.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Issue #2314 has been reported by Joe McDonagh.

Bug #2314: OpenBSD uses dmidecode for manufacturer info, should use native sysctl facility

• Author: Joe McDonagh
• Status: Unreviewed
• Priority: Low
• Assigned to:
• Category:
• Target version:
• Complexity: Unknown
• Keywords: openbsd facter

Hi, OpenBSD uses dmidecode to get facts about mfg. This is somewhat erroneous since the OBSD sysctl facility can get this information, and it is native to the OS while dmidecode is a bolt-on. If you'd like I can put together a patch.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To post to this group, send email to puppet-bugs <at> googlegroups.com
To unsubscribe from this group, send email to puppet-bugs+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---