I have found that since upgrading mock on my sole builder for doing livemedia tasks that these tasks no longer work. Previously, I had mock-1.4.6-1.fc26 with no problems, but mock-1.4.8-1 causes issues.
Digging around the logs for a failed livemedia task is always fun because lots of errors are normal, but not fatal. However, I see in anaconda-anaconda.log messages to the effect that "The group 'core' is required for this installation. This group does not exist. This is a fatal error and installation will be aborted." I think the real cause though is revealed in anaconda-dnf.librepo.log where I see "Curl error (6): Couldn't resolve host name for http://hostname..." which stems from the "url --url=http://hostname..." directive in my kickstart.
I see in the release notes for 1.4.7 and 1.4.8 mentions about changes related to how network connectivity is affected in the build roots, but those seem relevant only to systemd-nspawn. Since koji-1.15 hasn't made it's way to CentOS or Fedora repos yet, I'm still on 1.14 and so necessarily have a tag option "mock.new_chroot : False" set. To overcome the issues with upgrading to mock-1.4.8, I've also tried adding "mock.rpmbuild_networking : True" and "mock.use_host_resolv : True" but still the build root is preventing name resolution.
Any ideas?
Dne 26.1.2018 v 22:38 John Florian napsal(a):
I have found that since upgrading mock on my sole builder for doing livemedia tasks that these tasks no longer work. Previously, I had mock-1.4.6-1.fc26 with no problems, but mock-1.4.8-1 causes issues.
Digging around the logs for a failed livemedia task is always fun because lots of errors are normal, but not fatal. However, I see in anaconda-anaconda.log messages to the effect that "The group 'core' is required for this installation. This group does not exist. This is a fatal error and installation will be aborted." I think the real cause though is revealed in anaconda-dnf.librepo.log where I see "Curl error (6): Couldn't resolve host name for http://hostname..." which stems from the "url --url=http://hostname..." directive in my kickstart.
I see in the release notes for 1.4.7 and 1.4.8 mentions about changes related to how network connectivity is affected in the build roots, but those seem relevant only to systemd-nspawn. Since koji-1.15 hasn't made it's way to CentOS or Fedora repos yet, I'm still on 1.14 and so necessarily have a tag option "mock.new_chroot : False" set. To overcome the issues with upgrading to mock-1.4.8, I've also tried adding "mock.rpmbuild_networking : True" and "mock.use_host_resolv : True" but still the build root is preventing name resolution.
Full log will help.
Are you able to build the package in Copr? With network enabled and disabled?
Mirek
On Mon, 2018-01-29 at 17:05 +0100, Miroslav Suchý wrote:
Dne 26.1.2018 v 22:38 John Florian napsal(a):
I have found that since upgrading mock on my sole builder for doing livemedia tasks that these tasks no longer work. Previously, I had mock-1.4.6-1.fc26 with no problems, but mock-1.4.8-1 causes issues.
Digging around the logs for a failed livemedia task is always fun because lots of errors are normal, but not fatal. However, I see in anaconda-anaconda.log messages to the effect that "The group 'core' is required for this installation. This group does not exist. This is a fatal error and installation will be aborted." I think the real cause though is revealed in anaconda-dnf.librepo.log where I see "Curl error (6): Couldn't resolve host name for http://hostname..." which stems from the "url --url=http://hostname..." directive in my kickstart.
I see in the release notes for 1.4.7 and 1.4.8 mentions about changes related to how network connectivity is affected in the build roots, but those seem relevant only to systemd-nspawn. Since koji-1.15 hasn't made it's way to CentOS or Fedora repos yet, I'm still on 1.14 and so necessarily have a tag option "mock.new_chroot : False" set. To overcome the issues with upgrading to mock-1.4.8, I've also tried adding "mock.rpmbuild_networking : True" and "mock.use_host_resolv : True" but still the build root is preventing name resolution.
Full log will help.
An example is available here: https://paste.fedoraproject.org/paste/Qod kS4VopC8xitiQ1J0PtA
Are you able to build the package in Copr? With network enabled and disabled?
Not a package -- this is livemedia. I've never built anything in Copr, only in our private Koji instance. Network is enabled on the Koji builder, of course. Whether or not it's enabled in the mock chroot I can't say. With mock-1.4.6 (and apparently 1.4.7 too from more recent tests), I'd say it has to be enabled in the mock chroot as I don't see how the task could complete otherwise. With 1.4.8, it seems it is disabled, though I don't understand why.
koji-devel@lists.stg.fedorahosted.org
-
John Florian -
Miroslav Suchý