https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • s
    This message was deleted.
    t
    r
    d
    • 4
    • 3
  • s
    This message was deleted.
    d
    • 2
    • 1
  • r
    It appears that I've inadvertently skipped this step in previous upgrades, so I'm not sure how important it actually is.
  • b
    Good Afternoon all
  • b
    On WIN 2012 we are getting an error: SchUseStrongCrypto -Value '1' -Type Word returned -1 instead of 1
  • b
    Also getting EOF error Broken Pipe
  • b
    I assume they are related
  • b
    (Can't do a full copy and paste)
  • b
    Anyone have any suggestions?
  • b
    Copy code
    C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:325:in `sysread': end of file reached (EOFError) 
Error: 'Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord' returned -1 instead of o 
ne of [0] 
Error: /Stage[main]/Plaat_staging::Windows::Install/Exec[Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' 
-Value '1' -Type DWord]/returns: change from 'notrun' to ['0'] failed: 'Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'Sch 
UseStrongCrypto' -Value '1' -Type DWord' returned -1 instead of one of [0] (corrective)
  • b
    Copy code
    #<Thread:0x0000000007e48cc8@C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:321 run> terminated with exception (report_on_exception
is true):
C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:204:in `is_readable?'
:
Broken pipe (
Errno::EPIPE
)
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:308:in `drain_pipe_until_signaled'
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:321:in `block in read_streams'
#<Thread:0x0000000007e48b88@C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:322 run> terminated with exception (report_on_exception
is true):
C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:204:in `is_readable?'
:
Broken pip
e
(Errno::EPIPE
)
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:308:in `drain_pipe_until_signaled'
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:322:in `block in read_streams'
#<Thread:0x0000000007e3b190@C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:323 run> terminated with exception (report_on_exception
is true):
C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:325:in `sysread': end of file reached (EOFError
)
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:325:in `block in read_streams'
#<Thread:0x0000000007e3b4b0@C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:321 run> terminated with exception (report_on_exception
is true):
C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:204:in `is_readable?': Broken pipe (
Errno::EPIPE
)
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:308:in `drain_pipe_until_signaled'
                from C:/ProgramData/PuppetLabs/puppet/cache/lib/puppet_x/puppetlabs/powershell/powershell_manager.rb:321:in `block in read_streams'
  • h
    at first glance, it looks like the powershell tried to run Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord' and failed. I'd verify that this particular registry key can be set to 1.
    đź‘Ť 1
  • h
    at first glance, it looks like the powershell tried to run Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord' and failed. I'd verify that this particular registry key can be set to 1.
  • d
    To confirm the issue is it's a manual process via our google suite system and with the changes in marketing/product personal and us changing to o365 in general if im overly honest I think this has just been missed in error. We're discussing how to do this in future. Sorry for the inconvenience.
  • b
    Hi people, we created a bunch of tickets in the ENTERPRISE jira ticket, but the response rate is quite (s)low. Is that board currently triaged/reviewed on a regular basis?
  • s
    This message was deleted.
    j
    • 2
    • 1
  • s
    This message was deleted.
    đź‘Ť 1
    d
    k
    r
    • 4
    • 9
  • r
    where can/should i find the agent repos for airgapped installation for sts 2023.0.0 (the tar.gz repo)? for LTS i can find it in "previous versions" download page f.e. https://www.puppet.com/releases/2021.7.2). but for 2023.0.0 is nothing there (https://www.puppet.com/releases), and also not on the main download page of PE and also not when i edit the url like https://www.puppet.com/releases/2023.0.0
  • j
    The classifier maintains its own cache of classes, and if a node-group references a class that is deleted, that is maintained in the cache in a “deleted” state so we can show it in the UI as being removed (so there isn’t any mystery as to why the class suddenly disappeared). That “deleted” state is what I think was causing that behavior.
  • d
    PEADM is now at 3.11 supporting installation and management of Puppet Enterprise LTS release 2021.7.2 and latest STS 2023.0.0 https://forge.puppet.com/modules/puppetlabs/peadm/readme
    đź‘Ť 3
  • s
    This message was deleted.
    d
    b
    • 3
    • 8
  • d
    do you mean if it is allready a PEADM cluster or if it thinks it would be possible to run a covert to make a PEADM cluster
  • d
    so https://github.com/puppetlabs/puppetlabs-peadm/blob/main/tasks/get_peadm_config.json might go some of the way to return what it knows is setup
  • k
    I will need these too. Used to be at https://puppet.com/misc/pe-files/pe_repo
  • b
    Good morning people. I would like to use 
    lookup()
    outside of an apply block, with PE plans. The hiera.yaml is at the global layer, 
    /etc/puppetlabs/puppet/hiera.yaml
    and not at the project/environment layer. Is this supported? It works fine for puppet agent runs. But I'm not able to configure that for plan runs with the plan_hierarchy. But maybe the paths to the files are just wrong? • Is there an option to debug/see the loaded hiera.yaml in a plan? • Is a global hiera.yaml supported for plan runs? • Is something like 
    %{::environment}
    supported within hiera.yaml? Slack Conversation
  • s
    This message was deleted.
    b
    r
    c
    • 4
    • 16
  • b
    for huge eyaml blobs I now prefer hashicorp vault, for example
  • s
    This message was deleted.
    b
    z
    +2
    • 5
    • 40
  • z
    Hello all. Does anyone happen to use https://github.com/petems/petems-hiera_vault for the latest version of hiera? Any suggestions to integrate easily Puppet with hashicorp vault for pulling secrets?
  • z
    Hello all. Does anyone happen to use https://github.com/petems/petems-hiera_vault for the latest version of hiera? Any suggestions to easily integrate Puppet with hashicorp vault for pulling secrets?
1...353637...73Latest