Bug 1815992 - Should doc which external links cannot be accessed for build in IPv6 cluster
Summary: Should doc which external links cannot be accessed for build in IPv6 cluster
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Wenjing Zheng
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-23 05:47 UTC by Wenjing Zheng
Modified: 2020-11-02 01:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-02 01:31:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Wenjing Zheng 2020-03-23 05:47:17 UTC
Document URL: 

Section Number and Name: 

Describe the issue: 
Some external link used for build cannot be accessed in IPv6 cluster. for example github,Maven Central (Java), npm (NodeJS), and RubyGems (Ruby)


Suggestions for improvement: 
Should add such limitation for IPv6 cluster.

Additional information: 
1. github cannot be access for build in an IPv6 cluster:
Cloning "https://github.com/jboss-developer/jboss-eap-quickstarts.git" ...
error: fatal: unable to access 'https://github.com/jboss-developer/jboss-eap-quickstarts.git/': Failed to connect to 13.229.188.59: Network is unreachable

2. Maven Central (Java) cannot be access for build in an IPv6 cluster:
[INFO] Retrying request to {s}->https://maven.repository.redhat.com:443
[INFO] I/O exception (java.net.SocketException) caught when processing request to {s}->https://maven.repository.redhat.com:443: Network is unreachable (connect failed)
[FATAL] Non-resolvable parent POM for org.jboss.eap.quickstarts:kitchensink:[unknown-version]: Could not transfer artifact org.jboss.eap.quickstarts:quickstart-parent:pom:7.3.0.CD18 from/to central (https://repo1.maven.org/maven2): Network is unreachable (connect failed) and 'parent.relativePath' points at wrong local POM @ line 20, column 13

3. RubyGems (Ruby) cannot be access for build in an IPv6 cluster:
Retrying fetcher due to error (2/3): Bundler::HTTPError Could not fetch specs from https://rubygems.org/
Retrying fetcher due to error (3/3): Bundler::HTTPError Could not fetch specs from https://rubygems.org/
Could not fetch specs from https://rubygems.org/

4. npm (NodeJS) cannot be access for build in an IPv6 cluster:
---> Installing all dependencies
npm ERR! code ENETUNREACH
npm ERR! errno ENETUNREACH
npm ERR! request to https://registry.npmjs.org/chai failed, reason: connect ENETUNREACH 2606:4700::6810:1723:443

npm ERR! A complete log of this run can be found in:
npm ERR!     /opt/app-root/src/.npm/_logs/2020-03-23T03_33_13_339Z-debug.log
subprocess exited with status 1
subprocess exited with status 1
error: build error: error building at STEP "RUN /usr/libexec/s2i/assemble": exit status 1

Comment 3 Vikram Goyal 2020-11-02 01:31:05 UTC
OCP 4.2 and 4.3 are EOL after OCP 4.5 and 4.6 GA respectively.

This is a notification that this bug is being CLOSED as EOL as per the previous comment on this bug.

See my announcement email sent a week ago here [2].

If you have a customer case with a support exception or if you think this issue still applies on 4.4+, please reopen and include those details. When reopening, please change the reported version to 4.4+.

[1]: https://access.redhat.com/support/policy/updates/openshift
[2]: http://post-office.corp.redhat.com/archives/openshift-sme/2020-October/msg00826.html


Note You need to log in before you can comment on or make changes to this bug.