rhcos: update to 42.80.20190827.1 #2277
Conversation
openshift-ci-robot
added
the
size/L
This rhcos version has a working podman. The current pinned rhcos does not have the backported fix for https://bugzilla.redhat.com/show_bug.cgi?id=1741157. If the etcd health check fails, bootkube continues on regardless instead of retrying. This manifests itself most catastrophically for the baremetal IPI platform, where the first etcd health check fails very quickly as DNS records aren't available yet.
|
/test e2e-aws-upgrade |
|
/retest |
|
/test e2e-azure Just to be safe |
|
/test e2e-aws |
yuqi-zhang
left a comment
yuqi-zhang
left a comment
There was a problem hiding this comment.
/approve
Azure failure is not OS related so I think this update is safe to go
|
/lgtm /retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, stbenjam, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/retest |
|
@stbenjam: The following test failed, say
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. DetailsInstructions 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. |
7 participants
This rhcos version has a working podman. The current pinned rhcos does
not have the backported fix for
https://bugzilla.redhat.com/show_bug.cgi?id=1741157.
If the etcd health check fails, bootkube continues on regardless instead
of retrying. This manifests itself most catastrophically for the
baremetal IPI platform, where the first etcd health check fails very
quickly as DNS records aren't available yet.