Bug 1748271 - [HTTPS_PROXY] build met warning message about: MountVolume.SetUp failed when build in https_proxy cluster
Summary: [HTTPS_PROXY] build met warning message about: MountVolume.SetUp failed when...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Gabe Montero
QA Contact: wewang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-03 09:10 UTC by wewang
Modified: 2019-10-16 06:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:39:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-controller-manager pull 22 0 None closed Bug 1748271: Copy global CA data to builds 2021-01-27 16:35:09 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:40:03 UTC

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


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