Puppet Community

Ah, I see... Not good for us. But thanks for verification. :slightly_smiling_face:

you can probably provide a patch for this

Well, the lvm module is not safe to use any more, I think, since device files are dynamic nowadays and that raises errors at best. But this is a legacy manifest that we have to deal with somehow. Probably have to comment it out, and only use puppet for mounting lv's.

I wonder, why is a puppet notice message in a manifest, which doesn't change anything, regarded as an "intentional change"? Any sound reason for this?

See the `ipcrm-echo` module at <https://forge.puppet.com/ipcrm/echo?src=slack&amp;channel=office-hours>

I guess with notice it was intentional :sunglasses:

Ah, I meant "notify", "notice" is the default log level shown in the log.

Thank for tip about "echo". We try to only use modules supported by Puppet since we've been burned many times by using modules that suddenly goes unmaintained. So, I may not be allowed to use it due to our "once bitten twice shy" policy. :slightly_smiling_face:

Still the functionality of "echo" is just what I was looking for, so I wish Puppet would "adopt" the module and support it. :slightly_smiling_face:

Well, it "changes" the pixels on screen if output there, but that's about it... :slightly_smiling_face: Really weird behaviour in my view.

While that behavior may have been intended it is regardless basically a requirement of the way the Puppet resource transaction system works - to get it to the point it will emit a message you need to indicate the resource is "out of sync".  Once you do, then Puppet treats it as a changed resource.  The message is then emitted in the "run this to bring it in sync" bit.

The ipcrm/echo module cleverly "cheats" a bit by instead emitting the message during the stage of the transaction where the state is evaluated (and for which it always returns "in sync").

Sometimes I want the notify behavior, sometimes I want the echo behavior, and sometimes I just want a silent note in the catalog I can search for with `puppet query`.  I've long thought about creating a new module with a single logging resource that handles all the scenarios, but I never seem to get around to it.

:businessparrot: _:teacher:PE Console_ is about to start up in 15 minutes

\o Good day y’all - console office hour has begun!

If you have any questions/suggestions for anything related to the console, any of the console services (RBAC, Classifier, Activity Service) or the Orchestrator, ask away.

:the_more_you_know: Next up is _Modules Team_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20241105T113000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|109 hours>

OK, that’s a wrap for today - we’ll be back in a couple of weeks. Y’all be good to yourselves!

:businessparrot: _Modules Team_ is about to start up in -15 minutes

:fry_dancing: Next up is _:teacher:Puppet Core Team_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20241107T180000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|53 hours>

:beaker: _:teacher:Puppet Core Team_ is about to start up in 15 minutes

Hi folks, office hours are open for the next hour

it seems DNF maintainers don't care for "machine parsing" they deprecated `-d` and `-e` switches in dnf4 and removed them in dnf5, so that provider is broken now

unless there is some "low" level utility you suppose to use?

yeah, that's <https://github.com/puppetlabs/puppet/issues/9506> The dnf provider inherits from the rpm one <https://github.com/puppetlabs/puppet/blob/4ea6ee241d5e5ac504b7aec80417a02e923ce303/lib/puppet/provider/package/dnf.rb#L3> And there's the `dnfmodule` provider too

<https://github.com/rpm-software-management/dnf5/issues/867>

Maybe as puppet maintainer you can influence them better  ?

No XML, despite the PR for it. :smile:
<https://github.com/rpm-software-management/dnf5/pull/1524>

and seems added that for a limited set of commands

<@U2S1MUUQ7> sorry I'm confused by the dnf5 issue you linked. Are you saying puppet will need to parsing dnf5 output as json (as soon as we replace `-e` and `-d` with something else)? Or just that we should migrate to parsing JSON in the future?

I hope Puppet can influence dnf folks to provide json output for dnf commands it uses