Comments
ekohl
provided feedback
on freight-0.3.13-9.el9
a month ago
I wonder why https://bugzilla.redhat.com/show_bug.cgi?id=2126539 wasn't closed when I updated in Rawhide. Looks like it wasn't attached to https://bodhi.fedoraproject.org/updates/FEDORA-2023-44d0a5c8a7 so I should look at my bug referencing there.
I would have preferred to keep git branches in sync, so a simple git merge from rawhide into epel9.
The automated test for rubygem-scanf-1.0.0-1.fc36 looks like a false positive.
Not sure if I can give karma on my own update, but I upgraded my server and it works.
With this I'm able to use Vagrant (with vagrant-libvirt), prior to this (with rubygem-net-ssh-6.1.0-2.fc35.noarch) it failed.
Allows me to use fedora-review properly where previously it crashed.
I opened https://src.fedoraproject.org/rpms/puppet/pull-request/14 which I think should address the publicdir.
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}'
For others: this does change /etc/puppet to /etc/puppetlabs/puppet. Be aware of this when upgrading.
Looks like this introduced a regression. From https://community.theforeman.org/t/fix-for-problem-with-qpid-dispatch-router-1-2-0/10834
systemd[1]: Started Qpid Dispatch router daemon.
systemd[1]: Starting Qpid Dispatch router daemon...
qdrouterd[13453]: 2018-08-21 11:21:25.278980 +0200 ERROR (error) Python: AttributeError: 'module' object has no attribute '__import__'
qdrouterd[13453]: 2018-08-21 11:21:25.279507 +0200 ERROR (error) Traceback (most recent call last):
qdrouterd[13453]: File "/usr/lib/qpid-dispatch/python/qpid_dispatch_internal/dispatch.py", line 151, in <module>
qdrouterd[13453]: builtin_import = builtins.__import__
qdrouterd[13453]: AttributeError: 'module' object has no attribute '__import__'
systemd[1]: qdrouterd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Unit qdrouterd.service entered failed state.
systemd[1]: qdrouterd.service failed.