Skip to content
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

describe etcd 4.3 to 4.4 upgrade/downgrade #207

Merged
merged 2 commits into from Feb 19, 2020

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Feb 12, 2020

This leaves us in an interesting intermediate spot. We have a good story for the final upgrade/downgrade, but the intermediate state fails because we have a cluster-etcd-operator PR for step 1 and a machine-config-operator PR for step 4, but we cannot merge both at the same time.

Without the cluster-etcd-operator PR, the machine-config-operator PR won't install or upgrade because no etcd is present. Without the machine-config-operator PR, the cluster-etcd-operator PR cannot pass an upgrade because the machineconfigpool is permanently degraded.

@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 12, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 12, 2020

1. The 4.4-etcd-staticpod moves the /etcd/kubernetes/manifests/etcd-member.yaml to a backup location before trying to start etcd.
2. This causes the 4.3-machineconfigpool to go degraded because the file that it tries to maintain is gone.
3. If the master node restarts using a 4.3-machineconfigpool, the old /etcd/kubernetes/manifests/etcd-member.yaml will come back.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you sure if MCD works that way. last i checked, if it sees user changed something it owns it just marks the node degraded. and doesn't so anything.

@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 19, 2020
@hexfusion
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 19, 2020
@openshift-merge-robot openshift-merge-robot merged commit 2cb29e1 into openshift:master Feb 19, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, hexfusion

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants