Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1748271

Summary:	[HTTPS_PROXY] build met warning message about: MountVolume.SetUp failed when build in https_proxy cluster
Product:	OpenShift Container Platform	Reporter:	wewang <wewang>
Component:	Build	Assignee:	Gabe Montero <gmontero>
Status:	CLOSED ERRATA	QA Contact:	wewang <wewang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	adam.kaplan, aos-bugs, bparees, dhansen, gmontero, jtanenba, wzheng
Target Milestone:	---
Target Release:	4.2.0
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:	2019-10-16 06:39:51 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:

Comment 2 Daneyon Hansen 2019-09-03 15:52:08 UTC

'Get https://10.0.151.88:10250/containerLogs/openshift-must-gather-ndrqk/must-gather-hfplk/gather?follow=true: proxyconnect tcp: x509: certificate signed by unknown authority' is failing because this call is being proxied when it shouldn't be. The '10.0.151.88' address does not fall within a noProxy cidr. Can you confirm your machineCIDR with the following:

$ oc get cm/cluster-config-v1 -n kube-system -o yaml

Comment 3 Daneyon Hansen 2019-09-03 16:03:45 UTC

Note: the inability to access pod logs is a duplicate of bug https://bugzilla.redhat.com/show_bug.cgi?id=1743174. If you machine IP's do not fall within the machineCIDR, you need to create a noProxy entry for the machine CIDR that is being used.

Comment 7 Ben Parees 2019-09-04 13:15:18 UTC

Assuming we're still just talking about the "warning" event, definitely not a blocker.  But also Gabe has a pair of PRs up that should resolve this when merged.

Comment 11 wewang 2019-09-06 06:40:05 UTC

Latest nightly payload has not include the pr yeah, when a new payload come out, will quicky verify it.

Comment 13 errata-xmlrpc 2019-10-16 06:39:51 UTC

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-2019:2922