-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bootkube: Pass etcd images into MCO bootstrap #1194
bootkube: Pass etcd images into MCO bootstrap #1194
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is different compared to other images. It would be nice if we keep the env like others.
This was a missed corresponding change after openshift/machine-config-operator@6f0f3ff landed. Ref: openshift/machine-config-operator#367
2885cf1
to
658402b
Compare
OK, I reworked it. /test e2e-aws |
Ah OK...running with this locally I see on the master:
|
The image we're trying to switch to has it in `/usr/bin`, let's just search `$PATH`. Ref: openshift/installer#1194
/retest |
openshift/machine-config-operator#384 merged Let's try again /retest |
Yeah but it's not in an update payload yet AIUI - last accepted one was ~7 hours ago: https://origin-release.svc.ci.openshift.org/ (I think installer pulls latest accepted right?) |
Master builds default to latest accepted, but CI is latest master images (regardless of promotion gating). |
Oh god the matrix of combinations I need to understand just expanded... |
from e2e-aws level=error msg="Error: Error applying plan:"
level=error
level=error msg="1 error occurred:"
level=error msg="\t* module.bootstrap.aws_s3_bucket.ignition: 1 error occurred:"
level=error msg="\t* aws_s3_bucket.ignition: Error creating S3 bucket: TooManyBuckets: You have attempted to create more buckets than allowed"
level=error msg="\tstatus code: 400, request id: C0118BD0E3019AFE, host id: ykgc+MQizNapIl4gb3lnfWH89zNlDT7q0t8L5r+eFAFy+yxDL5e35BKHE2YpEmynR++Ar9DnTDs=" feels like need to wait for sometime before we retest |
/test e2e-aws |
Can this get approved+lgtm so it merges when tests start passing? |
It would be nice if can try this patch locally and paste that here to make sure this works.. that's why i was trying to wait for atleast one successful ci run... |
In that last run though the Specifically:
We just died due to storage test flakes AFAICS. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, cgwalters 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:
Approvers can indicate their approval by writing |
/retest |
@cgwalters: The following tests 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. 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. |
I've filed openshift/etcd#3 to lay the groundwork for replacing our current, hard-coded |
This was a missed corresponding change after
openshift/machine-config-operator@6f0f3ff
landed.
Ref: openshift/machine-config-operator#367