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.

Sign up for GitHub

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

Jump to bottom

migrate-if-needed.sh fails to remove etcd2 data when migrating from etcd 3.0->3.1 due to missing --endpoints flag #59667

Closed
jpbetz opened this issue Feb 9, 2018 · 1 comment
Closed

migrate-if-needed.sh fails to remove etcd2 data when migrating from etcd 3.0->3.1 due to missing --endpoints flag #59667

jpbetz opened this issue Feb 9, 2018 · 1 comment
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@jpbetz
Copy link
Contributor

jpbetz commented Feb 9, 2018

This was noticed when adding tests to #59298. One of the tests failed with an "unable to reach etcd error". Adding -endpoints "http://127.0.0.1:${ETCD_PORT}" to migrate-if-needed.sh to the etcdctl rm --recursive fixed the issue.

Creating this issue for posterity so the issue and it's fix are tracked.
@k8s-ci-robot
Copy link
Contributor

@jpbetz: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

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.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 9, 2018
@jpbetz jpbetz closed this as completed Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpbetz @k8s-ci-robot