Jira (FACT-197) processorcount counting CPU cores on Solaris
Title: Message Title Stefan Schulte created an issue Facter / FACT-197 processorcount counting CPU cores on Solaris Issue Type: Bug Affects Versions: 1.7.4 Assignee: Eric Sorenson Created: 11/Jan/14 3:02 AM Environment: Solaris 5.10; Solaris 5.11 Priority: Normal Reporter: Stefan Schulte The processorcount fact on Solaris is counting CPU cores physicalprocessorcount = 1 processor0 = SPARC-T4 processor1 = SPARC-T4 processor2 = SPARC-T4 processor3 = SPARC-T4 processorcount = 1 and on linux it counts CPU threads. This was reported as http://projects.puppetlabs.com/issues/18215 and a working fix is currently in master. However it is not released yet as the old ticket claims, because the linked backport in the redmine ticket does not seem to have anything to do with the original issue (the backport only touches code for HP-UX)
Jira (FACT-149) Implement UUID fact
Title: Message Title Jason Antman assigned an issue to Jason Antman Facter / FACT-149 Implement UUID fact Change By: Jason Antman Assignee: EricSorenson JasonAntman 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/groups/opt_out.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title redmine.exporter created an issue Facter / FACT-198 Rename uniqueid hostid Issue Type: Bug Assignee: Eric Sorenson Created: 11/Jan/14 7:22 AM Labels: redmine Priority: Normal Reporter: redmine.exporter basing it on hostid is not nearly unique enough especially in a xen environment with duplicated machines and multiple instances of IPs and MACs. I'd suggest something like serial number from BIOS (works for dell, hp, ibm, etc - significant portion of all x86 machines) modified by the system time when facter was initially installed. Add Comment
Jira (FACT-149) Implement UUID fact
Title: Message Title Jason Antman commented on an issue Re: Implement UUID fact The UUID fact was added to facter in 3d45e2b2b4 (from what I can tell, the 1.7.0 release) inside manufacturer.rb - this pulls from dmidecode under linux, and apparently similar facilities under other OSes. For cases that need an actually (globally, hopefully) unique ID, UUID should be used. In terms of what to do with 'uniqueid', I'll defer to FACT-198 which suggests renaming it to hostid. Add Comment Facter / FACT-149 Implement UUID fact Debian-based systems in particular (possibly others) ship with an /etc/hosts file that starts 127.0.0.1 localhost 127.0.1.1 hostname.domain.tld hostname This is used to specify the FQDN of the machine independently of its physical IP address, and I believe their expectation is that you are not required to change this. However, this breaks the host... 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
Jira (PUP-1179) puppet agent service can't start when using GBK encoding in windows environment
Title: Message Title Yoann LE TOUCHE commented on an issue Re: puppet agent service can't start when using GBK encoding in windows environment Old comment from the redmine original ticket by Josh Cooper : https://projects.puppetlabs.com/issues/23185#note-5 win32-dir should be upgraded to 0.4.6 (0.4.3 in puppet-3.4.2) Add Comment Puppet / PUP-1179 puppet agent service can't start when using GBK encoding in windows environment First of all, I am Chinese. my laptop os is windows 7, and the 'Language for non-Unicode programs' is set to 'Chinese(Simplified,PRC)'. several days before, i started install puppet 3.2.4 to my laptop, the package downloaded from downloads.puppetlabs.com/windows. in the install progress, installer tells me puppet agent can't started. i found the comm... 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-198) Rename uniqueid hostid
Title: Message Title Jason Antman commented on an issue Re: Rename uniqueid hostid See specifically: http://projects.puppetlabs.com/issues/3926#note-4 and http://projects.puppetlabs.com/issues/3926#note-6 The consensus in the Redmine ticket seemed to be: 1) people expected uniqueid to be globally unique on all OSes, but that's confusing, because in reality that's only true on Solaris, and it uses hostid elsewhere. The UUID fact ( FACT-149 , released in 1.7.0) is what people should be using. 2) This needs to be handled in a major point release (per Adrien, http://projects.puppetlabs.com/issues/3926#note-9) ideally by copying uniqueid to hostid and adding a deprecation warning, and then removing it in a subsequent release. Does that sound right, and acceptable? Add Comment Facter / FACT-198 Rename uniqueid hostid basing it on hostid is not nearly unique enough especially in a xen environment with duplicated machines and multiple instances of IPs and MACs. I'd suggest something like serial number from BIOS (works for dell, hp, ibm, etc - significant portion of all x86 machines) modified by the system time when facter was initially installed. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Jason Antman assigned an issue to Jason Antman Facter / FACT-198 Rename uniqueid hostid Change By: Jason Antman Assignee: EricSorenson JasonAntman 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/groups/opt_out.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Jason Antman assigned an issue to Eric Sorenson Facter / FACT-198 Rename uniqueid hostid Change By: Jason Antman Assignee: JasonAntman EricSorenson 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/groups/opt_out.
[CLA Application - Bug #23341] (Closed) https://github.com/puppetlabs/puppet/pull/2025 never got acked by the CLA bot
Issue #23341 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. It looks like this pull request was closed, so I'm closing this ticket. Bug #23341: https://github.com/puppetlabs/puppet/pull/2025 never got acked by the CLA bot https://projects.puppetlabs.com/issues/23341#change-102597 * Author: Kylo Ginsberg * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: * Keywords: * Branch: This pull may have come in while the CLA bot was down? Anyway, the contributor says he signed the CLA agreement but there's no ack in the comments for that PR. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[CLA Application - Bug #23076] (Closed) CLA updates stopped between Oct 15 - Oct 21
Issue #23076 has been updated by Dawn Foster. Status changed from Accepted to Closed Cleaning up old bugs. Looks like this one was resolved. Bug #23076: CLA updates stopped between Oct 15 - Oct 21 https://projects.puppetlabs.com/issues/23076#change-102598 * Author: eric sorenson * Status: Closed * Priority: Normal * Assignee: Paul Jungwirth * Category: * Target version: * Keywords: * Branch: Hi Paul, a couple of weeks ago we stopped getting updates from puppetcla on the puppetlabs projects. I don't know how to troubleshoot this. Can you please help? At this point I'd like both fish and instructions on how to fish since we've had some staff turnover and don't have internal docs on how to dig into problems with the app. Thanks! -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[CLA Application - Bug #22880] (Closed) CLA Status Change should only comment on open pull requests
Issue #22880 has been updated by Dawn Foster. Status changed from Investigating to Closed Cleaning up old bugs. This one was successfully resolved. Bug #22880: CLA Status Change should only comment on open pull requests https://projects.puppetlabs.com/issues/22880#change-102599 * Author: Dawn Foster * Status: Closed * Priority: Normal * Assignee: Paul Jungwirth * Category: * Target version: * Keywords: * Branch: I just changed Nate's GitHub username to match the change he made on GitHub. It dropped new comments that he had signed the CLA on his open pull requests, but it also dropped a comment on all of the closed pull requests, too. Here's one of them: https://github.com/puppetlabs/puppetdb/pull/696 It would seem like it should only care about open pull requests. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[CLA Application - Bug #19903] (Closed) SPF soft-fail for emails from the application
Issue #19903 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Bug #19903: SPF soft-fail for emails from the application https://projects.puppetlabs.com/issues/19903#change-102601 * Author: Ken Barber * Status: Closed * Priority: Low * Assignee: Kelsey Hightower * Category: * Target version: * Keywords: * Branch: Looking at the headers of an email I received from the CLA application: pre Received-SPF: softfail (google.com: domain of transitioning nore...@puppetlabs.com does not designate 66.228.49.237 as permitted sender) client-ip=66.228.49.237; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning nore...@puppetlabs.com does not designate 66.228.49.237 as permitted sender) smtp.mail=nore...@puppetlabs.com /pre While its only a soft-fail, some remote SMTP systems might consider it potential spam and flag it, and we may find we lose some email. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[CLA Application - Bug #19903] SPF soft-fail for emails from the application
Issue #19903 has been updated by Dawn Foster. Cleaning up old bugs. I'm assuming this was resolved. Bug #19903: SPF soft-fail for emails from the application https://projects.puppetlabs.com/issues/19903#change-102600 * Author: Ken Barber * Status: Unreviewed * Priority: Low * Assignee: Kelsey Hightower * Category: * Target version: * Keywords: * Branch: Looking at the headers of an email I received from the CLA application: pre Received-SPF: softfail (google.com: domain of transitioning nore...@puppetlabs.com does not designate 66.228.49.237 as permitted sender) client-ip=66.228.49.237; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning nore...@puppetlabs.com does not designate 66.228.49.237 as permitted sender) smtp.mail=nore...@puppetlabs.com /pre While its only a soft-fail, some remote SMTP systems might consider it potential spam and flag it, and we may find we lose some email. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[CLA Application - Bug #19900] (Closed) Odd error when confirming email
Issue #19900 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I'm assuming this one was resolved. Bug #19900: Odd error when confirming email https://projects.puppetlabs.com/issues/19900#change-102602 * Author: Matthaus Owens * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: * Keywords: * Branch: I used the github integration when trying to use the CLA app and when I used the link in the email (https://cla.puppetlabs.com/emails/confirm/bbcfcbe1492419497dbba771d62e5f17097b619f1d630ed22d472e5bc3461a56), the application gave me the following error: No user found. Please try again. I had already signed the CLA previously on redmine, and my github username does not match my redmine username (but the emails should be the same). -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
Jira (HI-48) YAML syntax errors should mention the fielname
Title: Message Title
Charlie Sharpsteen updated an issue
Hiera / HI-48
YAML syntax errors should mention the fielname
Change By:
Charlie Sharpsteen
(fromacustomer) ThisistheerrormessageIwasseeing {code} err:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:(unknown):foundcharacterthatcannotstartanytokenwhilescanningforthenexttokenatline43column5warning:Notusingcacheonfailedcatalogerr:Couldnotretrievecatalog;skippingrun {code} aftersomepokingaroundifoundaproblem {code} listen: -%{::ipaddress}:80 {code} TheworkingsyntaxwouldbetheDOUBLEquotedone {code} listen: -%{::ipaddress}:80 {code} Coulderrormessagebeimprovedtocontainthefilename?
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/groups/opt_out.
Jira (PUP-1288) Windows user provider fails to create user with non-ASCII characters
Title: Message Title
Yoann LE TOUCHE commented on an issue
Re: Windows user provider fails to create user with non-ASCII characters
Fixed in puppet-3.2.1
Still a possible issue with binary data in a yaml statefile preventing puppet from running again. (see : https://projects.puppetlabs.com/issues/18323#note-1) I can't replicate the problem. Is it still an issue ?
As the last update to the redmine ticket was 6 month ago, I will close the ticket and should the problem still be there feel free to open a new issue.
Add Comment
Puppet / PUP-1288
Windows user provider fails to create user with non-ASCII characters
The windows_adsi user provider essentially does the following when creating a user: pre require 'Win32API' require 'win32ole' def computer_name buf = * 128 Win32API.new('kernel32', 'GetComputerName', ['P','P'], 'I').call(buf, buf.length.to_s) buf.unpack(A*) end conn = WIN32OLE.connect(WinNT://#{computer_name}) user = conn.C...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the
Jira (FACT-165) virtual - dmidecode: /dev/mem: Operation not permitted
Title: Message Title Jason Antman assigned an issue to Jason Antman Facter / FACT-165 virtual - dmidecode: /dev/mem: Operation not permitted Change By: Jason Antman Assignee: EricSorenson JasonAntman 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/groups/opt_out.
[Ask Puppet Labs - Bug #23428] (Closed) Concern on Twitter about our ask.com certificate not being secure.
Issue #23428 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I think I remember this being resolved. We can re-open in the new JIRA tracker if not: https://tickets.puppetlabs.com/browse/ASK Bug #23428: Concern on Twitter about our ask.com certificate not being secure. https://projects.puppetlabs.com/issues/23428#change-102603 * Author: Zach Leslie * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: Copying original jira issue here: See this tweet: https://twitter.com/fadenb/status/411103972469256192/photo/1 I'd like to be able to respond or have someone else respond with why this is happening or that it's fixed before the end of the week. Any help is appreciated. Thanks! Michelle -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
Jira (PUP-1418) Explicitly pass in variables to template()
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-1418 Explicitly pass in variables to template() Issue Type: Improvement Assignee: Unassigned Created: 11/Jan/14 8:46 AM Priority: Normal Reporter: Daniele Sluijters By default templates have access to the class scope so templates can access any variable available in the class that contains the resource which called out to template() and of course anything in top scope like Puppet settings or Facts. I would like a second option where one needs to explicitly pass an array of variables and except for what is available in top scope don't magically look up anything else. The reasoning behind this is mostly visibility. Currently there's no way, except for documenting it in a comment, to deduce from a Puppet manifest which variables are actually used in a template. One can open up the template and read through it to figure it out but that's about it. This approach should not break the old approach, if no array of variables is passed as a second argument to template() the old behaviour should remain. Add Comment
Jira (FACT-165) virtual - dmidecode: /dev/mem: Operation not permitted
Title: Message Title Jason Antman commented on an issue Re: virtual - dmidecode: /dev/mem: Operation not permitted The original requester (redmine) attached a patch which became https://github.com/puppetlabs/facter/pull/488. That was closed in favor of https://github.com/puppetlabs/facter/pull/510 opened by Jasper Lievisse Adriaanse (just added him as a watcher on this ticket) 5 months ago. Last update on that PR was by Adrien Thebo who closed the PR 3 months ago: summary: this has been open for two months, and Daniel has pointed out that we can't trust the permissions of /dev/mem, so we would need to parse the output of stderr to actually check for failures. Because of this I'm going to close this pull request for the time being. If the next actions can be addressed or there is new information related to this pull request, you can submit a new pull request or ask us to reopen this pull request. As far as I can tell, this is still waiting on those changes to be made. Perhaps Jasper is still interested in following up his previous PR and making the changes? Add Comment Facter / FACT-165 virtual - dmidecode: /dev/mem: Operation not permitted Inside LXC Containers the system can't open /dev/mem. The virtual.rb fact runs demidecode and does not throw error output into /dev/null: facter virtual /dev/mem: Operation not permitted Please see attached patch to move error output of dmidecode to /dev/null. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-165) virtual - dmidecode: /dev/mem: Operation not permitted
Title: Message Title Jason Antman assigned an issue to Unassigned Facter / FACT-165 virtual - dmidecode: /dev/mem: Operation not permitted Change By: Jason Antman Assignee: JasonAntman 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/groups/opt_out.
Jira (PUP-1121) Node regex beginning with dash results in invalid tag
Title: Message Title David Gwilliam updated an issue Puppet / PUP-1121 Node regex beginning with dash results in invalid tag Change By: David Gwilliam Affects Version/s: 3.4.2 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/groups/opt_out.
Jira (FACT-188) Improve operatingsystemrelease detection for Ubuntu
Title: Message Title Arnoud de Jonge commented on an issue Re: Improve operatingsystemrelease detection for Ubuntu lsb_release might not always be installed, so /etc/issue is the most reliable way to determine the release on Ubuntu. Add Comment Facter / FACT-188 Improve operatingsystemrelease detection for Ubuntu Right now we look at /etc/issue to determine operatingsystemrelease for Ubuntu, which should not be trusted. This is really just equivalent to the value of the lsbrelease fact, so we should just use that. 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/groups/opt_out.
Jira (PUP-1121) Node regex beginning with dash results in invalid tag
Title: Message Title David Gwilliam updated an issue Puppet / PUP-1121 Node regex beginning with dash results in invalid tag Change By: David Gwilliam 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/groups/opt_out.
[Ask Puppet Labs - Support #23407] (Closed) Update ask.puppetlabs.com footer
Issue #23407 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Recreated this bug with more details about exactly what we need to change here: https://tickets.puppetlabs.com/browse/ASK-1 Support #23407: Update ask.puppetlabs.com footer https://projects.puppetlabs.com/issues/23407#change-102604 * Author: Michelle Johansen * Status: Closed * Priority: High * Assignee: * Category: * Target version: * Keywords: * Branch: We need to change the 'Bug Tracker' footer link of ask.puppetlabs.com. Current Bug Tracker link is to projects.puppetlabs.com and it needs to be redirected to tickets.puppetlabs.com This should happen on 12/16/2013 -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
Jira (PUP-1121) Node regex beginning with dash results in invalid tag
Title: Message Title
David Gwilliam updated an issue
Puppet / PUP-1121
Node regex beginning with dash results in invalid tag
Change By:
David Gwilliam
Anoderegexstartingwithadashresultsinatagthatbeginswithadash,whichPuppetdoesn'tacceptasvalid: {noformat} node/-(abc|def)-/{ {noformat} resultsinthefollowingerrorwhenitismatched: {noformat} Invalidtag-abcdef-onnodehost-abc-5678.example.com {noformat} Removingtheinitialdashworksasexpected: {noformat} node/(abc|def)-/{ {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/groups/opt_out.
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Mark Jeromin assigned an issue to Mark Jeromin I cannot reproduce exactly as described by the OP in either Puppet 2.7.25 or Puppet 3.4.2 on CentOS 6.4. However, after renaming the /sbin/ifconfig, facter fails to output values for interfaces, ipaddress*, macaddress*, mtu*, and netmask* facts. The ipaddress fact can be mitigated by adding an entry to /etc/hosts. Facter / FACT-184 Using 'ip addr' over ifconfig Change By: Mark Jeromin Assignee: EricSorenson MarkJeromin 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/groups/opt_out.
Jira (PUP-1352) package ensure = purged is too noisy!
Title: Message Title
Edwin Ramos commented on an issue
Re: package ensure = purged is too noisy!
debug: Prefetching yum resources for package
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm --version'
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
''
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q moo --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}
'
debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -y erase moo'
notice: /Stage[main]/Moo/Package[moo]/ensure: created
debug: /Stage[main]/Moo/Package[moo]: The container Class[Moo] will propagate my refresh event
Add Comment
Puppet / PUP-1352
package ensure = purged is too noisy!
pre $packages = [ one, two, three ] package { $packages: ensure = purged, } /pre is too noisy. The logs are filled with: pre /Stage[main]/MODULE/Package[one]/ensure created. /Stage[main]/MODULE/Package[two]/ensure created. /Stage[main]/MODULE/Package[three]/ensure created. /pre on every run of puppet-agent.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1121) Node regex beginning with dash results in invalid tag
Title: Message Title David Gwilliam assigned an issue to David Gwilliam Puppet / PUP-1121 Node regex beginning with dash results in invalid tag Change By: David Gwilliam Assignee: DavidGwilliam 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/groups/opt_out.
[Ask Puppet Labs - Bug #22663] (Closed) Email filter weirdness
Issue #22663 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #22663: Email filter weirdness https://projects.puppetlabs.com/issues/22663#change-102605 * Author: Lee Lowder * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: * Keywords: * Branch: I have an email filter setup, set to move all emails that are from a...@puppetlabs.com. I have not changed this filter,and other filters work as expected. The headers still show a...@puppetlabs.com, but it is not being picked up by the filter so that instead of being moved to the proper folder, they are now being left in the inbox. This is on Windows 7 using Thunderbird 24.0. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #22657] (Closed) Older answers and questions are truncated
Issue #22657 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #22657: Older answers and questions are truncated https://projects.puppetlabs.com/issues/22657#change-102606 * Author: Lee Lowder * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: On the older questions and answers, they are being truncated. Newer questions show ... (more) type link, but on the older ones only the ... shows. If you edit the question or answer and click save - even if you do not change anything, then the full question shows. Screenshots are attached. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #22464] (Closed) ask.puppetlabs.com questiontext overruns sidebar
Issue #22464 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #22464: ask.puppetlabs.com questiontext overruns sidebar https://projects.puppetlabs.com/issues/22464#change-102607 * Author: Ruth Linehan * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: e.g. https://ask.puppetlabs.com/question/2911/error-could-not-find-certificate-request-for-pe-internal-dashboard before it was edited to add a code block. The text of the question overruns the sidebar. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #21270] (Closed) RSS links broken
Issue #21270 has been updated by Dawn Foster. Status changed from Re-opened to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #21270: RSS links broken https://projects.puppetlabs.com/issues/21270#change-102609 * Author: Joe Thompson * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #20267] (Closed) login with google account broken - 502 bad gateway error
Issue #20267 has been updated by Dawn Foster. Status changed from Investigating to Closed Cleaning up old bugs. It looks like this one has been resolved. Bug #20267: login with google account broken - 502 bad gateway error https://projects.puppetlabs.com/issues/20267#change-102611 * Author: Daniel Pittman * Status: Closed * Priority: High * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: I tried to log in with my Google account to ask.puppetlabs.com, and got sent to this URL: https://ask.puppetlabs.com/account/signin/complete/?next=%2Fusers%2F26%2Fdaniel-pittman%2Fsubscriptions%2F%3Fjanrain_nonce=2013-04-17T17%3A43%3A57ZfJZ65gopenid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0openid.mode=id_resopenid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fudopenid.response_nonce=2013-04-17T17%3A43%3A59ZQWSGDt407Zv_swopenid.return_to=http%3A%2F%2Fask.puppetlabs.com%2Faccount%2Fsignin%2Fcomplete%2F%3Fnext%3D%252Fusers%252F26%252Fdaniel-pittman%252Fsubscriptions%252F%253F%26janrain_nonce%3D2013-04-17T17%253A43%253A57ZfJZ65gopenid.assoc_handle=1.AMlYA9U5oDIbqGpk0k0posm9HmX3gX3CBWGqSQWrzPJDG7yPHhR5o3qOV051NAopenid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handleopenid.sig=%2F11T908%2B2Ngr%2B5cd2gdEdCdKAWM%3Dopenid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmDWcBs_YKoWHMKlqX_bI5tvEszn6 5yTMoopenid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmDWcBs_YKoWHMKlqX_bI5tvEszn65yTMo That reports, persistently, a 502 bad gateway error to me. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #19528] (Closed) OpenID sensitive to protocol spec
Issue #19528 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #19528: OpenID sensitive to protocol spec https://projects.puppetlabs.com/issues/19528#change-102612 * Author: Wil Cooley * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: I just tried to login with my OpenID without the protocol spec (https://;), which I guess I seem to do regularly. The site forwarded me to my OpenID provider and I logged in but upon coming back I got a bare white `502 Bad Gateway` nginx error (I regret that I did not capture the whole error, but there was not much more than that). I went through again, this time including the protocol spec and I was taken to a user registration page, which I assume is the expected behavior. Without clicking Signup on the registration page, I went back to the sign-in page, entered my OpenID w/o protocol spec again, (I assume) did the bounce through my OpenID provider, and this time was taken back to the PL-themed Askbot sign-in page, now with the error banner at the top that says, OpenID myexampleopenid.myopenid.com is invalid. So, it seems like there are two separate issues and I apologize in advance for being a lazy reporter and conflating them: 1. The nginx-generated error page is probably not what is intended; it should presumably be a pretty themed error page. 2. I should be able to drop the protocol spec; I do not know if this is contrary to the OpenID standard or not, but I cannot imagine any harm -- there should never be another identity at myexampleopenid.myopenid.com, regardless of whether the protocol is https://; or puppet:// or gopher://; (ok, maybe those two wouldn't work, but the point stands). -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Mark Myers assigned an issue to Mark Myers Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Mark Myers Assignee: MarkMyers 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/groups/opt_out.
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title
Mark Myers commented on an issue
Re: Windows Group and User fail during deletion even though it is successful
Code is correct in lib/puppet/provider/user/windows_adsi.rb and I tested on multiple Windows versions. I did not make any changes to code.
Add Comment
Puppet / PUP-1279
Windows Group and User fail during deletion even though it is successful
This is due to commit being called in the flush method when it should not be. Steps to reproduce: 1. Create a user `puppet apply -e user{'FakeTestUser': ensure = present, password = 'nobodyknowssupersecret', } 2. Delete a user - `puppet apply -e user{'FakeTestUser': ensure = absent, } pre Notice: /User[FakeTestUser]/ensure: 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
[Ask Puppet Labs - Bug #18914] (Closed) Email subscriptions - don't seem to get email when a question is asked
Issue #18914 has been updated by Dawn Foster. Status changed from Investigating to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #18914: Email subscriptions - don't seem to get email when a question is asked https://projects.puppetlabs.com/issues/18914#change-102614 * Author: Ken Barber * Status: Closed * Priority: High * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: It seems to me that I only seem to be getting an email when a question is answered, not asked. I've subscribed to all the options with 'Immediately': * Asked by me * Answered by me * Individually selected * Entire forum * Comments and posts mentioning me I would have thought 'entire forum' does the trick, but alas no. For those who really wish to partake in ask this is very helpful, as they can jump in and answer when a question is asked. Also, we received some spam this morning and it would be faster to action if we receive this through a notification ie. email. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #19144] (Closed) Account creation needs captcha-like thingy to at least reduce bots from account creation
Issue #19144 has been updated by Dawn Foster. Status changed from Accepted to Closed Cleaning up old bugs. I'm assuming this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #19144: Account creation needs captcha-like thingy to at least reduce bots from account creation https://projects.puppetlabs.com/issues/19144#change-102613 * Author: Ken Barber * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: Just talking to llowder on IRC about spam ... Currently the account creation process for ask can probably be automated by bots ... if we added a captcha process during account creation this might reduce some of the spam we are seeing, or at least reduce that attack surface area. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #18797] (Closed) Character / regarded as invalid in certificate
Issue #18797 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Closing. Wrong bug tracker. If it's still an issue, you can re-open it as a new ticket here: https://tickets.puppetlabs.com Bug #18797: Character / regarded as invalid in certificate https://projects.puppetlabs.com/issues/18797#change-102615 * Author: Anonymous * Status: Closed * Priority: Urgent * Assignee: * Category: * Target version: * Keywords: certificate * Branch: Package name: puppet-3.0.2-1.el6.noarch / is not accepted as a valid character in puppetmaster certificate. The fix was to modify /usr/lib/ruby/site_ruby/1.8/puppet/ssl/base.rb INCORRECT: VALID_CERTNAME = /\A[ -.0-~]+\Z/ CORRECT:VALID_CERTNAME = /\A[ -.0-~\/]+\Z/ So that / is accepted as a valid char in certificate. Error encountered: Could not request certificate: Certname [hidden] must not contain unprintable or non-ASCII characters -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
[Ask Puppet Labs - Bug #18409] (Closed) The use of variable $ id
Issue #18409 has been updated by Dawn Foster.
Status changed from Unreviewed to Closed
Cleaning up old bugs. This looks like it's in the wrong bug tracker. If it's
still an issue, you can open it as a new ticket here:
https://tickets.puppetlabs.com
Bug #18409: The use of variable $ id
https://projects.puppetlabs.com/issues/18409#change-102616
* Author: nan wu
* Status: Closed
* Priority: Normal
* Assignee: Zack Smith
* Category:
* Target version:
* Keywords: $id
* Branch:
In my site.pp,file { C:/XSpeedRunStop/:
source = puppet://puppet-test-02/files/XSpeedRunStop,
recurse = true,
owner = $id,
group = $id+s,
mode = 777,
}
But it does not have any reaction when I first performed.when i changed the
owner = $id to the owner = client-01\administrator,Perform kick command,This
module performs.Then changed the owner = client-01\administrator to owner =
$id,To perform kick command again,This module performs.In short, when I first
execution, use $ id, the module does not perform,This is a bug?
--
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://projects.puppetlabs.com/my/account
--
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/groups/opt_out.
[Ask Puppet Labs - Bug #18252] (Closed) set up staging server for ask.puppetlabs.com
Issue #18252 has been updated by Dawn Foster. Status changed from Unreviewed to Closed Cleaning up old bugs. I'm assuming this is resolved: https://tickets.puppetlabs.com/browse/ASK Bug #18252: set up staging server for ask.puppetlabs.com https://projects.puppetlabs.com/issues/18252#change-102617 * Author: Evgeny Fadeev * Status: Closed * Priority: Normal * Assignee: Kelsey Hightower * Category: * Target version: * Keywords: * Branch: we need a staging env to test improvements in the QA site deployment -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Mark Jeromin updated an issue Facter / FACT-184 Using 'ip addr' over ifconfig Change By: Mark Jeromin Issue Type: Bug Improvement 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/groups/opt_out.
Jira (FACT-184) Using 'ip addr' over ifconfig
Title: Message Title Mark Jeromin updated an issue Facter / FACT-184 Using 'ip addr' over ifconfig Change By: Mark Jeromin Assignee: MarkJeromin EricSorenson 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/groups/opt_out.
[Ask Puppet Labs - Bug #18191] (Closed) Mobile theme needs some love
Issue #18191 has been updated by Dawn Foster. Status changed from Accepted to Closed Cleaning up old bugs. It looks like this is resolved, but if not, you can open it as a new ticket here: https://tickets.puppetlabs.com/browse/ASK Bug #18191: Mobile theme needs some love https://projects.puppetlabs.com/issues/18191#change-102618 * Author: Dawn Foster * Status: Closed * Priority: Normal * Assignee: Evgeny Fadeev * Category: * Target version: * Keywords: * Branch: The mobile theme is really mangled ... to the point of being mostly unusable. I tested it on iPhone (Chrome Safari). The mobile theme doesn't need to be perfect. Most people will use the Ask site from their computers, but we'd like for it to look decent when people find answers via google search or if someone just wants to look at a question and answer. -- 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://projects.puppetlabs.com/my/account -- 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/groups/opt_out.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Eric Sorenson commented on an issue Re: Rename uniqueid hostid +1 to that plan, Jason Antman Add Comment Facter / FACT-198 Rename uniqueid hostid basing it on hostid is not nearly unique enough especially in a xen environment with duplicated machines and multiple instances of IPs and MACs. I'd suggest something like serial number from BIOS (works for dell, hp, ibm, etc - significant portion of all x86 machines) modified by the system time when facter was initially installed. 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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork. {noformat} #file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;} {noformat} Usingtheabovemanifestthefollowingdoesnotactasexpected.puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpectedmkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothingtouch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec
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/groups/opt_out.
Jira (FACT-198) Rename uniqueid hostid
Title: Message Title Eric Sorenson updated an issue Facter / FACT-198 Rename uniqueid hostid Change By: Eric Sorenson Assignee: EricSorenson JasonAntman 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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat} Usingtheabovemanifestthefollowingdoesnotactasexpected. {noformat} puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected {noformat}{noformat} mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing {noformat}{noformat} touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec {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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory, recurse=true,checksum=mtime, mode=644, notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1087) variables embedded in regexps are not expanded
Title: Message Title Edwin Ramos updated an issue Puppet / PUP-1087 variables embedded in regexps are not expanded Change By: Edwin Ramos Issue Type: Bug Improvement 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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null: alias=tar, refreshonly=true; }{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Arnoud de Jonge commented on an issue
Re: file resource can't be used to monitor file changes recursively
Works as expected. From the Puppet docs: When setting numeric permissions for directories, Puppet sets the search permission wherever the read permission is set. So the directories are set to 0655 and plain files to 0644. So after the mkdir, the directories are set to 0655, and puppet will not change that and thus doesn't run the exec.
Add Comment
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
for a long time i have used puppet to monitor a directory recursively for file changes but since upgrading to 2.6 that doesn't appear to work. {noformat} # file_test.pp file { /tmp/file_test: ensure = directory, recurse = true, checksum = mtime, mode = 644, notify = Exec[tar]; } exec { /bin/tar -cf - /tmp/file_t...
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
Jira (PUP-1108) Class inheritance and stages act weirdly
Title: Message Title luisa assigned an issue to luisa Puppet / PUP-1108 Class inheritance and stages act weirdly Change By: luisa Assignee: luisa 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/groups/opt_out.
Jira (PUP-1108) Class inheritance and stages act weirdly
Title: Message Title
luisa commented on an issue
Re: Class inheritance and stages act weirdly
in red mine got changed to accepted and also tagged with URGENT, this happened 2 years so the tag URGENT was not notices evidently
Add Comment
Puppet / PUP-1108
Class inheritance and stages act weirdly
Given the code: pre stage { first: before = Stage[main] } class foo { package{zsh: ensure = present } } class bar inherits foo { notify{/usr/bin/cowsay 'hello world': require = Package[zsh] } } class{bar: stage = first} /pre This produce pre err: Could not apply complete cat...
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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1239 file resource can't be used to monitor file changes recursively Change By: Daniel Dreier Affects Version/s: 2.7.25 Affects Version/s: 3.4.2 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/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier commented on an issue
Re: file resource can't be used to monitor file changes recursively
According to [Nigel](http://projects.puppetlabs.com/issues/5414#note-17) 3 years back,
All IÂ’m saying is that the feedback IÂ’ve gotten from developers is that this wasnÂ’t ever intended behavior. Whether it should or shouldnÂ’t have is undefined
I just reproduced the issue / absence of feature on 3.4.2 and 2.7.25 on Centos 6.4. It's not clear to me whether this should be a bug or feature request, but if it's a feature request then the fact that the recursive functionality doesn't work on standalone should probably trigger some sort of warning.
Add Comment
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
for a long time i have used puppet to monitor a directory recursively for file changes but since upgrading to 2.6 that doesn't appear to work. {noformat} # file_test.pp file { /tmp/file_test: ensure = directory, recurse = true, checksum = mtime, mode = 644, notify = Exec[tar]; } exec { /bin/tar -cf - /tmp/file_t...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1087) variables embedded in regexps are not expanded
Title: Message Title
Edwin Ramos commented on an issue
Re: variables embedded in regexps are not expanded
This ticket has been reproduced from redmine. Please refer to Henrik's comment under redmine.
Add Comment
Puppet / PUP-1087
variables embedded in regexps are not expanded
This doesn't define the notify resource: pre $foo = bar $bar = bar if $bar =~ /$foo/ { notify { bar: message=BAR; } } /pre It seems that variables within regexps are not being expanded. This is a problem for us as we're trying to define new resources that check facts for parameterised content via a regexp.
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/groups/opt_out.
Jira (PUP-1349) improve error message when File[undef] occurs
Title: Message Title Mark Myers assigned an issue to Mark Myers Puppet / PUP-1349 improve error message when File[undef] occurs Change By: Mark Myers Assignee: MarkMyers 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/groups/opt_out.
Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title Jason Antman assigned an issue to Eric Sorenson Puppet / PUP-1320 service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop Change By: Jason Antman Assignee: EricSorenson 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/groups/opt_out.
Jira (PUP-1189) Custom reports not working (Class is already defined in Puppet::Reports)
Title: Message Title luisa updated an issue Puppet / PUP-1189 Custom reports not working (Class is already defined in Puppet::Reports) Change By: luisa Assignee: CharlieSharpsteen 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/groups/opt_out.
Jira (PUP-1189) Custom reports not working (Class is already defined in Puppet::Reports)
Title: Message Title luisa commented on an issue Re: Custom reports not working (Class is already defined in Puppet::Reports) From comments in red-mine looks like it is fixed but should validated Add Comment Puppet / PUP-1189 Custom reports not working (Class is already defined in Puppet::Reports) I've got a client experiencing this with the boundary report from https://github.com/puppetlabs/puppetlabs-boundary Also someone in #puppet said they get it with the datadog report in Puppet 3.0. Here's the full message we get at the end of the run: err: Could not send report: Error 400 on SERVER: Could not autoload boundary: Class Boundary is al... 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/groups/opt_out.
Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title
Jason Antman commented on an issue
Re: service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
So part of this could be fixed in MCollective (the immediate issue that I'm seeing). However, that doesn't help the problem that Puppet still kills itself if it's running in daemon mode and you tell it to stop. I suppose I should look into how puppet handles this for refreshes/restarts of itself (I assume there's some special logic? or does this problem hold true there too?)
Add Comment
Puppet / PUP-1320
service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
We have recently switched from puppet agent in daemon mode (for kick) to cron-run puppet with mcollective agent. However, I started noticing that puppet policies were being inconsistently applied across the hosts. It turns out that this policy is the problem: {noformat} service { 'puppet': ensure = stopped, enable = false...
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
Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-1320 service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop Change By: Jason Antman Assignee: EricSorenson JasonAntman 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/groups/opt_out.
Jira (PUP-1078) Exported resources are hard to collect by environment
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-1078
Exported resources are hard to collect by environment
Change By:
Reid Vandewiele
Inoticedtodaythat {{ Foo|| }} collectsallFooresourcesregardlessofenvironment.Doing {{ Foo|environment==...| }} wouldbecool,butIdon'tthinkthatworks.Whywasthisaproblem?Ihavemultipledeployments;someofwhichcannotseeeachotheronthenetwork(outsideofthestoreconfigsdb).Asaresultofthisbehavior(collectallresourcesinallenvironments),Ihavenagiosinstancesthattrytomonitormachinestheycan'tseeandthusallchecksfailandpagergoesbeepbeep.;)Ifoundaworkaroundusingtags. pre {code} nodedefault{#Globallyapplyanenvironment-basedtagtoallresourcesoneachnode.tag(deployment::$environment)...}#Andlater...SomeResource|tag==deployment::$environment| /pre {code} Theaboveworkaroundissufficientformetocontinuedeployingexportedresources(notablocker).Iwasexpectingcollectorsofexportedresourceswouldonly,bydefault,getresourcesfromthesameenvironment.Barringthat,Ithinkaqueryof {{ |environment==...| }} wouldbequiteusefulratherthanresortingtotagging.
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/groups/opt_out.
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-1244 Yum provider using version-release to validate installation. Change By: Jason Antman Assignee: JasonAntman 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/groups/opt_out.
Jira (PUP-682) Comparing package versions in puppet behaves differently to yum
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-682 Comparing package versions in puppet behaves differently to yum Change By: Jason Antman Assignee: JasonAntman 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/groups/opt_out.
Jira (PUP-683) Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-683 Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest Change By: Jason Antman Assignee: JasonAntman 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/groups/opt_out.
Jira (PUP-683) Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest
Title: Message Title Jason Antman commented on an issue Re: Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest My work for PUP-1244 should either fix this, or provide 99% of the fix, depending on how far I get. Add Comment Puppet / PUP-683 Puppet yum provider for package resource does not appear to use 'release' tag to ensure latest Puppet's yum provider for the package resource does not appear to offer complete support for RPM naming/versioning. Yum compares RPMs using the RPM naming convention (e.g name-version-release.arch.rpm). Our snapshot RPMs make use of this convention and rely upon the fact that yum can distinguish between RPMs based on the release components. For 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
Jira (PUP-1175) Puppet ssh_authorized_keys fails on one account if key with same name exists in another account
Title: Message Title Arnoud de Jonge commented on an issue Re: Puppet ssh_authorized_keys fails on one account if key with same name exists in another account I can't replicate this behaviour. I've tried various orders of making the keys on the root account and the user account, but I don't see the error. I've tried with Puppet 3.1.1. Can you specify which version of Puppet you are using? Add Comment Puppet / PUP-1175 Puppet ssh_authorized_keys fails on one account if key with same name exists in another account Hello, I have been trying to debug this very strange error: err: /Stage[main]/Accounts::Human::Sshkeys/Ssh_authorized_key[jgoerzen@wile]: Could not evaluate: No such file or directory - /home/jgoerzen/.ssh/authorized_keys I observed that it went away if I changed the name jgoerzen@wile to jgoerzen@wile2 in my Puppet .pp files. This is a v... 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-1328) gem package provider should reset permissions
Title: Message Title Daniel Dreier commented on an issue Re: gem package provider should reset permissions There was discussion on redmine about whether this is a bug or feature, and what behavior is desired. It was rejected a year ago and re-opened a month ago. A decision is needed on whether we stick with the potentially confusing behavior of rubygems is a feature or problem to be worked around in puppet. Add Comment Puppet / PUP-1328 gem package provider should reset permissions If the user running `puppet apply` uses a restrictive umask (e.g. 0077), gems installed using the gem package provider will be unreadable for all users except root. rubygems author has [ruled this behaviour as a feature](https://github.com/rubygems/rubygems/issues/272), but in Puppet context I fail to see a reason why the gem package provider should be... 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-1328) gem package provider should reset permissions
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1328 gem package provider should reset permissions Change By: Daniel Dreier Component/s: TypesandProviders 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/groups/opt_out.
Jira (PUP-1319) Ability to run --onetime in the background while a daemon is idle
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1319 Ability to run --onetime in the background while a daemon is idle Change By: Daniel Dreier Issue Type: Bug Improvement 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/groups/opt_out.
Jira (PUP-1217) yum provider + package groups giving unnecessary errors
Title: Message Title Pamela Harrison assigned an issue to Jason Antman Via IRC conversation, jantman has a fix idea. Puppet / PUP-1217 yum provider + package groups giving unnecessary errors Change By: Pamela Harrison Assignee: JasonAntman 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/groups/opt_out.
Jira (FACT-175) undefined method `enum_lsdev' for Facter::Util::Processor:Module with facter 1.6.14
Title: Message Title Edwin Hermans commented on an issue Re: undefined method `enum_lsdev' for Facter::Util::Processor:Module with facter 1.6.14 I couldn't reproduce this, on linux or macosx. Add Comment Facter / FACT-175 undefined method `enum_lsdev' for Facter::Util::Processor:Module with facter 1.6.14 install facter 1.6.14 using gem on ubuntu12.04 and get this message: root@node6:~# gem install facter root@node6:~# facter Error: undefined method `enum_lsdev' for Facter::Util::Processor:Module ruby version is 1.8.7 facter 1.6.13 is ok 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/groups/opt_out.
Jira (PUP-1078) Exported resources are hard to collect by environment
Title: Message Title
Reid Vandewiele commented on an issue
Re: Exported resources are hard to collect by environment
The root problem here is probably that the storeconfigs backend (the supported backend being PuppetDB) doesn't support environments. That means that when resources are exported from any environment, they are stored in a common pool, from which all collectors in all environments then match.
We have a story open right now to make PuppetDB environment aware (PDB-24). PuppetDB will need to be environment aware in order to modify the behavior of collectors.
The two possible resolutions to this issue, assuming PuppetDB is capable of distinguishing environments, are:
1. PuppetDB isolates environments and resources cannot be collected from other environments. No language changes. 2. PuppetDB isolates environments but we allow resources from other environments to be collected. Language changes will be required.
If there are any use cases for #2, then a separate feature request should be filed.
Add Comment
Puppet / PUP-1078
Exported resources are hard to collect by environment
I noticed today that {{Foo | |}} collects all Foo resources regardless of environment. Doing {{Foo | environment == ... |}} would be cool, but I don't think that works. Why was this a problem? I have multiple deployments; some of which cannot see each other on the network (outside of the storeconfigs db). As a result of this behavior (collect a...
Jira (FACT-175) undefined method `enum_lsdev' for Facter::Util::Processor:Module with facter 1.6.14
Title: Message Title Edwin Hermans commented on an issue Re: undefined method `enum_lsdev' for Facter::Util::Processor:Module with facter 1.6.14 The original poster FORREST ALDRICH of the current problem could perhaps give more debugging output, otherwise I'd close this ticket. Add Comment Facter / FACT-175 undefined method `enum_lsdev' for Facter::Util::Processor:Module with facter 1.6.14 install facter 1.6.14 using gem on ubuntu12.04 and get this message: root@node6:~# gem install facter root@node6:~# facter Error: undefined method `enum_lsdev' for Facter::Util::Processor:Module ruby version is 1.8.7 facter 1.6.13 is ok 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/groups/opt_out.
Jira (PUP-1383) RHEL init scripts unable to distinguish properly between agent and master
Title: Message Title Jason Antman commented on an issue Re: RHEL init scripts unable to distinguish properly between agent and master Confirmed on CentOS 6.4 using puppet-3.4.1-1.el6.noarch puppetlabs package. Last (and only) comment in Redmine was by Andrew Parker: Charlie Sharpsteen had put together a patch at https://github.com/puppetlabs/puppet/pull/1726, but according to Moses Mendoza this patch won’t work for EL5 systems. I suppose I could be missing something here, but it seems like the pidfile should prevent this issue from happening. I'll try and dig into this a bit further... Add Comment Puppet / PUP-1383 RHEL init scripts unable to distinguish properly between agent and master The init scripts on EL systems are mis-identifying the master process when the agent is running. The following interaction seems to show that the master is being recognized simply as `puppet`, which is causing it problems when getting the status of the master when it isn't running. pre [root@rhel6-64-puppet-3 ~]# service puppet status puppet is sto... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1383) RHEL init scripts unable to distinguish properly between agent and master
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-1383 RHEL init scripts unable to distinguish properly between agent and master Change By: Jason Antman Assignee: JasonAntman 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/groups/opt_out.
Jira (HI-123) hiera json backend is broken on puppet 3.1.1 for windows
Title: Message Title
Edwin Hermans commented on an issue
Re: hiera json backend is broken on puppet 3.1.1 for windows
As Josh Cooper mentioned: we should probably package json_pure by default and update the Gemfile accordingly. This was also chosen as the current fix for the problem.
Add Comment
Hiera / HI-123
hiera json backend is broken on puppet 3.1.1 for windows
From this example: http://www.craigdunn.org/2011/10/puppet-configuration-variables-and-hiera/ pre C:\Users\Administrator\tempgt; type hiera.yaml :backends: - json :logger: console :hierarchy: - %{env} - common :json: :datadir: hieradataC:\Users\Administrator\temp\hieradatatype common.json { webname: localhost...
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-1203) Ordering with chaining arrows and collectors is not working
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-1203
Ordering with chaining arrows and collectors is not working
Change By:
Reid Vandewiele
Considerthefollowingscenario:AnanchorthatmarksthestartofaclassneedstohaveorderingstatementssotheAnchorisprocessedbeforeanypackageinthatclass.Accordingtothelangdocs,tagssection, ahref=""> [resourcesareautomaticallytaggedwiththeclassname| http://docs.puppetlabs.com/puppet/3/reference/lang_tags.html#automatic-tagging resourcesareautomaticallytaggedwiththeclassname/a ] : pre {quote} Everyresourceautomaticallyreceivesthefollowingtags: li * Itsresourcetype li * Thefullnameoftheclassand/ordefinedtypeinwhichtheresourcewasdeclared li * Everynamespacesegmentoftheresource’sclassand/ordefinedtype /pre {quote} Therefore,itwouldmakesensetousethefollowingcodetoestablishorderingrelationshipsbetweenstartanchorsandclassresources: pre { code } classtestmod{anchor{'testmod::begin':}Anchor['testmod::begin']-Package|tag=='testmod'|package{'htop':}package{'vim':}} / { code /pre } However,theoutcomeisthattheexpressedorderrelationshipismissing.Forthisexampleclass,usingPuppetversion:3.2.2,IgetthefollowingdotfilegeneratedbyPuppet,whichclearlyshowsthattheDAGismissingtheconnectionbetweentheAnchorandthepackageresources: ahref=""> http://pastebin.ca/2478032 http://pastebin.ca/2478032/a This,ofcourse,unfortunatelyresultsinbrokenpuppetruns.(Orworse,youareluckyanddon'tgetbrokenrunsduringtests)
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-1363) yum helper fails when using a custom yum plugin with custom variables
Title: Message Title
Jason Antman commented on an issue
Re: yum helper fails when using a custom yum plugin with custom variables
History in Redmine asked reporter to try a patch a year ago. No response, no updates, no other watchers. The redmine ticket did reference PUP-1362. Closing as cannot reproduce, since nobody else has watched this or commented on it in a year, and it's enough of an edge case that I can't reproduce.
Add Comment
Puppet / PUP-1363
yum helper fails when using a custom yum plugin with custom variables
We have a custom yum plugin that provides a custom variable for use in our .repo files and the Puppet yum helper does not function correctly with custom variables. First, we ensure our yum plugin is installed on all machines: package { 'SNC-2-1-1-1:.:.:snc-yum': name = 'snc-yum', ensure = installed } Th...
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-1319) Ability to run --onetime in the background while a daemon is idle
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1319 Ability to run --onetime in the background while a daemon is idle Change By: Daniel Dreier Affects Version/s: 2.7.25 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/groups/opt_out.
Jira (PUP-1319) Ability to run --onetime in the background while a daemon is idle
Title: Message Title Daniel Dreier commented on an issue Re: Ability to run --onetime in the background while a daemon is idle This issue appears to be resolved in 3.4.2 - just based on very casual testing. Add Comment Puppet / PUP-1319 Ability to run --onetime in the background while a daemon is idle When the puppetd daemon is running it has the pid file preventing other background daemons. When running --onetime --no-daemonize - a foreground run - this is fine, pid file doesnt prevent the --onetime run but if you wanted to do a backgrounded --onetime run the pid file will prevent that run from happening. We should arrange so that a backgrounded... 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/groups/opt_out.
Jira (FACT-169) processorcount on hpux is wrong
Title: Message Title
Charlie Sharpsteen updated an issue
Facter / FACT-169
processorcount on hpux is wrong
Change By:
Charlie Sharpsteen
Factersays: {code} #facterprocessorcount8 {code} Yettheserver(avPar)hasonlyonecpuallocated.WhatitisdetectingistheamountofCPUsinthenPar.Generallythishappenswhenyouuse ' {{ ioscan-fkCprocessor ' }} ,insteadofsomethinglike: {{ mpsched-s|awk'/ProcessorCount/{print$NF;}' }} .
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/groups/opt_out.
Jira (FACT-169) processorcount on hpux is wrong
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: processorcount on hpux is wrong
Currently, we don't have access to a HP-UX box here at Puppet Labs. We would be glad to take a patch for this issue but it would have to be developed and tested by someone with access to the HP-UX hardware and operating system.
Add Comment
Facter / FACT-169
processorcount on hpux is wrong
Facter says: {code} # facter processorcount 8 {code} Yet the server ( a vPar ) has only one cpu allocated. What it is detecting is the amount of CPUs in the nPar. Generally this happens when you use {{ioscan -fkCprocessor}}, instead of something like: {{mpsched -s | awk '/Processor Count/{print $NF;}'}}.
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-1340) Unrecognised escape sequence '\`' in file (escaped backtick in manifest)
Title: Message Title Pamela Harrison assigned an issue to Pamela Harrison Puppet / PUP-1340 Unrecognised escape sequence '\`' in file (escaped backtick in manifest) Change By: Pamela Harrison Assignee: PamelaHarrison 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/groups/opt_out.
Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module
Title: Message Title Pamela Harrison assigned an issue to Pamela Harrison Puppet / PUP-1030 FreeBSD: Puppet triggers loading of ZFS module Change By: Pamela Harrison Assignee: PamelaHarrison 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/groups/opt_out.
