FEDORA-2021-ec4a4b2634 — enhancement update for puppet

stable

puppet-7.9.0-1.fc34

FEDORA-2021-ec4a4b2634 created by brandfbb 3 years ago for Fedora 34

Update Puppet from version 5.5 (which completely broken in Fedora 34 due to Ruby 3) to 7.9.0.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2021-ec4a4b2634

This update has been submitted for testing by brandfbb.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago

This update's test gating status has been changed to 'waiting'.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago

ekohl commented 3 years ago

For others: this does change /etc/puppet to /etc/puppetlabs/puppet. Be aware of this when upgrading.

ekohl edited this update.

3 years ago

This update has been pushed to testing.

3 years ago

ekohl commented & provided feedback 3 years ago

karma

Looks like upgrading actually fails on my machine because we have Obsoletes: puppet-headless < 6.0.0 and I have a weird local build. Probably not something most users care about but posting here just as an example:

  file /usr/share/man/man5/puppet.conf.5.gz from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/man/man8/puppet-config.8.gz from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/man/man8/puppet-module.8.gz from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/defaults.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/face/config.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/face/module/install.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/face/module/list.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/face/module/uninstall.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/reference/configuration.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /usr/share/ruby/vendor_ruby/puppet/util/run_mode.rb from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch
  file /var/lib/puppet from install of puppet-7.7.0-4.fc34.noarch conflicts with file from package puppet-headless-7.7.0-1.fc34.noarch

I also noticed it pulled in augeas itself but I think ruby-augeas should be sufficient.

I then see this:

# puppet agent -t --noop
Error: Cannot create /opt/puppetlabs/puppet/public; parent directory /opt/puppetlabs/puppet does not exist
Error: /File[/opt/puppetlabs/puppet/public]/ensure: change from 'absent' to 'directory' failed: Cannot create /opt/puppetlabs/puppet/public; parent directory /opt/puppetlabs/puppet does not exist
Error: Could not prepare for execution: Got 1 failure(s) while initializing: File[/opt/puppetlabs/puppet/public]: change from 'absent' to 'directory' failed: Cannot create /opt/puppetlabs/puppet/public; parent directory /opt/puppetlabs/puppet does not exist

This is a path we've missed. From the debug log it looks like it's publicdir:

Debug: Using settings: adding file resource 'publicdir': 'File[/opt/puppetlabs/puppet/public]{:path=>"/opt/puppetlabs/puppet/public", :mode=>"755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

3 years ago

ekohl commented & provided feedback 3 years ago

I opened https://src.fedoraproject.org/rpms/puppet/pull-request/14 which I think should address the publicdir.

This update can be pushed to stable now if the maintainer wishes

3 years ago

ekohl edited this update.

New build(s):