Forwarding to infra-support for analysis.
---------- Forwarded message ---------
From: Lev Veyde <firstname.lastname@example.org>
Date: Thu, Apr 23, 2020 at 2:02 PM
Subject: Problem with the mock parameters
To: infra <email@example.com>
Cc: Sandro Bonazzola <firstname.lastname@example.org>
it looks like we have some issues in the mock parameters on some of the
note the ERROR: Option --old-chroot has been deprecated. Use
Thanks in advance,
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
email@example.com | firstname.lastname@example.org
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
Infra mailing list – email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
Associate Manager - RHV DevOps - Red Hat
We need to ensure the new `--isolation` option still enables one to use chroots with mock as opposed to systemd-nspawn containers.
If it does support chroot - use can enable it by making `mock_runner.sh` check the output of `mock -h` and use the new option if its found there. We already had code in it that does something like that fromthe last time the mock CLI was changed.
If the chroot support was removed we have two options:
Keep an older version of mock somewhere and use that
Port our code to work with systemd-nspawn. I used to have n epic about this in Jira that detailed what we would need to fix to make that happen. I think most of the more serious fixes are in placealeady anyway.
According to the documentation --isolation=simple is equivalent to --old-chroot and --isolation=nspawn is equivalent to the --new-chroot option.
I updated the patch to rely on the output of the mock -h, and use --isolation if it supports it.