Bug 1295323 - schroot for EPEL 7 fails to lock session file
Summary: schroot for EPEL 7 fails to lock session file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: schroot
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zach Carter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 08:12 UTC by Slawomir Czarko
Modified: 2018-05-31 13:05 UTC (History)
6 users (show)

Fixed In Version: schroot-1.6.10-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1045006
Environment:
Last Closed: 2018-05-31 13:05:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Slawomir Czarko 2016-01-04 08:12:41 UTC
Latest schroot for EPEL 7 doesn't include fix for Bug #1045006


+++ This bug was initially created as a clone of Bug #1045006 +++

Description of problem:

schroot fails to open session with an error message like:

[andris@ap doc]$ schroot -pc c32
E: centos-i386-0721e417-a54a-452a-bf95-5b20140efcb6: Failed to lock chroot: /var/lib/schroot/session/centos-i386-0721e417-a54a-452a-bf95-5b20140efcb6: Failed to write session file: Permission denied


Version-Release number of selected component (if applicable):

schroot-1.6.5-3.fc20.x86_64


How reproducible:

Always

Steps to Reproduce:
1. try to use schroot
2.
3.

Actual results:

I'm getting an error message as mentioned above

Expected results:

normal operation (worked before upgrade to Fedora 20)

Additional info:

Tested on 2 Fedora 20 systems
Problem can be workarounded by makeing /usr/bin/schroot suid root
(perhaps group rights would be preferable, but that should be fixed in the
package)

[andris@ap doc]$ ls -l /var/lib/schroot
total 8
drwxr-xr-x. 2 root root 4096 Dec 19 14:40 mount
drwxr-xr-x. 2 root root 4096 Dec 19 14:40 session

--- Additional comment from Zach Carter on 2013-12-19 11:06:26 EST ---

Reproduced it.   I'll get a fix out soon.

--- Additional comment from Fedora Update System on 2013-12-19 12:26:53 EST ---

schroot-1.6.5-4.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/schroot-1.6.5-4.fc20

--- Additional comment from Andris Pavenis on 2013-12-19 14:19:45 EST ---

Updated package works nicely. Thanks

--- Additional comment from Fedora Update System on 2013-12-20 21:10:16 EST ---

Package schroot-1.6.5-4.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing schroot-1.6.5-4.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23693/schroot-1.6.5-4.fc20
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-12-30 21:02:32 EST ---

schroot-1.6.5-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from André on 2015-01-12 07:01:53 EST ---

This issue still persists in Fedora 21 schroot-1.6.5-6.fc21 version.

Comment 1 Slawomir Czarko 2016-05-11 10:05:22 UTC
Any plans to fix this?

Comment 2 Fedora Update System 2018-05-11 20:02:51 UTC
schroot-1.6.10-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-70339c68b5

Comment 3 Fedora Update System 2018-05-12 20:23:29 UTC
schroot-1.6.10-3.el7 has been pushed to the Fedora EPEL 7 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-EPEL-2018-70339c68b5

Comment 4 Fedora Update System 2018-05-31 13:05:41 UTC
schroot-1.6.10-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, 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.