Revert "Implementing Proxy CA Bundle validation."

[bparees]

Reverts #342

I don't think there was anything wrong w/ the original PR but the Dockerfile changes didn't get synced to distgit, so it started failing in our ART nightlies. once that issue is resolved, this can be un-reverted.

@wking @ricardomaraschini

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [bparees]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bparees]

slack discussion here:
https://coreos.slack.com/archives/CEKNRGF25/p1565415755176800

bug for resolving the dockerfile sync issue is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1727080

[bparees]

/retest

…

On Sat, Aug 10, 2019 at 12:04 PM OpenShift CI Robot < ***@***.***> wrote: @bparees <https://github.com/bparees>: The following test *failed*, say /retest to rerun them all: Test name Commit Details Rerun command ci/prow/e2e-aws 0c96cbf <0c96cbf> link <https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/363/pull-ci-openshift-cluster-image-registry-operator-master-e2e-aws/1782> /test e2e-aws Full PR test history <https://prow.svc.ci.openshift.org/pr-history?org=openshift&repo=cluster-image-registry-operator&pr=363>. Your PR dashboard <https://prow.svc.ci.openshift.org/pr?query=is:pr+state:open+author:bparees>. Please help us cut down on flakes by linking to <https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests> an open issue <https://github.com/openshift/cluster-image-registry-operator/issues?q=is:issue+is:open> when you hit one in your PR. Instructions for interacting with me using PR comments are available here <https://git.k8s.io/community/contributors/guide/pull-requests.md>. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra <https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:> repository. I understand the commands that are listed here <https://go.k8s.io/bot-commands>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#363?email_source=notifications&email_token=ABF6LXW64JS6AVCUEDUO7RDQD3RHJA5CNFSM4IKZTR2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4AQHMY#issuecomment-520160179>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABF6LXRPXSRUDJDG6IER6QTQD3RHJANCNFSM4IKZTR2A> .

-- Ben Parees | OpenShift

[wking]

e2e-aws had a number of errors. The first was:

Error from server: error dialing backend: remote error: tls: internal error
...
failed: (22.1s) 2019-08-10T15:24:09 "[sig-storage] PersistentVolumes-local  [Volume type: blockfswithoutformat] One pod requesting one prebound PVC should be able to mount volume and write from pod1 [Suite:openshift/conformance/parallel] [Suite:k8s]"

There are a few bugs mentioning similar errors, but they're all closed or verified. We should probably open a new one once we have time to dig in.