Bug 1610717

Summary: Enable network inside chroot fails
Product: [Fedora] Fedora EPEL Reporter: Frank Büttner <bugzilla>
Component: mockAssignee: Miroslav Suchý <msuchy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: jdisnard, jkeating, mebrown, msimacek, msuchy, praiskup, williams
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-02 11:38:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Büttner 2018-08-01 09:12:41 UTC 
Description of problem:
Inside the chroot networking will fails, when it was activated.

Version-Release number of selected component (if applicable):
mock-1.4.11-1.el7.noarch


How reproducible:
Every time

Steps to Reproduce:
1. Add an call "wget http://repo1.maven.org/maven2/org/antlr/antlr/3.1.3/antlr-3.1.3.pom" inside the spec file
2. try to build it


Actual results:
It will fails because network will not work.
Error:
+ wget http://repo1.maven.org/maven2/org/antlr/antlr/3.1.3/antlr-3.1.3.pom
--2018-08-01 11:07:43--  http://repo1.maven.org/maven2/org/antlr/antlr/3.1.3/antlr-3.1.3.pom
Resolving repo1.maven.org (repo1.maven.org)... failed: Name or service not known.
wget: unable to resolve host address 'repo1.maven.org'



Expected results:
Network inside the chroot, when enabled.

Additional info:
I have try the following options:
--enable-network -> fails
--enable-network --config-opts=rpmbuild_networking=True --config-opts=use_host_resolv=True -> fails
--config-opts=rpmbuild_networking=True --config-opts=use_host_resolv=True -> fails
Comment 1 Miroslav Suchý 2018-08-02 11:38:05 UTC 

*** This bug has been marked as a duplicate of bug 1593212 ***