Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title Jeff Sparrow commented on PUP-9043 Re: file resource - mtime checksum does not seem to work Any idea when or what puppet/ruby build this will be fixed in? It continues to be an issues with multiple vendors. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4817) Use different method to determine duplicate declarations with windows package
Title: Message Title Jeff Sparrow commented on PUP-4817 Re: Use different method to determine duplicate declarations with windows package Right. I package everything in to Chocolatey, but only because Puppet cant handle it. Would be nice if Puppet handled Windows packages correctly. I see it as simple as allowing a parameter on package resources to ignore duplicate declarations. Actually there are numerous places in Windows that duplicate declaration makes Puppet life harder, than easier. Windows services as well. Cant start a service and then stop it with Puppet. You'll get a duplicate declaration issue. Leave you again to use one service resource and one exec resource. After 7 years I just ended up writing my own functions to bypass my hatred for duplicate declaration issues in Puppet on Windows. Its always a struggle and although I figured the answer would be 'wont do' I thought I'd ask. Its like my 8th ticket over my Puppet career asking for duplicate declarations to be allowed with a param. No worries. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title Jeff Sparrow commented on PUP-9043 Re: file resource - mtime checksum does not seem to work Josh Cooper - I think you hit it right on the head when you said this: However, i've noticed that if the connection is disconnected during download, ruby will ignore the resulting EOFError, which will cause puppet to write out a partial file. See https://github.com/ruby/ruby/blob/v2_4_4/lib/net/http/response.rb#L293 and https://github.com/ruby/ruby/blob/v2_4_4/lib/net/protocol.rb#L129. And since puppet completes the file download, it will rename the temporary truncated file over the real file, and will not update the file again (until the mtime changes on the server). We dug into this a bit further yesterday. That is exactly what has happened on our side, it appears. The Puppet run was done during the transfer of that file to artifactory. It is transferred around 6am every day, then this specific group runs puppet around 8-9am. However, on this day, the file wasnt transferred to Artifactory until around 8am. At 1.4GB it took a couple seconds, and it appears only part of the file was downloaded during this teams Puppet runs. Then, as you alluded to, Puppet will never update the file again, because the mtime locally is greater than or equal to the remote file. Since the mtime is actually greater, but the file was incomplete, it would never be resolved again; except through manual intervention. Thus, between no md5 availability for artifactory, or mtime not being rechecked, the file will always be bad. Just curious, is there a reason that the greater than **portion of mtime checking exists? I understand there would be a slight time difference for transfer, but it would seem that if its an extended period of time, say beyond an hour or so difference, that the file has likely been changed (or in our case is incorrect all together) and thus puppet would then view the file as not being the same? Add Comment
Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-9043 file resource - mtime checksum does not seem to work Issue Type: Bug Assignee: Unassigned Created: 2018/08/06 12:25 PM Labels: file checksum artifactory http Priority: Normal Reporter: Jeff Sparrow Puppet Version: 4.10.9 Puppet Server Version: 2.8.0 OS Name/Version: Windows 201x Describe your issue in as much detail as possible… The mtime checksum for a file resource, does not seem to work with Artifactory. I don't know if this extends into oter http resources, but we are seeing this issue with Artifactory for sure. I am aware of PUP-6114 for md5 checksum fixes, but this is for mtime. I am not sure if there is already a ticket open for this or not, but I didnt see one, so here this is. We have 70 some servers that all have this issue. Here is a file we are obtaining from artifactory, as you can see it has a last-modified time of: Last-Modified: Sat, 04 Aug 2018 08:19:42 GMT Here is a list of the server times of that file. The size of the file is drastically different on every server as well. Its a 1.4GB file and some servers only have a file size of 100KB.
Jira (PUP-6114) Add support for Artifactory checksum headers and enable SHA1 checksum type
Title: Message Title Jeff Sparrow commented on PUP-6114 Re: Add support for Artifactory checksum headers and enable SHA1 checksum type Would love to see this implemented. Multiple vendors of our use artifactory for shares, chocolatey, builds, etc. We recently ran into a big headache where we realized files were not md5 checking, using artifactory and its `X-CheckSum-xxx`. As a side note, it also seems that `mtime` is also way off on numerous files vs. the artifactory (remote) `mtime`. Without this update, I will have to move all `file` resources that use artifactory, to a file uri. Which means having to move these to more of a file share type system. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow commented on FACT-1817 Re: Facter: Custom Fact failures due to Facter.add inside if statement. This can be closed. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow commented on FACT-1817 Re: Facter: Custom Fact failures due to Facter.add inside if statement. Oo. I was just debugging through it as I was replying to you, and I see it now. By moving the Facter.add outside of the if statement, I am effectively also moving it outside the requirement of if (kernel == 'windows') and (phys_virt != 'physical') thus, it will actually set Facter.add regardless (and correctly). I really need to get someone to rewrite these things Thanks!!! Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow commented on FACT-1817 Re: Facter: Custom Fact failures due to Facter.add inside if statement. Is it possible to provide some sort of example that causes this? It is all in the gists. Specifically the change in the hba_fc_passthrough.rb files. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow created an issue Facter / FACT-1817 Facter: Custom Fact failures due to Facter.add inside if statement. Issue Type: Bug Affects Versions: FACT 3.6.8 Assignee: Unassigned Created: 2018/02/08 8:51 AM Priority: Normal Reporter: Jeff Sparrow Basic Info Module Version: 3.6.8 Puppet Version: 4.10.9 OS Name/Version: Windows 2012r2/2016 There are two issues here (perhaps related, perhaps not, I'll let you decide). 1. Custom facts will not be found if Facter.add is inside an if statement 2. In a single custom fact file, all custom facts will fail to be found if ANY custom fact isnt found (in this case because of issue 1) Running into a very strange issue with Facter 3.6.8. We have not seen this behavior on old 2x versions (we just upgraded). We have numerous custom facts. Many of them rely on each other. Something changed in our environment and we had custom facts failing. Looking in to this, I couldnt figure out why; as the custom facts resolve just fine, but the facts that rely on those exact same custom facts were failing. In this example, qlogic_hbasettings.rb relies on custom facts created in qlogicfcfacts.rb and hca_fc_passthrough.rb. It would appear that if any custom facts are not found, the rest will fail as well. This can be observed by the changes in the 2nd gist below, where I move the Facter.add call outside the if statement. When I do that, all the custom facts work. I couldn't find anything in the release notes or issues regarding calling Facter.add inside or outside an if/else loop. The issue did not exist on older versions of facter. Seems like Facter.add should work wherever a user places it (to a degree). There should be a warning for facts if a custom fact is being called and it can not resolve or be found. In this case, facter just keeps going and thus, so does puppet. This can put users in a state where things are failing, but they are not aware of the failures. This will fail:
Jira (FACT-1817) Facter: Custom Fact failures due to Facter.add inside if statement.
Title: Message Title Jeff Sparrow commented on FACT-1817 Re: Facter: Custom Fact failures due to Facter.add inside if statement. And as a user said in slack: That is, without a doubt, the gnarliest custom fact I've ever seen @singularity42 :beer: Yes they are and I apologized for that. Sorry they are not more clear. They were written 5-6 years ago when I had no idea even what a variable or loop was. Since then, they have been moved over to other people and never refactored. Maybe someday... Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8222) puppet timestamping for every event
Title: Message Title Jeff Sparrow commented on PUP-8222 Re: puppet timestamping for every event Thanks. I suppose Windows Event viewer shall do. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1158) Facter::Util::Resolution.exec on Windows fails to exec paths with spaces
Title: Message Title
Jeff Sparrow commented on FACT-1158
Re: Facter::Util::Resolution.exec on Windows fails to exec paths with spaces
Let me run the above reproduction, but it sure seems to be the same:
Looks like it tries to expand the program name by PATH, causing it to fail:
Facter::Core::Execution.exec('quacli')
executing command: C:\Windows\system32\cmd.exe /c "C:\Program Files\QLogic Corporation\QConvergeConsoleCLI\qaucli.exe"
which then fails because it expands the file path and then comes back with:
'C:\Program' is not recognized as an internal or external command
%PATH%
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\ProgramData\chocolatey\bin;C:\Program Files\QLogic Corporation\QConvergeConsoleCLI\;C:\PROGRA~1\Emulex\Util\OCManager;C:\Program Files (x86)\Dell\Enterprise Manager\msagui;c:\Program Files\Puppet Labs\Puppet\bin;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Nmap
I did notice that
Jira (FACT-1158) Facter::Util::Resolution.exec on Windows fails to exec paths with spaces
Title: Message Title Jeff Sparrow commented on FACT-1158 Re: Facter::Util::Resolution.exec on Windows fails to exec paths with spaces I realize this ticket is long closed, however I am running in to this issue on Facter 3.6.7 - should I create a new ticket? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8222) puppet timestamping for every event
Title: Message Title
Jeff Sparrow updated an issue
Puppet / PUP-8222
puppet timestamping for every event
Change By:
Jeff Sparrow
Been using Puppet for ~ 5 years now. Had a user come up and ask me something that I didn't think twice about. They asked where the time stamps were for each thing puppet was doing. Lo and behold, I can't find timestamps on the things Puppet is doing. We can see timestamps for the report time, time stamps for some notices, and time stamps in event viewer, by beyond that, no other time stamps (like if you ran puppet manually). The event viewer helps, but I figured if it can create a timestamp of when each action is occurring, that Puppet itself should be able to do the same. I mentioned this to a few people on #windows in slack, and they agreed it would be a nice auditing feature to have. Maybe something like this:{code:java}Debug: Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type](provider=registry)Debug: Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags](provider=registry)Debug: Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval](provider=registry){code}to this:{code:java}Debug (07:23:34): Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type](provider=registry)Debug (07:23:47): Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags](provider=registry)Debug (07:24:02): Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval](provider=registry){code} just as an example. Please consider this feature.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8222) puppet timestamping for every event
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-8222 puppet timestamping for every event Issue Type: New Feature Assignee: Unassigned Created: 2017/12/01 5:26 AM Priority: Normal Reporter: Jeff Sparrow Been using Puppet for ~ 5 years now. Had a user come up and ask me something that I didn't think twice about. They asked where the time stamps were for each thing puppet was doing. Lo and behold, I can't find timestamps on the things Puppet is doing. We can see timestamps for the report time, time stamps for some notices, and time stamps in event viewer, by beyond that, no other time stamps (like if you ran puppet manually). The event viewer helps, but I figured if it can create a timestamp of when each action is occurring, that Puppet itself should be able to do the same. I mentioned this to a few people on #windows in slack, and they agreed it would be a nice auditing feature to have. Maybe something like this: Debug: Checking the existence of registry value: Registry_value[HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type](provider=registry) Debug: Checking the existence of registry value:
Jira (FACT-1777) `load': cannot load such file - LoadError
Title: Message Title Jeff Sparrow commented on FACT-1777 Re: `load': cannot load such file - LoadError This appears to be an issue in path, as Michael Smith elluded to. Broken: C:\Users\Administrator>echo %PATH% C:\PROGRA~1\Java\jdk1.8.0_131\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\chocolatey\bin;C:\Program Files\Java\jdk1.8.0_102\bin;C:\Program Files (x86)\Notepad++;C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin;C:\Program Files (x86)\PuTTY\;C:\Program Files\Java\jdk1.8.0_131\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps; Working: C:\Users\Administrator>echo %PATH% C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\chocolatey\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps; Notice: C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin; in the
Jira (FACT-1777) `load': cannot load such file - LoadError
Title: Message Title Jeff Sparrow updated an issue Facter / FACT-1777 `load': cannot load such file - LoadError added msi verbose upgrade log per request of jpogran via slack Change By: Jeff Sparrow Attachment: msi_verbose_upgrade_log.txt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1777) `load': cannot load such file - LoadError
Title: Message Title Jeff Sparrow commented on FACT-1777 Re: `load': cannot load such file - LoadError > You'll want to put C:\Program Files\Puppet Labs\Puppet\bin before the sys\ruby\bin. I have not changed %PATH% beyond what installing puppet does. However, this is a server that originally had puppet<3.7.3>/facter<2.3.0> installed. Is upgrading from -> to those versions not supported, or is there an upgrade path that we need to follow? > Also, I'm not sure what facter - is expected to do... In the past, facter - would allow me to actually do useful things with facter: eg; C:\Users\Administrator>facter -help facter(8) -- Gather system information == SYNOPSIS Collect and display facts about the system.
Jira (FACT-1778) Puppet/Facter loading facts twice
Title: Message Title Jeff Sparrow commented on FACT-1778 Re: Puppet/Facter loading facts twice no problem. Thanks Michael Smith for looking at this. We will eventually be moving to latest Puppet and thus puppet-agent. So hopefully the fix will be out for us by that time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1778) Puppet/Facter loading facts twice
Title: Message Title Jeff Sparrow commented on FACT-1778 Re: Puppet/Facter loading facts twice fyi, I ran a puppet config print and I see factpath is factpath = C:/ProgramData/PuppetLabs/puppet/cache/lib/facter;C:/ProgramData/PuppetLabs/puppet/cache/facts but we aren't specifically setting that anywhere. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1778) Puppet/Facter loading facts twice
Title: Message Title Jeff Sparrow commented on FACT-1778 Re: Puppet/Facter loading facts twice interesting find, we will eventually be going to puppet 5 (latest) any idea what it looks like in that? fix or work around maybe? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1777) `load': cannot load such file - LoadError
Title: Message Title
Jeff Sparrow commented on FACT-1777
Re: `load': cannot load such file - LoadError
Michael Smith - That information should all be in the environment portion of the ticket. WHich I dont see for some reason, unless i click on the history tab. None the less, here is again:
C:\Users\Administrator>where facter
C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\facter
C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\facter.bat
C:\Program Files\Puppet Labs\Puppet\bin\facter.bat
C:\Users\Administrator>echo %PATH%
C:\PROGRA~1\Java\jdk1.8.0_131\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\chocolatey\bin;C:\Program Files\Java\jdk1.8.0_102\bin;C:\Program Files (x86)\Notepad++;C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin;C:\Program Files (x86)\PuTTY\;C:\Program Files\Java\jdk1.8.0_131\bin;C:\Program Files\Puppet Labs\Puppet\bin;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;
Is facter - }} even supported in 3.6.7 , puppet 4.10.8 ? It seems like the path is correct, because it knows what {{facter is, but its looking in the wrong path for the gem.
Jira (PUP-5934) Updated fact values should be submitted after each Puppet run
Title: Message Title Jeff Sparrow commented on PUP-5934 Re: Updated fact values should be submitted after each Puppet run 1 have wanted this for 5 years Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1778) Puppet/Facter loading facts twice
Title: Message Title Jeff Sparrow created an issue Facter / FACT-1778 Puppet/Facter loading facts twice Issue Type: Bug Affects Versions: FACT 3.6.7 Assignee: Unassigned Created: 2017/10/11 8:54 AM Priority: Normal Reporter: Jeff Sparrow Just went from Puppet 3.7.3 to Puppet 4.10.8 I now see my custom facts load twice at the beginning of a Puppet run. I was told in #irc this was an expected behavior, that has been filed many times, but thats just how it is? Is there a reason for this, or a work around? This really messes up our entire environment as some servers can take up to 6 (sometimes 8 minutes) just to gather facts. These are large storage servers with sometimes 200 luns attached. In addition, some of our 730's and newer 930's have 16-24 ports in them, which are also ran through facter. This was not an issue for the last 4-5 years, but seems like there is no way around this? Is that a correct statement? Add Comment
Jira (FACT-1777) `load': cannot load such file - LoadError
Title: Message Title Jeff Sparrow commented on FACT-1777 Re: `load': cannot load such file - LoadError hmmm. Is this possibly due to changes over time, that now use puppet facts , instead of something like facter -p ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1777) `load': cannot load such file - LoadError
Title: Message Title
Jeff Sparrow updated an issue
Facter / FACT-1777
`load': cannot load such file - LoadError
Change By:
Jeff Sparrow
Environment:
{code:java}Host Name: PPT-2016-1OS Name: Microsoft Windows Server 2016 StandardOS Version:10.0.14393 N/A Build 14393OS Manufacturer: Microsoft CorporationOS Configuration: Standalone ServerOS Build Type: Multiprocessor FreeRegistered Owner: DellRegistered Organization: DellProduct ID:00377-6-0-AA980Original Install Date: 5/30/2017, 8:27:38 AMSystem Boot Time: 9/6/2017, 8:21:41 AMSystem Manufacturer: VMware, Inc.System Model: VMware Virtual PlatformSystem Type: x64-based PCProcessor(s): 1 Processor(s) Installed. [01]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2395 MhzBIOS Version: Phoenix Technologies LTD 6.00, 4/5/2016Windows Directory: C:\WindowsSystem Directory: C:\Windows\system32Boot Device: \Device\HarddiskVolume1System Locale: en-us;English (United States)Input Locale: en-us;English (United States)Time Zone: (UTC-06:00) Central Time (US & Canada)Total Physical Memory: 4,096 MBAvailable Physical Memory: 2,789 MBVirtual Memory: Max Size: 4,800 MBVirtual Memory: Available: 3,536 MBVirtual Memory: In Use:1,264 MBPage File Location(s): C:\pagefile.sysDomain:WORKGROUPLogon Server: \\PPT-2016-1Hotfix(s): 6 Hotfix(s) Installed. [01]: KB3186568 [02]: KB3192137 [03]: KB3199986 [04]: KB4023834 [05]: KB4035631 [06]: KB4034658Network Card(s): 1 NIC(s) Installed. [01]: vmxnet3 Ethernet Adapter Connection Name: abiyvuzk DHCP Enabled:Yes DHCP Server: 100.88.0.122 IP address(es) [01]: 100.91.41.20Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.{code}{code:java}C:\Users\Administrator>gem list*** LOCAL GEMS ***bigdecimal (1.2.4)deep_merge (1.0.1)facter (3.6.7)fast_gettext (1.1.0)ffi (1.9.14 x64-mingw32)gettext (3.2.2)gettext-setup (0.20)hocon (1.2.5)io-console (0.4.3)json (1.8.1)locale (2.1.2)minitar (0.6.1)minitest (4.7.5)nats-pure (0.2.4)net-ssh (4.1.0)psych (2.0.5)puppet (4.10.8)rake (10.1.0)rdoc (4.1.0)semantic_puppet (0.1.2)stomp (1.3.3)test-unit (2.1.9.0)text (1.3.1)win32-dir (0.4.9)win32-eventlog (0.6.2)win32-process (0.7.4)win32-security (0.2.5)win32-service (0.8.8){code}{code:java}C:\Users\Administrator>gem environmentRubyGems Environment: - RUBYGEMS VERSION: 2.4.5.1 - RUBY VERSION: 2.1.9 (2016-03-30 patchlevel 490) [x64-mingw32] - INSTALLATION DIRECTORY: C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0 - RUBY EXECUTABLE: "C:/Program Files/Puppet Labs/Puppet/sys/ruby/bin/ruby.exe" - EXECUTABLE DIRECTORY: C:/Program Files/Puppet Labs/Puppet/sys/ruby/bin - SPEC CACHE
Jira (PUP-7779) Re-implement `puppet facts upload` and associated server endpoint
Title: Message Title Jeff Sparrow commented on PUP-7779 Re: Re-implement `puppet facts upload` and associated server endpoint +1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7153) Puppet fails with inscrutable errors when logging large messages on Windows
Title: Message Title Jeff Sparrow commented on PUP-7153 Re: Puppet fails with inscrutable errors when logging large messages on Windows We are also hitting this error too. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4927) Add logfile option to exec
Title: Message Title Jeff Sparrow commented on PUP-4927 Re: Add logfile option to exec not sure what else this needs? feel free to close this. its been 2 years with no movement. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title Jeff Sparrow commented on FACT-1493 Re: Could not retrieve local facts: failed to parse display name of moniker Sorry. Must have missed the update on it. Have not seen it again, and the path to get there was odd (ps script, as remote user, on a windows install script, etc, etc.) Thanks and my apologies. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title
Jeff Sparrow created an issue
Facter / FACT-1493
Could not retrieve local facts: failed to parse display name of moniker
Issue Type:
Bug
Affects Versions:
FACT 2.4.4
Assignee:
Unassigned
Components:
Windows
Created:
2016/08/23 12:14 PM
Priority:
Normal
Reporter:
Jeff Sparrow
Attempting to run puppet as a remote user on a windows install (so running under SYSTEM). The puppet run starts and I get:
Could not retrieve local facts: failed to parse display name of moniker `winmgmts:{impersonationLevel=impersonate}!//./root/cimv2' HRESULT error code:0x800401e4 Invalid syntax
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title
Jeff Sparrow updated an issue
Facter / FACT-1493
Could not retrieve local facts: failed to parse display name of moniker
Change By:
Jeff Sparrow
Attempting to run puppet , in a powershell script as a remote user , on a windows install script (so running under SYSTEM). The puppet run starts and I get:{code:} Could not retrieve local facts: failed to parse display name of moniker `winmgmts:{impersonationLevel=impersonate}!//./root/cimv2' HRESULT error code:0x800401e4 Invalid syntax{code}Not quite sure where to even begin on this. Any help is appreciated.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6077) puppet commands fail from default users dir on windows 2k8
Title: Message Title Jeff Sparrow assigned an issue to Rob Reynolds Puppet / PUP-6077 puppet commands fail from default users dir on windows 2k8 Change By: Jeff Sparrow Assignee: Jeff Sparrow Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6077) puppet commands fail from default users dir on windows 2k8
Title: Message Title Jeff Sparrow updated an issue Puppet / PUP-6077 puppet commands fail from default users dir on windows 2k8 Change By: Jeff Sparrow Environment: Windows 2k8 High Resolution Date & Time: 3/21/2016 1:19:58.4074604 PMEvent Class: ProcessOperation: Process StartResult: SUCCESSPath: TID: 2272Duration: 0.000Parent PID: 1764Command line: ruby -S -- "Puppet" helpCurrent directory: C:\Users\Administrator\Environment: =::=::\ =C:=C:\Users\Administrator ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\Administrator\AppData\Roaming CLIENTNAME=D1MLQHX1W7 CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=E8G2 ComSpec=C:\Windows\system32\cmd.exe FACTER_DIR=C:\PROGRA~1\PUPPET~1\Puppet\facter FACTER_env_windows_installdir=C:\PROGRA~1\PUPPET~1\Puppet FP_NO_HOST_CHECK=NO HIERA_DIR=C:\PROGRA~1\PUPPET~1\Puppet\hiera HOMEDRIVE=C: HOMEPATH=\Users\Administrator JAVA_HOME=c:\progra~1\java\jdk1.8.0_71 LOCALAPPDATA=C:\Users\Administrator\AppData\Local LOGONSERVER=\\E8G2 MAVEN_HOME=c:\apache-maven-3.3.3 NUMBER_OF_PROCESSORS=4 OS=Windows_NT Path=C:\PROGRA~1\PUPPET~1\Puppet\puppet\bin;C:\PROGRA~1\PUPPET~1\Puppet\facter\bin;C:\PROGRA~1\PUPPET~1\Puppet\hiera\bin;C:\PROGRA~1\PUPPET~1\Puppet\bin;C:\PROGRA~1\PUPPET~1\Puppet\sys\ruby\bin;C:\PROGRA~1\PUPPET~1\Puppet\sys\tools\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\apache-maven-3.3.3\bin;C:\PROGRA~1\PUPPET~1\Puppet\bin PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PL_BASEDIR=C:\PROGRA~1\PUPPET~1\Puppet PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 23 Stepping 6, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=1706 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=$P$G PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public PUPPET_DIR=C:\PROGRA~1\PUPPET~1\Puppet\puppet RUBYLIB=C:/PROGRA~1/PUPPET~1/Puppet/puppet/lib;C:/PROGRA~1/PUPPET~1/Puppet/facter/lib;C:/PROGRA~1/PUPPET~1/Puppet/hiera/lib;; RUBYOPT=rubygems SCRIPT_NAME=Puppet SCRIPT_TEMP=Puppet SESSIONNAME=RDP-Tcp#0 SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\ADMINI~1\AppData\Local\Temp\2 TMP=C:\Users\ADMINI~1\AppData\Local\Temp\2 USERDOMAIN=E8G2 USERNAME=Administrator USERPROFILE=C:\Users\Administrator windir=C:\Windows Add Comment
Jira (PUP-6077) puppet commands fail from default users dir on windows 2k8
Title: Message Title Jeff Sparrow commented on PUP-6077 Re: puppet commands fail from default users dir on windows 2k8 Environment from the command that got passed as a Cap: (the environment from the one with no Caps was identical High Resolution Date & Time: 3/21/2016 1:19:58.4074604 PM Event Class: Process Operation: Process Start Result: SUCCESS Path: TID: 2272 Duration: 0.000 Parent PID: 1764 Command line: ruby -S -- "Puppet" help Current directory: C:\Users\Administrator\
Jira (PUP-6077) puppet commands fail from default users dir on windows 2k8
Title: Message Title Jeff Sparrow commented on PUP-6077 Re: puppet commands fail from default users dir on windows 2k8 thanks. I was sure i checked this earlier as well, but here it is again. I debugged the crap out of this and couldnt figure it out. I am not overly concerned as only one server is doing this. But perhaps wanted to know why. PS. Additional info, in regards to the second image from cmd prompt. If I run the same command in C:\Users\Administrator from powershell prompt, it also works fine. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>where.exe puppet C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat C:\Users\Administrator>cd .. C:\Users>where.exe puppet
Jira (PUP-6077) puppet commands fail from default users dir on windows 2k8
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-6077 puppet commands fail from default users dir on windows 2k8 Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Created: 2016/03/21 11:54 AM Environment: Windows 2k8 High Resolution Date & Time: 3/21/2016 1:19:58.4074604 PM Event Class: Process Operation: Process Start Result: SUCCESS Path: TID: 2272 Duration: 0.000 Parent PID: 1764 Command line: ruby -S – "Puppet" help Current directory: C:\Users\Administrator\ Environment: =::=::\ =C:=C:\Users\Administrator ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\Administrator\AppData\Roaming CLIENTNAME=D1MLQHX1W7 CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files CommonProgramW6432=C:\Program Files\Common Files COMPUTERNAME=E8G2 ComSpec=C:\Windows\system32\cmd.exe FACTER_DIR=C:\PROGRA~1\PUPPET~1\Puppet\facter FACTER_env_windows_installdir=C:\PROGRA~1\PUPPET~1\Puppet FP_NO_HOST_CHECK=NO HIERA_DIR=C:\PROGRA~1\PUPPET~1\Puppet\hiera HOMEDRIVE=C: HOMEPATH=\Users\Administrator JAVA_HOME=c:\progra~1\java\jdk1.8.0_71 LOCALAPPDATA=C:\Users\Administrator\AppData\Local LOGONSERVER=E8G2 MAVEN_HOME=c:\apache-maven-3.3.3 NUMBER_OF_PROCESSORS=4 OS=Windows_NT Path=C:\PROGRA~1\PUPPET~1\Puppet\puppet\bin;C:\PROGRA~1\PUPPET~1\Puppet\facter\bin;C:\PROGRA~1\PUPPET~1\Puppet\hiera\bin;C:\PROGRA~1\PUPPET~1\Puppet\bin;C:\PROGRA~1\PUPPET~1\Puppet\sys\ruby\bin;C:\PROGRA~1\PUPPET~1\Puppet\sys\tools\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\apache-maven-3.3.3\bin;C:\PROGRA~1\PUPPET~1\Puppet\bin PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PL_BASEDIR=C:\PROGRA~1\PUPPET~1\Puppet PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 23 Stepping 6, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=1706 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) ProgramW6432=C:\Program Files PROMPT=$P$G PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public PUPPET_DIR=C:\PROGRA~1\PUPPET~1\Puppet\puppet
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Jeff Sparrow commented on PUP-1431 Re: Pre/Post-run commands don't work under Windows Rakesh Kathpal Did you ever find a work around? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4927) Add logfile option to exec
Title: Message Title
Jeff Sparrow commented on PUP-4927
Re: Add logfile option to exec
Perhaps I dont fully understand puppet with redirect operators. However, as an example, in order to execute commands and send to a log file I have to do funny (or what I think is funny) things. Such as:
exec { qle2xxx driver update:
command = C:\\Windows\\System32\\cmd.exe /c qaucli -fc -d \C:\\ProgramData\\PuppetLabs\\$qle25xx_2k12_driver_file\ C:\\ProgramData\\PuppetLabs\\qaucli_fc.log,
path= $::path,
timeout = 720,
}
or
exec { 'wmi_access_exec':
command = C:\\Windows\\System32\\cmd.exe /c powershell -Executionpolicy Unrestricted -File C:/ProgramData/PuppetLabs/wmi_access.ps1 C:\\ProgramData\\PuppetLabs\\wmi_access.log,
path= $::path,
Jira (PUP-4927) Add logfile option to exec
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-4927 Add logfile option to exec Issue Type: New Feature Assignee: Unassigned Components: Platform Created: 2015/07/27 6:26 AM Environment: Windows Priority: Normal Reporter: Jeff Sparrow It would be very beneficial if puppet had a attribute for the exec parameter to log output to a file. Currently, running a command in windows and redirecting to a file really seems to be it or miss. It required fiddling around with different redirects for cmd, different ones for different versions of powershell, etc. In addition you have to actually call C:\Windows\System32\cmd.exe for puppet to even understand redirects (aside from |). Give windows users a way to handle logging to files without having to monkey around with different path calls, or different redirects in different environments.
Jira (PUP-4333) Puppet package provider on windows fails if non-UTF8 characters are in Uninstall products name value
Title: Message Title Jeff Sparrow commented on PUP-4333 Re: Puppet package provider on windows fails if non-UTF8 characters are in Uninstall products name value Is the work around for this to remove the non ascii characters from the registry? We are about to push out a large build, but we have a handful of servers running in to this issue. We do not have the time or resources to upgrade puppet as we are planning a larger 4.x upgrade soon. Wondering what the best work around is? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4817) Use different method to determine duplicate declarations with windows package
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-4817 Use different method to determine duplicate declarations with windows package Issue Type: Improvement Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/07/06 8:14 AM Environment: Windows Labels: windows package Priority: Normal Reporter: Jeff Sparrow There is a major Catch 22 for Windows packages. Many msi's do not support upgrades. Thus, you have to uninstall the old package and reinstall the new package. However, package resource requires its name to match the Name of the program you are installing. This means that anytime you want to use package resource with windows, you can never use it to uninstall one program and reinstall another of the same name. Yes, you can usually use registry keys, but it makes it much easier to just call out the uninstall of the package name, and let puppet find the registry key and subsequent uninstall command. This means that anyone who wants to uninstall some program and reinstall a newer
Jira (PUP-4085) Windows Agents should report User
Title: Message Title Jeff Sparrow updated an issue Puppet / PUP-4085 Windows Agents should report User Change By: Jeff Sparrow Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4772) Puppet-Labs Reboot
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-4772 Puppet-Labs Reboot Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Components: Modules Created: 2015/06/22 6:01 AM Labels: puppetlabs-reboot reboot Priority: Normal Reporter: Jeff Sparrow I am having issues with the puppet-labs reboot module. I did not see any help/forums/ask sections pertaining to it, and there is no way to create an issue on its git page, so I hope this works. The reboot module does indeed reboot a server as expected. The issue I am running in to is that once the server comes back up, puppet does not finish the rest of the run. I do not see anywhere in the requirements if the reboot module assumes that people have their puppet service set to run on startup. Is it required? How does puppet know where to pick back up after the module does the reboot? There is very little information about this module. Thanks
Jira (PUP-4085) Windows Agents should report User
Title: Message Title Jeff Sparrow updated an issue Puppet / PUP-4085 Windows Agents should report User Change By: Jeff Sparrow Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4085) Windows Agents should report User
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-4085 Windows Agents should report User Issue Type: New Feature Affects Versions: PUP 3.7.3 Assignee: Unassigned Components: Platform, Windows Created: 2015/03/05 4:14 AM Environment: Windows Priority: Normal Reporter: Jeff Sparrow We had some puppet agents run unexpectedly. I was tasked with trying to figure out if the system clock had changed, thus kicking them off, or if someone had manually ran them. However, we discovered that puppet does not report to event viewer the name of the user under which puppet is running. It would be beneficial if puppet reported the user (SYSTEM/Local) that puppet is running under.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class I have grepped everywhere for the phrase and searched everywhere for that dir/file. I cant seem to find it. Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class Should I essentially just replace everything that says Win32::Service::Error with SystemCallError? Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class I am an idiot.. I was looking on server side this whole time.. lol. Replacing now. What about the additional file that was committed on git? Do I need to worry about that? Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... 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-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class Error: Cannot start mcollectived, error was: Execution of 'C:/Windows/system32/net.exe start mcollectived' returned 2: System error 2 has occurred. The system cannot find the file specified. Wrapped exception: Execution of 'C:/Windows/system32/net.exe start mcollectived' returned 2: System error 2 has occurred. The system cannot find the file specified. Error: /Stage[main]/Windows_mcollective/Service[mcollectived]/ensure: change from stopped to running failed: Cannot start mcollectived, error was: Execution of 'C:/Windows/system32/net.exe start mcollectived' returned 2: System error 2 has occurred. The system cannot find the file specified. After changing: - rescue Win32::Service::Error = detail + rescue SystemCallError = detail Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-...
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class I am very new to Puppet (3-4 weeks at most). Looks like you guys are using jira, are you saying to create a new bug issue in jira, with MCO as the project? Sorry for any confusion on my part. Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... 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
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class I should note the mcollective service was installed. Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class You are completely right. I am not sure how I missed this: Originally I thought it was because I had removed ruby from path, thus it didnt know what to do, but even when running it from ruby, it is not installed: `C:\Program Files\Puppet Labs\Puppet\sys\ruby\binc:\marionette-collective\bin\register_service.bat Service mcollectived installed` Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... 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
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class Found out we arent going live until later tomorrow afternoon. So I can test that in the morning. I will report back. Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
