-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
disttask: init node meta inside domain #49996
Conversation
Hi @D3Hunter. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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. |
/run-check-issue-triage-complete |
@@ -132,13 +132,15 @@ func (m *Manager) initMeta() (err error) { | |||
return err | |||
} | |||
|
|||
// InitMeta initializes the meta of the Manager. | |||
// not a must-success step before start manager, manager will try to init meta periodically. | |||
func (m *Manager) InitMeta() error { |
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.
Just rename initMeta to InitMeta?
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.
it's named Init
in the begin, but it's misleading to Start even Init failed, so renamed to InitMeta
will leave it for now
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.
Rest LGTM
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #49996 +/- ##
================================================
- Coverage 72.0631% 68.9309% -3.1323%
================================================
Files 1438 1440 +2
Lines 345762 410775 +65013
================================================
+ Hits 249167 283151 +33984
- Misses 76457 108690 +32233
+ Partials 20138 18934 -1204
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lance6716, tangenta, ywqzzy 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 |
/test tiprow_fast_test |
@D3Hunter: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In 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. |
@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an In 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. |
@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an In 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. |
/ok-to-test |
/unhold |
/retest |
What problem does this PR solve?
Issue Number: close #49990
Problem Summary:
What changed and how does it work?
we init node meta inside domain, as create task requires at least 1 managed node inited after #49875 merged
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.