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

Bug 1821286: Unstarted members cannot be blank in the log/event messages #318

Merged

Conversation

retroflexer
Copy link
Contributor

@retroflexer retroflexer commented Apr 22, 2020

etcd doesn't store the name for the unstarted members. It is initialized only when the etcd is started. So, when reporting unstarted members, currently the message appears with blank name, which can be confusing. This PR attempts to fill the name with hostname (or IP address) extracted from peer URL for the unstarted members.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 22, 2020
Copy link
Contributor

@alaypatel07 alaypatel07 left a comment

Choose a reason for hiding this comment

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

as per team discussion, overall idea looks good, added few nits inline

pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
@retroflexer retroflexer force-pushed the fix-unstarted-member-name branch 3 times, most recently from 63b93c2 to 6b02ba5 Compare April 23, 2020 13:42
@retroflexer retroflexer changed the title [wip] Unstarted members cannot be blank in the log/event messages Bug 1821286: Unstarted members cannot be blank in the log/event messages Apr 23, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/high and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Apr 23, 2020
@openshift-ci-robot
Copy link

@retroflexer: This pull request references Bugzilla bug 1821286, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1821286: Unstarted members cannot be blank in the log/event messages

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 23, 2020
@openshift-ci-robot
Copy link

@retroflexer: This pull request references Bugzilla bug 1821286, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1821286: Unstarted members cannot be blank in the log/event messages

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.

@retroflexer
Copy link
Contributor Author

/retest

3 similar comments
@retroflexer
Copy link
Contributor Author

/retest

@retroflexer
Copy link
Contributor Author

/retest

@retroflexer
Copy link
Contributor Author

/retest

@retroflexer
Copy link
Contributor Author

/test e2e-azure

@alaypatel07
Copy link
Contributor

lgtm, leaving the tag for @hexfusion if he has comments. Thanks

Copy link
Contributor

@hexfusion hexfusion left a comment

Choose a reason for hiding this comment

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

@retroflexer, in general, I think we can define an unstarted member as something like

fmt.Sprintf("UNSTARTED-NAME-PENDING.%s", hostname)

making it more clear why we see the naming?

pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
@retroflexer
Copy link
Contributor Author

@retroflexer, in general, I think we can define an unstarted member as something like

fmt.Sprintf("UNSTARTED-NAME-PENDING.%s", hostname)

making it more clear why we see the naming?

I agree. But my only apprehension is that with IPv6 it could become very lengthy and unreadable.

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. and removed bugzilla/high labels Apr 29, 2020
Copy link
Contributor

@hexfusion hexfusion left a comment

Choose a reason for hiding this comment

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

few more notes

pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
pkg/etcdcli/etcdcli.go Outdated Show resolved Hide resolved
@hexfusion
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 30, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2020
@hexfusion
Copy link
Contributor

/test e2e-aws

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 30, 2020

@retroflexer: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-disruptive cdade9b link /test e2e-aws-disruptive
ci/prow/e2e-azure cdade9b link /test e2e-azure

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.

@hexfusion
Copy link
Contributor

/skip

@openshift-merge-robot openshift-merge-robot merged commit ac55a8b into openshift:master Apr 30, 2020
@openshift-ci-robot
Copy link

@retroflexer: All pull requests linked via external trackers have merged: openshift/cluster-etcd-operator#290, openshift/cluster-etcd-operator#318. Bugzilla bug 1821286 has been moved to the MODIFIED state.

In response to this:

Bug 1821286: Unstarted members cannot be blank in the log/event messages

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.

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants