Bug 2276045 - puppet packages are outdated
Summary: puppet packages are outdated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: puppet
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Breno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-19 10:39 UTC by Han Boetes
Modified: 2024-04-29 02:23 UTC (History)
4 users (show)

Fixed In Version: puppet-8.3.1-1.fc38
Clone Of:
Environment:
Last Closed: 2024-04-29 02:23:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Han Boetes 2024-04-19 10:39:26 UTC
Description of problem:

Package version is outdated

Please refer to https://github.com/puppetlabs/puppet/issues/9320 for a detailed bug description.

If the puppet packages were kept up-to-date, I wouldn't run into this problem. Please also keep the puppet version for other releases up-to-date.

Thanks!

Comment 1 Fedora Update System 2024-04-20 05:45:53 UTC
FEDORA-2024-53eef902c8 (puppet-8.3.1-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-53eef902c8

Comment 2 Breno 2024-04-20 05:47:09 UTC
We are matching F38 with F39's version. Rawhide should get the latest soon.

Comment 3 Han Boetes 2024-04-20 07:44:59 UTC
How on earth can you claim that replacing one broken version with another broken version is fixing a problem? Why don't you install the latest version? All that is added to the original packages are bug fixes.

Comment 4 Breno 2024-04-20 12:30:27 UTC
"How on earth" ?

You should review your manners, don't talk to me like that, especially considering this is not a paid system, you are talking to volunteers.

We are bumping Fedora 38 which goes to End Of Life in a couple of weeks from Puppet 7.27 to Puppet 8.3. You can also place a PR requesting any version bumps, this is open-source.

Finally, Fedora rawhide/40 is taking Puppet 8.6.0 https://bugzilla.redhat.com/show_bug.cgi?id=2274550.

Comment 5 Han Boetes 2024-04-20 13:45:44 UTC
Puppet 7.27 is quite stable, I recommend you don't replace the stable version for fc38, since they removed the long deprecated legacy facts, the upgrade from 7 to 8 will cause mayor problems for the unprepared.

I do recommend you track updates for puppet 8 for the foreseeing time for 39 & 40

Do consider getting information from theforeman developers like ekohl, who can confirm what I just said, or better yet, hand over maintainership to someone from the foreman team.

Comment 6 Breno 2024-04-20 15:08:05 UTC
Hey Han,

I understand your concern, and you're probably right.
Now taking a second look at the link you initially posted, I understand where you're coming from.

When I saw this ticket yesterday my first impression was more of a major bump, so I tailgated on the closest major which came from Fedora 39. And I was fine with it since 38 is going end of life in a few weeks. We can review that.

As I said rawhide is now on the latest. If you can test it out and let us know how it goes, we can downstream it to 40 and maybe 39.

What do you think?

Now, regarding your suggestions, I understand you just arrived and may not have the full picture.

I took the ownership of this package years ago, after asking the puppet folks several times to handle it. They were not interested. Back then EL7 had puppet 3, and fedora an unsupported puppet 5. Puppet back then didn't share the spec files, only the built packages. I had to figure out everything myself. And this is a short summary of the drama.

I'm saying all that so you keep in mind we, as we volunteers, try our best to deliver good software to the community. Please have that in mind. Have a little patience, mistakes will be made, and they can be fixed if we all cooperate and work together.

That being said, I recently offered Ekohl the ownership of this package, due to some of lack of my time, and personal matters. That's in progress. A coincidence or not, before you cite him, I had emailed him asking for his opinion on this.

- Breno

Comment 7 Han Boetes 2024-04-22 08:32:13 UTC
Hello Breno,

Please don't take it personally. I was frustrated by the unsolvable problem I was facing for quite some time now. Mea Culpa.

What I also posted in the github ticket:

I just manually build a puppet-8.6.0 package for fedora-40, copied from rawhide and that also doesn't fix the issue, even though it's using ruby-3.3.0

Which according to Josh Cooper is caused by a problem with a ruby library:
https://github.com/puppetlabs/puppet/issues/9320#issuecomment-2057725864


```
root@habocp3 ~ #  puppet apply -e 'user { "foo01": password => Sensitive("bah") }'
/usr/share/ruby/vendor_ruby/augeas.rb:48: warning: undefining the allocator of T_DATA class Augeas
Notice: Compiled catalog for habocp3.axis-flight-training-systems.at in environment production in 0.01 seconds
Warning: /User[foo01]: Unable to mark 'password' as sensitive: the property itself was not assigned a value.
Notice: Applied catalog in 0.08 seconds
root@habocp3 ~ #  rpm -qa G puppet
rubygem-semantic_puppet-1.1.0-2.fc40.noarch
rubygem-puppet-resource_api-1.8.18-2.fc40.noarch
puppet-8.6.0-1.fc40.noarch

root@habocp3 ~ #  rpm -qa G ruby  
ruby-libs-3.3.0-4.fc40.x86_64
rubypick-1.1.1-20.fc40.noarch
ruby-3.3.0-4.fc40.x86_64
ruby-default-gems-3.3.0-4.fc40.noarch
rubygem-io-console-0.7.1-4.fc40.x86_64
rubygem-json-2.7.1-203.fc40.x86_64
rubygem-psych-5.1.2-4.fc40.x86_64
rubygem-rdoc-6.6.2-4.fc40.noarch
rubygems-3.5.3-4.fc40.noarch
rubygem-bcrypt_pbkdf-1.1.0-11.fc40.x86_64
rubygem-ed25519-1.3.0-7.fc40.x86_64
rubygem-net-ssh-7.1.0-3.fc40.noarch
rubygem-net-scp-4.0.0-4.fc40.noarch
rubygem-net-sftp-4.0.0-3.fc40.noarch
rubygem-childprocess-4.1.0-8.fc40.noarch
rubygem-concurrent-ruby-1.1.9-6.fc40.noarch
rubygem-i18n-1.14.1-5.fc40.noarch
rubygem-erubi-1.12.0-1.fc40.noarch
rubygem-ffi-1.15.5-10.fc40.x86_64
rubygem-rb-inotify-0.10.1-9.fc40.noarch
rubygem-listen-3.7.1-5.fc40.noarch
rubygem-hashicorp-checkpoint-0.1.5-14.fc40.noarch
rubygem-irb-1.11.0-4.fc40.noarch
ruby-bundled-gems-3.3.0-4.fc40.x86_64
rubygem-log4r-1.1.10-22.fc40.noarch
rubygem-mime-types-data-3.2023.0218.1-3.fc40.noarch
rubygem-mime-types-3.4.1-4.fc40.noarch
rubygem-rexml-3.2.6-4.fc40.noarch
rubygem-rubyzip-2.3.2-8.fc40.noarch
rubygem-thor-1.2.1-6.fc40.noarch
rubygem-sys-filesystem-1.4.3-4.fc40.noarch
rubygem-hocon-1.4.0-4.fc40.noarch
ruby-devel-3.3.0-4.fc40.x86_64
rubygem-semantic_puppet-1.1.0-2.fc40.noarch
rubygem-scanf-1.0.0-5.fc40.noarch
rubygem-racc-1.7.3-202.fc40.x86_64
rubygem-multi_json-1.15.0-9.fc40.noarch
rubygem-deep_merge-1.2.2-7.fc40.noarch
ruby-augeas-0.5.0-38.fc40.x86_64
libselinux-ruby-3.6-4.fc40.x86_64
rubygem-puppet-resource_api-1.8.18-2.fc40.noarch

```

Comment 8 Ewoud Kohl van Wijngaarden 2024-04-23 11:27:14 UTC
Hello Han,

I'm glad you realized your tone wasn't appropriate. It's a good way to burn out maintainers, which leads to even more workload on existing maintainers. A very negative spiral we don't want to enter.

A more constructive way would be to add more testing. We have some very basic tests in place:

https://src.fedoraproject.org/rpms/puppet/blob/rawhide/f/tests/smoke/test.sh

Our gating tells bodhi that it's mandatory to pass:

https://src.fedoraproject.org/rpms/puppet/blob/rawhide/f/gating.yaml

This means we can't ship a completely broken package. Now the test suite is very minimal and doesn't cover your use case, so you could add that.

As for the augeas warning, I think think we should apply more patches. I opened these upstream:
* https://github.com/hercules-team/ruby-augeas/pull/14
* https://github.com/hercules-team/ruby-augeas/pull/17

The latter one is also in Fedora (https://src.fedoraproject.org/rpms/ruby-augeas/c/5b630333cfd83a1e26bd39d3acaf97b0721ecf36?branch=rawhide) but I should also include the former.

Comment 9 Fedora Update System 2024-04-29 02:23:54 UTC
FEDORA-2024-53eef902c8 (puppet-8.3.1-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.