bootstrap_container option is broken in on F30 builders

[Pavel Raiskup]

Hi all,

we are in the process of migration builders to F30, and from recent build
failures I deduce that the bootstrap_container feature is broken, or that
we have the mock misconfigured on F30.

If you see where the problem is, please let us know.  Not really 100%
work-around is to disable bootstrap_container feature (Settings -> uncheck
the "Enable mock's use_bootstrap_container experimental feature").  In
many cases it was enabled unintentionally;  for a certain time period this
was enabled by default.

I'll have a look at the problem tomorrow morning (or sooner maybe), sorry
for temporary inconvenience.

Pavel

[Pavel Raiskup]

On Monday, May 27, 2019 6:00:29 PM CEST Pavel Raiskup wrote:
>  we are in the process of migration builders to F30, and from recent
> build
>  failures I deduce that the bootstrap_container feature is broken, or that
>  we have the mock misconfigured on F30. 
There was for some reason (I need to check) enabled systemd-resolved
service on builder VMs.  Not only there, on fresh Fedora 30 install on my
laptop I got the service enabled as well.

I think that systemd-nspawn (used in copr by default) detects that
systemd-resolved is running on host (even though host's /etc/resolv.conf
is generated by network manager :-)) - and creates its own stub
/etc/resolv.conf in the container using the host's systemd-resolved
feature.  And then, the systemd-resolved service suffers from some
race-condition issue (rhbz#1710699).

I hoped that mock's use_host_resolv will work-around the issues, but
there's a bunch of issues to be fixed in mock till use_host_resolv
will work fine with use_nspawn mock option.

So be careful to use 'mock --bootstrap-chroot' with systemd-resolved
enabled on F30.  Copr builders have the service now disabled, and all
seems to be working fine..  sorry for the delay.

Happy building!
Pavel