hack/build: Pin to RHCOS 47.330 and quay.io/openshift-release-dev/ocp-release:4.0.0-0.6

[wking]

DO NOT MERGE! This PR is just for CI coverage (like #1271 and similar before it), with pins on top of the change-log in #1344.

@smarterclayton pushed 4.0.0-0.nightly-2019-02-27-213933 to quay.io/openshift-release-dev/ocp-release:4.0.0-0.6. Extracting the associated RHCOS build:

$ oc adm release info --pullspecs quay.io/openshift-release-dev/ocp-release:4.0.0-0.6 | grep machine-os-content
 machine-os-content  registry.svc.ci.openshift.org/ocp/4.0-art-latest-2019-02-27-213933@sha256:1262533e31a427917f94babeef2774c98373409897863ae742ff04120f32f79b
$ oc image info registry.svc.ci.openshift.org/ocp/4.0-art-latest-2019-02-26-125216@sha256:1262533e31a427917f94babeef2774c98373409897863ae742ff04120f32f79b | grep version
           version=47.330

that's the same machine-os-content image referenced from 4.0.0-0.5, which we used for installer v0.13.0 (#1271).

/hold

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wking

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 [wking]

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

[abhinavdahiya]

LGTM

[openshift-ci-robot]

@wking: The following test failed for commit a9bb8a6, say /retest to rerun them:

Test name	Details	Rerun command
ci/prow/e2e-aws	link	/test e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[wking]

e2e-aws:

level=error msg="\t* aws_route.to_nat_gw.2: Error creating route: timeout while waiting for state to become 'success' (timeout: 2m0s)"

/retest

[abhinavdahiya]

e2e-aws:

Failing tests:

[sig-api-machinery] CustomResourcePublishOpenAPI [Feature:CustomResourcePublishOpenAPI] works for CRD without validation schema [Suite:openshift/conformance/parallel] [Suite:k8s]

/retest

[wking]

e2e-aws:

Flaky tests:

[k8s.io] Probing container should be restarted with a exec "cat /tmp/health" liveness probe [NodeConformance] [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]

Failing tests:

[sig-api-machinery] CustomResourcePublishOpenAPI [Feature:CustomResourcePublishOpenAPI] works for CRD without validation schema [Suite:openshift/conformance/parallel] [Suite:k8s]

Good enough for me. But run one more while I upload the tag and binaries:

/retest

[wking]

e2e-aws:

level=fatal msg="failed to initialize the cluster: Cluster operator cluster-autoscaler has not yet reported success"

But whatever, this commit is 0.13.1.

/close

[openshift-ci-robot]

@wking: Closed this PR.

In response to this:

e2e-aws:

level=fatal msg="failed to initialize the cluster: Cluster operator cluster-autoscaler has not yet reported success"

But whatever, this commit is 0.13.1.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.