https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • r
    Yeah that didn't seem to help
  • s
    Can you just pass 
    -y
    as an extra yum command line option?
  • r
    No, the rpm for mssql-tools doesn't care about that
  • r
    it specfically either wants you to answer the "Do you accept the EULA?" or have the ACCEPT_EULA variable passed ahead of time
  • s
    Of course, it's MS... why would they follow convention...
    😩 1
  • r
    Right?!
  • s
    I guess your other option would be to set ACCEPT_EULA in root's environment, so it is always there?
  • r
    Hadn't thought about that... trying this...
    Copy code
    wl_linux_base::pre_patch_commands:
  - "rpm -qa | grep msodbcsql17 && ACCEPT_EULA=y yum update msodbcsql17 -y"
  • r
    That adds a line to our default pre patch script
  • g
    I wonder, is there any reason why one is allowed to add the same server twice to the same node group? Is there a use case for this? If not, how can it be a sanity control like that is not in place after years and year of use by millions of customers?
    b
    s
    s
    • 4
    • 17
  • k
    One thing we use node groups for is querying the classifier for a node list, and using that result to generate lists of nodes for Splunk classification. But IMO this is backwards, we should be using Puppet to drive the Splunk configuration directly (it was set up this way before I started working here). I've been trying to find time for years to migrate us from jorritfolmer-splunk to puppet-splunk, which I think would allow for this.
    b
    • 2
    • 3
  • d
  • b
    @csharpsteen PE has puppet_enterprise:masterpuppetserver:settings_ catalog for "Experimental setting to potentially improve Puppet Server startup time". Does it have known issues? (I was wondering why it's experimental)
    c
    • 2
    • 8
  • t
    I recently updated puppet and noticed that I am getting warnings about the SSL Certificate size. Is there way to set this to a larger number ?
    Copy code
    puppet -tv 
-----END CERTIFICATE-----' with the value length: '6965' exceeds the value length limit: 4096
    b
    c
    • 3
    • 5
  • h
    The release notes for PE 2021.7.9 say that Legacy facts have been removed. Is there a way to turn them back on?
  • c
    there is, but it's not recommended. Changing your existing codebase to leverage the facts hash is a better idea
  • h
    and we are certainly working toward that, but workloads being what they are, we were targetting that work to be done for the upgrade to PE 2023
  • c
  • c
    Copy code
    If you need to keep legacy facts in your code, they can be re-enabled by setting include_legacy_facts=true in puppet.conf on each agent.
  • h
    PE2021.7.9 is puppet 7 based
  • c
    so, you have a line of code or so to put in your puppet management
  • c
    2021.7 is not listed in the version matrix on the website. ¯\_(ツ)_/¯
  • c
    found it. It's out of order rolleyes
  • h
    the release notes for 2021.7.9 has
    Copy code
    Legacy facts disabled while running 2021.7.x (maintenance) to help improve user's upgrade testing
    While there are other methods available to test if your code base is Puppet 8 compatible, disabling legacy facts in Puppet Enterprise ensures there's no issues/blockers. This process is not possible in earlier versions of PE 2021.7.x because legacy facts is still used. Legacy facts has been removed in version PE 2021.7.9.
    so I assumed it was server side (which is managed by others). What was actually changed to disable legacy facts in PE 2021.7.9?
  • b
    legacy facts are still enabled in PE 2021
  • c
    I'm likely going out on a limb here, but I'm betting 7.32.1 version would be applicable
  • b
    the 
    puppet infra
    command used some legacy facts in PE 2021. that was switched to modern facts so it doesn't break when you disable legacy facts on your own. that's all
  • h
    the wording on the release notes is panic inducing https://www.puppet.com/docs/pe/2021.7/release_notes_pe#release_notes_pe
  • b
    it's not optimal, yes
  • b
    but facts for your normal puppet agent <> server interaction are always controlled by the agent, not the server
1...686970...73Latest