-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
Testable
When running scratch-build for target: c9s-candidate related to this PR <https://gitlab.com/redhat/centos-stream/rpms/ruby/-/merge_requests/18>, I saw that DNS is enabled in s390x servers.
$ centpkg --release c9s scratch-build --srpm --nowait
Here is the CentOS stream koji link.
https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2412513
Host is "s390-04.stream.rdu2.redhat.com" seeing the s390x build task below.
https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2412519
I tried to check the DNS connection using the following patch on the PR above.
$ git diff
diff --git a/ruby.spec b/ruby.spec
index 012cdcb..6d1de40 100644
--- a/ruby.spec
+++ b/ruby.spec
@@ -298,6 +298,9 @@ BuildRequires: gcc
BuildRequires: make
BuildRequires: zlib-devel
+BuildRequires: %{_bindir}/dig
+
+
# This package provides %%{_bindir}/ruby-mri therefore it is marked by this
# virtual provide. It can be installed as dependency of rubypick.
Provides: ruby(runtime_executable) = %{ruby_release}
@@ -691,6 +694,9 @@ analysis result in RBS format, a standard type description format for Ruby
%prep
+# Debug
+dig index.rubygems.org || :
+
%setup -q -n %{ruby_archive}
# Remove bundled libraries to be sure they are not used.
But the build was succeeded. The used s390x host is "s390-03.stream.rdu2.redhat.com".
https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2412559
So, I assumed that DNS servers are enabled in some s390x build servers. Could you take a look to disable the DNS on the servers?
As a note, the unit tests in the ruby spec file access to the following domains.
rubygems.org www.rubygems.org staging.rubygems.org index.rubygems.org
I remember we faced this issue in another brew servers. So, I hope a systematic approach not to repeat this kind of issue again in the future.
Thank you.
- is related to
-
-
- New
-
- relates to
-
-
- Planning
-
- mentioned on
