Description of problem: Version-Release number of selected component (if applicable): sudo-1.8.29-1.fc31.x86_64 How reproducible: Always Steps to Reproduce: 1. Run Fedora in an lxc container 2. Update sudo to sudo-1.8.29-1.fc31.x86_64 3. Run sudo Actual results: sudo works, but emits an error Expected results: no errors are produced. Additional info: This did not happen with sudo-1.8.28-1.fc31.x86_64 [jason@penguin ~]$ rpm -q sudo sudo-1.8.28-1.fc31.x86_64 [jason@penguin ~]$ sudo su - Last login: Fri Nov 15 20:47:32 EST 2019 on pts/0 [root@penguin ~]# dnf update -y Last metadata expiration check: 0:07:40 ago on Fri 15 Nov 2019 08:40:07 PM EST. Dependencies resolved. ==================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================== Upgrading: sudo x86_64 1.8.29-1.fc31 updates 908 k Transaction Summary ==================================================================================================================================================== Upgrade 1 Package Total download size: 908 k Downloading Packages: sudo-1.8.29-1.fc31.x86_64.rpm 1.0 MB/s | 908 kB 00:00 ---------------------------------------------------------------------------------------------------------------------------------------------------- Total 830 kB/s | 908 kB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading : sudo-1.8.29-1.fc31.x86_64 1/2 Running scriptlet: sudo-1.8.29-1.fc31.x86_64 1/2 Cleanup : sudo-1.8.28-1.fc31.x86_64 2/2 Running scriptlet: sudo-1.8.28-1.fc31.x86_64 2/2 Verifying : sudo-1.8.29-1.fc31.x86_64 1/2 Verifying : sudo-1.8.28-1.fc31.x86_64 2/2 Upgraded: sudo-1.8.29-1.fc31.x86_64 Complete! [root@penguin ~]# logout [jason@penguin ~]$ sudo su - sudo: setrlimit(RLIMIT_CORE): Operation not permitted Last login: Fri Nov 15 20:47:41 EST 2019 on pts/0 [root@penguin ~]#
As a workaround to get rid of the error I can do the following: $ cat /etc/sudo.conf Set disable_coredump false
FEDORA-2020-7c1b270959 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-7c1b270959
sudo-1.9.0-0.1.b1.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7c1b270959
sudo-1.9.0-0.1.b1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8b563bc5f4
sudo-1.9.0-0.1.b1 does not seem to fix the problem for me inside my toolboxes.
sudo-1.9.0-0.1.b1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
This new package does not fix the problem: $ sudo rpm -q sudo sudo: setrlimit(RLIMIT_CORE): Operation not permitted sudo-1.9.0-0.1.b1.fc31.x86_64
I am wondering should the fedora container be allowed to set RLIMIT_CORE? I don't really see why not: maybe this CAP is determined by podman/buildah? At least this didn't happen earlier...
But I guess it is something new that sudo is doing since 1.8.29. I opened a ticket in github: https://github.com/sudo-project/sudo/issues/42
Upstream released a fix in 1.8.31p1.
sudo-1.9.0-0.1.b1.fc32 has been pushed to the Fedora 32 stable repository. If problems still persist, please make note of it in this bug report.
Please remove the bug from Bodhi next time :)
I think this will get fixed in sudo 1.9.0b5. Also dunno why we are shipping a beta release of sudo in F31?
(It is already fixed in the sudo 1.8.31p1 release.)
But can we update to 1.9.0b4 first in F32+? To test it more before 1.9.0b5 is released.
(In reply to Jens Petersen from comment #14) > I think this will get fixed in sudo 1.9.0b5. > > Also dunno why we are shipping a beta release of sudo in F31? Sudo beta releases are stable enough and we need proper testing before 1.9.0 stable. Also me and @alakatos were wondering about waiting for 1.9.0 stable now, cause we don't have much time for rebases.
https://src.fedoraproject.org/rpms/sudo/pull-request/13 (see also bug 1816593).
(In reply to Radovan Sroka from comment #17) > Sudo beta releases are stable enough and we need proper testing before 1.9.0 > stable. Sure it is your call - I am not very familiar with sudo releases etc. > Also me and @alakatos were wondering about waiting for 1.9.0 stable now, > cause we don't have much time for rebases. Anyway bug is already fixed in the 1.8.31p1 release... https://www.sudo.ws/pipermail/sudo-announce/2020-March/000172.html
(In reply to Jens Petersen from comment #18) > https://src.fedoraproject.org/rpms/sudo/pull-request/13 (see also bug > 1816593). Working fine for me here.
(In reply to Jens Petersen from comment #18) > https://src.fedoraproject.org/rpms/sudo/pull-request/13 (see also bug > 1816593). Can you update the PR, so we can merge it? There have been some changes in master since you opened the PR.
Done, thanks
FEDORA-2020-034d5a4cae has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-034d5a4cae
FEDORA-2020-242921ccb4 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-242921ccb4
Thanks for the updates Just noting that this also affects f30 - if f30 was updated to 1.8.31p1 that would make the warning go away, I think.
(In reply to Jens Petersen from comment #25) > Thanks for the updates > > Just noting that this also affects f30 - if f30 was updated to 1.8.31p1 > that would make the warning go away, I think. That makes sense to me and I agree with you. Thank you.
FEDORA-2020-b3edb41afd has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b3edb41afd
FEDORA-2020-242921ccb4 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-242921ccb4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-242921ccb4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-b3edb41afd has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b3edb41afd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b3edb41afd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-034d5a4cae has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-034d5a4cae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-034d5a4cae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-034d5a4cae has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-242921ccb4 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-b3edb41afd has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.