Re: [Puppet Users] Puppet VM Extension is Missing in Azure
Hi Michael -
Sorry for the inconvenience. We recently marked the agent extension
handlers as internal, as we realize we haven't been updating them, none of
the versions in Azure are supported any longer, and as such their use poses
a security risk. We were also unable to track down more than a couple of
actual users (Microsoft doesn't provide us with any install data), and
weren't aware that marking the installer as internal could pose problems
for existing VMs with the extension installed.
The most recent agents published, Puppet / PupppetAgent 1.5.2 and
PuppetLabs / PuppetEnterpriseAgent 2016.1.2 are both agents from the Puppet
4 series. The Puppet 4 agent went EOL in October of 2018 -
https://ask.puppet.com/question/33472/puppet-4-open-source-end-of-life-eol/.
We have some additional information for PE support lifecycles at
https://puppet.com/docs/puppet-enterprise/product-support-lifecycle/
We recommend that users migrate to using the PE package management support
in their masters to bootstrap agent installs as described in
https://puppet.com/docs/pe/2019.3/installing_agents.html#install_windows_agents_with_pe_package_management
Thanks!
On Tue, Feb 4, 2020 at 11:14 PM michael mack wrote:
> Is there any reason why the puppet-agent VM extension has been removed in
> Azure? The last time, it work for me was 1/16/2020.
>
> Command to get VM extension
>
> Get-AzVmImagePublisher -Location "WestUS2" | Where-Object{$_.PublisherName
> -match 'puppetlabs.test'} | `
> Get-AzVMExtensionImageType | `
> Get-AzVMExtensionImage | Select Type, Version
>
> Bootsrap Error message
> {
> "code": "DeploymentFailed",
> "message":
> "At least one resource deployment operation failed. Please list deployment
> operations for details. Please see
> https://aka.ms/DeployOperations for usage details.",
> "details": [
> {
> "code": "NotFound",
> "message":
> "{\r\n \"error\": {\r\n\"code\": \"ArtifactNotFound\",\r\n
> \"message\": \"Extension with publisher 'Puppet', type 'PuppetAgent', and
> type handler version '1.5' could not be found in the extension
> repository.\"\r\n }\r\n}"
> }
> ]
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/583ecc84-348f-43ea-a261-fc0c6924f550%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/583ecc84-348f-43ea-a261-fc0c6924f550%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
*Ethan Brown*
Principal Engineer
et...@puppet.com | @ethanjbrown <https://twitter.com/ethanjbrown>
--
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CALCHMcQZ5_2Lf1Nvvvr7BZ4RSfa_26PvYrwTyGLiSHchoy6M%3DQ%40mail.gmail.com.
Re: [Puppet Users] PDK 1.0.0.1 on Windows
On Thu, Aug 17, 2017 at 6:32 AM, David Schmitt wrote: > > > On 17 August 2017 at 12:11, Peter Faller wrote: > >> Hi David >> >> Thanks for pointing out 'pdk bundle' - it does provide what I was looking >> for. It is however a bit noisy (but that's not a big deal): >> >> PS> pdk bundle exec -- rspec .\spec\classes\apg_base_spec.rb >> . >> >> Finished in 7.81 seconds (files took 1.85 seconds to load) >> 1 example, 0 failures >> >> C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/puppet-5.0.1-x64-mingw32/lib/puppet/util/windows >> /api_types.rb:6: warning: already initialized constant FFI::WIN32_FALSE >> C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/facter-2.5.0-x64-mingw32/lib/facter/util/windows >> /api_types.rb:5: warning: previous definition of WIN32_FALSE was here >> C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/puppet-5.0.1-x64-mingw32/lib/puppet/util/windows >> /api_types.rb:9: warning: already initialized constant FFI::ERROR_SUCCESS >> C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/facter-2.5.0-x64-mingw32/lib/facter/util/windows >> /api_types.rb:8: warning: previous definition of ERROR_SUCCESS was here >> C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/puppet-5.0.1-x64-mingw32/lib/puppet/util/windows >> /api_types.rb:21: warning: already initialized constant >> FFI::Pointer::NULL_HANDLE >> C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/facter-2.5.0-x64-mingw32/lib/facter/util/windows >> /api_types.rb:20: warning: previous definition of NULL_HANDLE was here >> !! spec/fixtures/modules/rimcdm already exists and is not a symlink >> > > This is now tracked in https://tickets.puppetlabs.com/browse/FACT-1733, > but the underlying problem is https://tickets.puppetlabs. > com/browse/FACT-1542 , which will require some time to resolve. > FACT-1729 <https://tickets.puppetlabs.com/browse/FACT-1729> has been merged which addresses the constant redefinition issue, and is pending release next week in Facter 2.5.1. > > >> The things that I use 'rake' and 'rspec' for are: >> >> > rspec spec/classes/some_class_spec.rb # to run a single unit test >> instead of all tests >> > > Eventually <https://tickets.puppetlabs.com/browse/PDK-429>, `pdk test > unit` will properly expose rspec's selector CLI. > > > > rake spec_prep # to update fixtures >> > rake spec_standalone # to run tests without updating fixtures >> >> I'm working on refactoring an over-sized module; that's why being able to >> do quick tests is important to me. >> > > > >> >> I'm using the version of rspec-puppet bundled with the PDK - it appears >> to be version 2.6.7: >> >> PS> pdk bundle exec -- rspec --debug >> ... >> # C:/Program Files/Puppet Labs/DevelopmentKit/share/cach >> e/ruby/2.1.0/gems/rspec-puppet-2.6.7/lib/rspec-puppet/monkey_patches.rb:273:in >> `require' >> ... >> > > > That's interesting. In the scientific sense. Is there a way you could > share the module, or a reduced example that repro's the issue? > > > > Cheers, David > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/puppet-users/CALF7fHYmecRp5ZcYAfiAZZXJZZsi3 > dr9YjdMSFJQJga5GnX0mg%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-users/CALF7fHYmecRp5ZcYAfiAZZXJZZsi3dr9YjdMSFJQJga5GnX0mg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- *Ethan Brown* Principal Engineer et...@puppet.com | @ethanjbrown <https://twitter.com/ethanjbrown> -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CALCHMcRzytrwtFrNjke_ApS%3Dq8KV0Oa3ZecUTz%3D4NoNDc1hgJg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Announce: Ruby 2.3 update planned for puppet-agent 1.6.0
On Monday, August 8, 2016 at 8:30:27 PM UTC-7, Garrett Honeycutt wrote: > > On 8/5/16 9:12 PM, Geoff Nichols wrote: > > > > > > On Friday, July 29, 2016 at 5:00:26 PM UTC-7, Geoff Nichols wrote: > > > > Because Ruby 2.1 is approaching end-of-life (upstream bugfix support > > ended March 2016), we need to move puppet-agent to a more modern > > Ruby version. > > > > > > If all goes well with testing, the upcoming puppet-agent 1.6.0 > > release will include Ruby 2.3.1. > > > > > > As an update, we found some issues during testing, so puppet-agent 1.6.0 > > will NOT include Ruby 2.3.1. > > > > We're now targeting the Ruby 2.3 update for a later puppet-agent > > release. (We'll share more information about that timeframe as the plan > > firms up.) > > > > Thanks, > > Geoff > > > > Hi Geoff, > > It seems that the testing is leaving out the huge dataset of modules > from the Forge. Checked out the TravisCI configs for a couple of the top > supported modules including stdlib, apache, ntp, apt and vcsrepo and > none of them are testing with ruby 2.3. Suggest that before moving to a > new version of ruby, the TravisCI configs for all supported modules > should be explicitly testing against the new ruby version to ensure it > works. > We have tested on some Windows modules with success. Generally speaking, I believe we're more likely to see issues in modules that have Ruby type and provider code than we are in modules that are primarily manifest driven. That said, I totally agree we should get module testing changes rolled out officially ASAP. For the Windows modules, we'll plan on getting all the Travis / AppVeyor updates in place over the next few days. Contact has been made with the owners of the other modules to do the same. I did identify some issues in core Puppet around module loading on Windows, thanks to Ruby changing the behavior of Dir.glob when given 8.3 style paths - that ticket is at https://tickets.puppetlabs.com/browse/PUP-6557 / PR is at https://github.com/puppetlabs/puppet/pull/5156 and should be merged shortly. Thanks! Ethan J. Brown Tech Lead, Windows Engineering -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/056d604d-6311-4948-8e14-ef305086a03a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Puppet 3.7.5 Windows Releases Being Recalled
It was recently discovered that the following open source Puppet 3.7.5 releases on Windows from March 26, 2015 were mistakenly shipped with Ruby 2.1.6: puppet-3.7.5.msi puppet-3.7.5-x64.msi Given compatibility against Ruby 2.1 is not tested until Puppet 4 series releases, we are removing the 2 releases above from downloads.puppetlabs.com, effective immediately. Puppet Enterprise releases are not affected. We suggest that users downgrade to Puppet 3.7.4 or upgrade to Puppet 3.8.1, which both include the appropriate Windows Ruby versions, namely Ruby 1.9.3 for x86 and Ruby 2.0.0 for x64. We are evaluating the viability of a subsequent Windows 3.7.6 release. Puppet 3.7.4 x64 - https://downloads.puppetlabs.com/windows/puppet-3.7.4-x64.msi Puppet 3.7.4 x86 - https://downloads.puppetlabs.com/windows/puppet-3.7.4.msi Puppet 3.8.1 x64 - https://downloads.puppetlabs.com/windows/puppet-3.8.1-x64.msi Puppet 3.8.1 x86 - https://downloads.puppetlabs.com/windows/puppet-3.8.1.msi -- Ethan J. Brown Tech Lead, Windows + Cloud -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CALCHMcQSPWJxby2ZZu1gs6JATuN9jmHgpTsw6NuO_m%3DzeNQ6Pg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers
Christian - Thanks a bunch for taking the time out to verify this. While we believed our fix was correct, I was trying to replicate your network configuration internally to be absolutely certain. I was having difficulty getting the virtual machines configured properly with respect to the 'Microsoft Failover Cluster Virtual Adapter', so it's fantastic to hear that you were able to verify this directly in your environment. On Fri, Oct 4, 2013 at 6:00 AM, Christian Koep wrote: > Hi Rob, > i just applied the changes to the windows.rb file. > > The catalog run finished as usual. Thank you ;-) > > > > On Thu, Oct 3, 2013 at 8:47 PM, Rob Reynolds wrote: > >> This verifies for us that this is a gating issue. >> >> Would you feel comfortable helping us verify that we've fixed this issue >> for you? >> >> >> https://github.com/ferventcoder/facter/blob/874a5a96ac5fa778c50f1e93424850022b1756cf/lib/facter/util/ip/windows.rb#L46-L47 >> >> >> >> >> On Thu, Oct 3, 2013 at 1:42 PM, Christian Koep wrote: >> >>> Yes, thats all i got from *facter --trace --debug* >>> >>> >>> On Thu, Oct 3, 2013 at 8:41 PM, Rob Reynolds wrote: >>> >>>> Was this the entire log (minus anything you feel sensitive)? >>>> >>>> >>>> On Thu, Oct 3, 2013 at 1:15 PM, cko wrote: >>>> >>>>> https://gist.github.com/anonymous/6814400 >>>>> >>>>> >>>>> On Thursday, October 3, 2013 5:23:05 PM UTC+2, Rob Reynolds wrote: >>>>> >>>>>> You should be able to run >>>>>> >>>>>> facter --trace --debug >>>>>> >>>>>> >>>>>> On Wed, Oct 2, 2013 at 5:18 PM, cko wrote: >>>>>> >>>>>>> Hi Ethan, >>>>>>> >>>>>>> what's the exact command that i would have to use? >>>>>>> >>>>>>> >>>>>>> On Wednesday, October 2, 2013 11:35:29 PM UTC+2, Ethan Brown wrote: >>>>>>> >>>>>>>> Christian - >>>>>>>> >>>>>>>> I'm doing the final verification of our fix, and was hoping that I >>>>>>>> could get the output from Facter run by itself? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I would say with all of this in mind we move forward with a fix >>>>>>>>> where we look to see that the network adapter itself is also enabled. >>>>>>>>> This >>>>>>>>> is laid out in the ticket that I noted earlier. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel wrote: >>>>>>>>> >>>>>>>>>> Exchange DAG is essentially a cluster and the adapter in >>>>>>>>>> question the dag ip. >>>>>>>>>> >>>>>>>>>> My guess is the logic for adapters should be modded for when >>>>>>>>>> netconnectionid is not null. >>>>>>>>>> >>>>>>>>>> In general don't try to mess with hidden adapters on dags unless >>>>>>>>>> you understand ramifications. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>> Google Groups "Puppet Users" group. >>>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>>> send an email to puppet-users...@**googlegroups.**com. >>>>>>>>>> To post to this group, send email to puppet...@googlegroups.com. >>>>>>>>>> >>>>>>>>>> Visit this group at http://groups.google.com/**group** >>>>>>>>>> /puppet-users <http://groups.google.com/group/puppet-users>. >>>>>>>>>> For more options, visit https://groups.google.com/**grou** >>>>>>>>>> ps/opt_out <https://groups.google.co
Re: [Puppet Users] Re: [windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers
Christian - I'm doing the final verification of our fix, and was hoping that I could get the output from Facter run by itself? On Fri, Sep 20, 2013 at 1:36 PM, Rob Reynolds wrote: > I would say with all of this in mind we move forward with a fix where we > look to see that the network adapter itself is also enabled. This is laid > out in the ticket that I noted earlier. > > > On Fri, Sep 20, 2013 at 7:44 AM, Rich Siegel wrote: > >> Exchange DAG is essentially a cluster and the adapter in question the dag >> ip. >> >> My guess is the logic for adapters should be modded for when >> netconnectionid is not null. >> >> In general don't try to mess with hidden adapters on dags unless you >> understand ramifications. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscr...@googlegroups.com. >> To post to this group, send email to puppet-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/puppet-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Rob Reynolds > Developer, Puppet Labs > > Join us at PuppetConf 2014, September 23-24 in San Francisco > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- Ethan Brown et...@puppetlabs.com Software Engineer *Join us at PuppetConf 2014, September 23-24 in San Francisco* -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
