Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1578989 - jenkins slave does not respect no_proxy 3.9
jenkins slave does not respect no_proxy 3.9
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build (Show other bugs)
3.9.0
Unspecified Unspecified
unspecified Severity high
: ---
: 3.9.z
Assigned To: Gabe Montero
Wenjing Zheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-16 14:11 EDT by Gabe Montero
Modified: 2018-06-06 11:46 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: jenkins no_proxy processing could not handle suffixes like ".svc" Consequence: communication between a jenkins k8s agent pod and the jenkins master would attempt to go through a configured http_proxy and fail Fix: the openshift jenkins agent images are updated to automatically include the jenkins master and jnlp hosts in the no_proxy list Result: the jenkins limitation for no_proxy processing is circumvented
Story Points: ---
Clone Of: 1578987
: 1578993 (view as bug list)
Environment:
Last Closed: 2018-06-06 11:46:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3429951 None None None 2018-05-16 14:11 EDT
Red Hat Product Errata RHBA-2018:1796 None None None 2018-06-06 11:46 EDT

  None (edit)
Comment 1 Gabe Montero 2018-05-16 14:18:34 EDT
PR https://github.com/openshift/jenkins/pull/609 with the 3.9 change has merged

Moving to modified, will update with repro instructions when I see the new image in brew-pulp for QA to try.
Comment 5 errata-xmlrpc 2018-06-06 11:46:21 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1796

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