Bump pinned release to 4.2.0-0.ci-2019-07-31-123929-kni.0

[stbenjam]

This won't be the final release, I just want to see if CI is OK. Once openshift/installer#2004 makes it into a CI build, I'll build a new release with that. Hopefully this afternoon.

[e-minguez]

Can we jump to 2019-07-30-141752 please? It includes the ability to use a custom ceph cluster name in rook (openshift/console#2206)

[stbenjam]

Can we jump to 2019-07-30-141752 please? It includes the ability to use a custom ceph cluster name in rook (openshift/console#2206)

Sure, we'll actually have something later than that. I'm waiting on the PR mentioned above to be merged, and a CI release with those changes, and then I'll use that.

[metal3ci]

Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/966/

[stbenjam]

Pinned to 4.2.0-0.ci-2019-07-30-172629-kni.0, openshift CI is still running on that release, but I figure we can run ours concurrently.

[metal3ci]

Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/968/

[stbenjam]

@russellb It doesn't look like Ingress came up, do we need some other change?

Jul 30 20:47:40 |  level=fatal msg="failed to initialize the cluster: Some cluster operators are still updating: authentication, ingress, monitoring"

[stbenjam]

I put back the ingress controller template, as it doesn't seem the scheduler change was enough.

[russellb]

I put back the ingress controller template, as it doesn't seem the scheduler change was enough.

It's not enough on its own. Our install config says there is 1 worker, so it won't turn on schedulable masters by default. We need to do that manually, or deploy with 0 workers and add a worker as a post-install step.

[stbenjam]

I put back the ingress controller template, as it doesn't seem the scheduler change was enough.

It's not enough on its own. Our install config says there is 1 worker, so it won't turn on schedulable masters by default. We need to do that manually, or deploy with 0 workers and add a worker as a post-install step.

Ah ok, I guess we can deal with it in a separate PR and just get the new image in for now?

[russellb]

yes

…

On Wed, Jul 31, 2019 at 10:20 AM Stephen Benjamin ***@***.***> wrote: I put back the ingress controller template, as it doesn't seem the scheduler change was enough. It's not enough on its own. Our install config says there is 1 worker, so it won't turn on schedulable masters by default. We need to do that manually, or deploy with 0 workers and add a worker as a post-install step. Ah ok, I guess we can deal with it in a separate PR and just get the new image in for now? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#710?email_source=notifications&email_token=AACLQCRHZNWFHHVEEN2B4HDQCGNRZA5CNFSM4IH4SLE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3HM5VI#issuecomment-516869845>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACLQCURRJEIPX25LDRKTLDQCGNRZANCNFSM4IH4SLEQ> .

-- Russell Bryant

[stbenjam]

I've bumped to 4.2.0-0.ci-2019-07-31-123929-kni.0, so we get the changes that were merged last night for moving bootstrap assets to MCO.

[metal3ci]

Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/975/