Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1262887 - Different root home dir for old/new chroot
Summary: Different root home dir for old/new chroot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-14 14:43 UTC by Vít Ondruch
Modified: 2016-06-02 14:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-02 14:46:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Vít Ondruch 2015-09-14 14:43:15 UTC 
Description of problem:

$ mock -r ruby -q --new-chroot --chroot 'realpath ~'
Spawning container b379de02cf7f49cdac8bf5d3ac4a95d0 on /var/lib/mock/ruby/root.
Press ^] three times within 1s to kill container.
/root
Container b379de02cf7f49cdac8bf5d3ac4a95d0 exited successfully.

$ mock -r ruby -q --old-chroot --chroot 'realpath ~'
/builddir

Version-Release number of selected component (if applicable):
$ rpm -q mock
mock-1.2.12-1.fc22.noarch


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jan Kurik 2016-02-24 13:44:58 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 2 Miroslav Suchý 2016-06-02 14:46:43 UTC 
I am not sure when and how this was fixed, but it is working correctly now.
Note You need to log in before you can comment on or make changes to this bug.