As of recently, when we try to build in koji, if we run the junit tests, the build fails because the test engine is trying to resolve the hostname -- and you can't do that on the koji machines. On the koji machines, only localhost is resolvable.
So this affects koji scratch builds and regualr builds, but not mock builds which by default take the resolv.conf of the local machine.
This is a recent problem in f18. It does not occur on f19 builds, and it does mean that builds that used to work on f18 -- 10.0.0-2 for example, now no longer build in a scratch build.
The workaround for 10.0.1 was to comment out the junit tests, so we could get a build. This is not really an ideal solution. We need to figure out what changed in f18. All indications are for a change in one of the underlying packages.
Metadata Update from @vakwetu: - Issue assigned to vakwetu - Issue set to the milestone: UNTRIAGED
Fixed in master branch:
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: UNTRIAGED) - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1054
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.