hack/build: Bump RHCOS from 47.245 to 47.249

[wking]

To fix a bug where Ignition was run on every boot (when it should only run on the first boot).

The 47.249 build is still running, but I thought I'd push this up so it's ready when the build goes out.

CC @crawford

[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

[ashcrow]

Thank you @wking

[wking]

Build is up.

/retest

[crawford]

This looks good. We aren't planning on merging this, correct? It will just end up under a tag?

[crawford]

failed to fetch Terraform Variables: failed to fetch dependency of "Terraform Variables": failed to fetch dependency of "Bootstrap Ignition Config": failed to fetch dependency of "Openshift Manifests": failed to generate asset "Worker Machines": failed to determine default AMI: failed to fetch RHCOS metadata: incorrect HTTP response (404 Not Found)

Looks like the upload succeeded.

/retest

[wking]

We aren't planning on merging this, correct? It will just end up under a tag?

Yeah, I don't think we need to bother merging, I'll just tag this once we have green CI.

[wking]

e2e-aws:

Flaky tests:

[Feature:DeploymentConfig] deploymentconfigs when run iteratively [Conformance] should immediately start a new deployment [Suite:openshift/conformance/parallel/minimal]
[Feature:DeploymentConfig] deploymentconfigs with test deployments [Conformance] should run a deployment to completion and then scale to zero [Suite:openshift/conformance/parallel/minimal]
[sig-storage] Dynamic Provisioning DynamicProvisioner should test that deleting a claim before the volume is provisioned deletes the volume. [Suite:openshift/conformance/parallel] [Suite:k8s] [Suite:openshift/smoke-4]

Writing JUnit report to /tmp/artifacts/junit/junit_e2e_20190107-193118.xml

Error: 3 fail, 521 pass, 97 skip (28m42s)
2019/01/07 19:31:18 Container test in pod e2e-aws failed, exit code 1, reason Error

Checking the promotion test-grid, the first two are known flakes. But the sig-storage error hasn't happened in promotion CI. Is that a real issue with this update-payload/RHCOS combination?

[wking]

More details on the sig-storage failure:

Jan  7 19:25:37.497: INFO: Running AfterSuite actions on node 1
fail [k8s.io/kubernetes/test/e2e/storage/volume_provisioning.go:585]: Expected error:
    <*errors.errorString | 0xc420095560>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred

Jan 07 19:20:18.229 W persistentvolume=pvc-4412cf43-12b1-11e9-aa77-0e19e50dd334 Error deleting EBS volume "vol-0212e228e7ba6ebc2" since volume is in "creating" state
...
Jan 07 19:20:24.626 W persistentvolume=pvc-47b5511a-12b1-11e9-aa77-0e19e50dd334 Error deleting EBS volume "vol-0b3abd615fd4c8333" since volume is in "creating" state
Jan 07 19:21:30.431 W persistentvolume=pvc-44c3aaec-12b1-11e9-9518-0a83a7960b64 Error deleting EBS volume "vol-0354240e5b3da2362" since volume is currently attached to "i-0f82edec1140e60b7"
Jan 07 19:22:39.479 I ns=openshift-kube-apiserver-operator deployment=openshift-kube-apiserver-operator Allowed registries for import changed to []
Jan 07 19:22:54.361 W persistentvolume=pvc-48c56170-12b1-11e9-9518-0a83a7960b64 Error deleting EBS volume "vol-0c9b1b840d14daa34" since volume is currently attached to "i-0f82edec1140e60b7"

failed: (5m24s) 2019-01-07T19:25:37 "[sig-storage] Dynamic Provisioning DynamicProvisioner should test that deleting a claim before the volume is provisioned deletes the volume. [Suite:openshift/conformance/parallel] [Suite:k8s] [Suite:openshift/smoke-4]"

That smells like a flake to me, so I'll go ahead and push the release now. In case it gets us pretty, green CI, I'll give it one more shot in the meantime ;)

/retest

[ashcrow]

I've been seeing a lot of failures today as well. Likely a flake.

[openshift-ci-robot]

@wking: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws	76f91bd	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]

This time around:

Flaky tests:

[Feature:DeploymentConfig] deploymentconfigs with custom deployments [Conformance] should run the custom deployment steps [Suite:openshift/conformance/parallel/minimal]
[sig-auth] ServiceAccounts should allow opting out of API token automount  [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]

Writing JUnit report to /tmp/artifacts/junit/junit_e2e_20190107-204134.xml

Error: 2 fail, 522 pass, 97 skip (30m59s)

So between the two runs, all of the tests passed ;). And 0.9.1 is out with this content.