-
Notifications
You must be signed in to change notification settings - Fork 463
*: conditionally populate the images configmap with cluster-etcd-operator image #1288
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
*: conditionally populate the images configmap with cluster-etcd-operator image #1288
Conversation
|
/hold testing this manually |
|
/skip |
|
/retest |
|
at a quick glance this seems to be failing on masters only so prob the pr? seems etcd server is taking too long: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1288/pull-ci-openshift-machine-config-operator-master-e2e-aws/5908/artifacts/e2e-aws/pods/openshift-etcd_etcd-member-ip-10-0-137-114.ec2.internal_etcd-member.log |
6f850a1 to
b3235f8
Compare
b3235f8 to
370c2c7
Compare
415d39c to
e3caad8
Compare
e3caad8 to
ad0c14d
Compare
da8bbf6 to
8d9a25c
Compare
Etcd was up but openshift-apiserver had the above error messages, compacted data store, trying again /test e2e-aws |
8d9a25c to
4da3c5a
Compare
0893291 to
bd48395
Compare
|
/retest Please review the full test history for this PR and help us cut down flakes. |
213919b to
91ab6c5
Compare
/retest |
/test e2e-aws-scaleup-rhel7 |
|
digging into the error /hold |
|
/test e2e-gcp-op |
/retest |
EtcdInformer is only used by the MCO pod to reconcile image names. This pulls out the logic of creating etcd informer from the generic controller context to MCO pod start method.
ee499f2 to
c29ebe9
Compare
|
Looks like CI is up again. /retest |
|
/joke |
|
@hexfusion: A red and a blue ship have just collided in the Caribbean. Apparently the survivors are marooned. DetailsIn response to this:
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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alaypatel07, hexfusion, kikisdeliveryservice 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 |
|
/hold cancel |
New, I have not see this... last round passed /test e2e-gcp-op |
|
@alaypatel07: 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. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/cherrypick fcos |
|
@vrutkovs: new pull request created: #1413 DetailsIn response to this:
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. |
This adds a flag to MCO for cluster-etcd-operator image and hardcodes
the value to
"".This PR conditionally populates the cluster-etcd-operator image only
if the etcd custom resource exists and if it has a spec field set as
managementState: Managed. It is the same mechanism usedin the installer. This will make sure that the MC rendered during the initial.
boot with the value coming in from the installer flag is always same
as one generate in the sync loop.
With this, we can use a single knob in cluster-etcd-operator
project to test the bootstrap process in CI with cluster-etcd-operator
enabled.
The existence of cluster-etcd-operator image is used to render static
etcd pod yaml. This PR will be followed by another PR which introduces
a boolean flag to be used for conditional rendering of the static pod image.
It will be a more readable way of achieving the same means.