Comments

26 Comments
karma

works now; not sure why it failed last time... maybe I didn't have updates enabled at the time, but that'd be strange

[root@fe88089cb8fe /]# yum upgrade --advisory=FEDORA-2021-ea80a01b49
Last metadata expiration check: 0:01:29 ago on Mon Apr 26 15:15:58 2021.
Dependencies resolved.
============================================================
 Package             Arch   Version           Repo     Size
============================================================
Upgrading:
 grub2-common        noarch 1:2.06~rc1-4.fc34 updates 934 k
 grub2-efi-x64       x86_64 1:2.06~rc1-4.fc34 updates 499 k
 grub2-tools         x86_64 1:2.06~rc1-4.fc34 updates 1.9 M
 grub2-tools-minimal x86_64 1:2.06~rc1-4.fc34 updates 612 k
Installing dependencies:
 freetype            x86_64 2.10.4-3.fc34     fedora  394 k
 graphite2           x86_64 1.3.14-7.fc34     fedora   95 k
 grub2-tools-efi     x86_64 1:2.06~rc1-4.fc34 updates 552 k
 grub2-tools-extra   x86_64 1:2.06~rc1-4.fc34 updates 855 k
 harfbuzz            x86_64 2.7.4-3.fc34      fedora  634 k
 libpng              x86_64 2:1.6.37-10.fc34  fedora  119 k

Transaction Summary
============================================================
Install  6 Packages
Upgrade  4 Packages

Total download size: 6.4 M

Pulls in some extra dependencies vs the previous version:

[root@fe88089cb8fe /]# yum upgrade --advisory=FEDORA-2021-ea80a01b49 Last metadata expiration check: 0:01:29 ago on Mon Apr 26 15:15:58 2021. Dependencies resolved. ============================================================ Package Arch Version Repo Size ============================================================ Upgrading: grub2-common noarch 1:2.06~rc1-4.fc34 updates 934 k grub2-efi-x64 x86_64 1:2.06~rc1-4.fc34 updates 499 k grub2-tools x86_64 1:2.06~rc1-4.fc34 updates 1.9 M grub2-tools-minimal x86_64 1:2.06~rc1-4.fc34 updates 612 k Installing dependencies: freetype x86_64 2.10.4-3.fc34 fedora 394 k graphite2 x86_64 1.3.14-7.fc34 fedora 95 k grub2-tools-efi x86_64 1:2.06~rc1-4.fc34 updates 552 k grub2-tools-extra x86_64 1:2.06~rc1-4.fc34 updates 855 k harfbuzz x86_64 2.7.4-3.fc34 fedora 634 k libpng x86_64 2:1.6.37-10.fc34 fedora 119 k

Transaction Summary

Install 6 Packages Upgrade 4 Packages

Total download size: 6.4 M

karma

Problem: cannot install the best update candidate for package libbluray-1.2.1-2.fc33.x86_64 - nothing provides libudfread.so.0()(64bit) needed by libbluray-1.3.0-1.fc33.x86_64

The error went away after a reboot. Otherwise, downgrading to the previous version made it work also.

karma

[user1@localhost ~]$ podman run -it --rm ubi8 echo test test [user1@localhost ~]$ rpm -q podman podman-3.0.1-1.fc33.x86_64 [user1@localhost ~]$ podman run -it --rm ubi8 echo test ERRO[0000] error unmounting /home/user1/.local/share/containers/storage/overlay/98570b4417e481626699854d927ba4425a7146809be053027177556c4f8b1938/merged: invalid argument Error: error mounting storage for container 040c7194ab1372ad4cad1c19345e7fb23d0d297994c3bdf4d31811e890126362: error creating overlay mount to /home/user1/.local/share/containers/storage/overlay/98570b4417e481626699854d927ba4425a7146809be053027177556c4f8b1938/merged, mount_data=",lowerdir=/home/user1/.local/share/containers/storage/overlay/l/QOGJSS76ABUBTR3K32IPZW6OZF:/home/user1/.local/share/containers/storage/overlay/l/ZUXR33ROCFWIYMLMEGWWTVNM73,upperdir=/home/user1/.local/share/containers/storage/overlay/98570b4417e481626699854d927ba4425a7146809be053027177556c4f8b1938/diff,workdir=/home/user1/.local/share/containers/storage/overlay/98570b4417e481626699854d927ba4425a7146809be053027177556c4f8b1938/work,userxattr,context=\"system_u:object_r:container_file_t:s0:c187,c613\"": permission denied [user1@localhost ~]$ rpm -q podman podman-3.1.0-1.fc33.x86_64

karma

seems to fix the previously-broken rootless overlay mounts

broke rootless for me:

$ podman run -it --rm ubi8 ERRO[0000] error unmounting /home/user1/.local/share/containers/storage/overlay/9b28d0d31ad7a23398ceb59f96de532c2152a8296a672557b2c9803b91d99fdd/merged: invalid argument Error: error mounting storage for container d4f7f642837f9a776c9595525143c96954ef703093b90ffa8e1a23496570c6e2: error creating overlay mount to /home/user1/.local/share/containers/storage/overlay/9b28d0d31ad7a23398ceb59f96de532c2152a8296a672557b2c9803b91d99fdd/merged, mount_data=",lowerdir=/home/user1/.local/share/containers/storage/overlay/l/QOGJSS76ABUBTR3K32IPZW6OZF:/home/user1/.local/share/containers/storage/overlay/l/ZUXR33ROCFWIYMLMEGWWTVNM73,upperdir=/home/user1/.local/share/containers/storage/overlay/9b28d0d31ad7a23398ceb59f96de532c2152a8296a672557b2c9803b91d99fdd/diff,workdir=/home/user1/.local/share/containers/storage/overlay/9b28d0d31ad7a23398ceb59f96de532c2152a8296a672557b2c9803b91d99fdd/work,userxattr,context=\"system_u:object_r:container_file_t:s0:c125,c263\"": permission denied

karma

Not sure if it's the fault of the update, but I did get this that I haven't seen before. I also don't know that the crash actually breaks/broke anythnig... I ran a container interactively, then sometime later I got the ABRT error.

"The application encountered a problem and could not continue" "conmon killed by SIGABRT"

--- Running report_uReport --- ('report_uReport' completed successfully)

--- Skipping collect_GConf --- No matching actions found for this event.

--- Skipping collect_vimrc_user --- No matching actions found for this event.

--- Skipping collect_vimrc_system --- No matching actions found for this event.

--- Skipping collect_xsession_errors --- No matching actions found for this event.

--- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings Preparing an archive to upload Uploading 71.1 KiB Upload successful Retrace job started Analyzing crash data ......... Generating backtrace ................. Retrace job finished successfully

--- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla

karma

On a fresh install, the profile.d files are completely missing.

[root@dd3a49c7a024 /]# rpm -r /mnt/sysimage/ -Va vim* -v | grep '^[^/]*g'
missing   g /usr/share/vim/vimfiles/doc/tags
missing   c /etc/profile.d/vim.csh
missing   c /etc/profile.d/vim.sh
missing   g /usr/share/fish/vendor_functions.d/vim.fish
missing   c /etc/profile.d/vim.csh
missing   c /etc/profile.d/vim.sh
missing   g /usr/share/fish/vendor_functions.d/vim.fish

other than the cosmetic issue above, it seems to be functional for me

[root@93125a6375f1 /]# podman version
Version:            1.4.5-dev
RemoteAPI Version:  1
Go Version:         go1.12.6
OS/Arch:            linux/amd64
[root@93125a6375f1 /]# rpm -q podman
podman-1.4.4-1.fc30.x86_64
karma

podman version shows:

$ podman version
Version:            1.4.5-dev
RemoteAPI Version:  1
Go Version:         go1.11.11
OS/Arch:            linux/amd64
karma

Updating to "generally functional" because those smart enough to add their services to the clamscan group will also be smart enough to add them to the virusgroup group. Would be great to also see the fix for #859339 shipped to epel.

karma

Seems that it counts as +1 if I said 'generally functional'...

karma

Update is functional and works fine on new installations. Change of group from clamscan to virusgroup breaks existing installations that rely on having added system users to the clamscan group. Unfortunately, I haven't yet read the entire thread on that bug. Not opposed to the change, only concerned for those with older installs. Can we setfacl in an RPM to allow also clamscan group access?

karma

Breaks pamd module. Fixed in 2.6.1.