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

Flake Test: TestMultiNode/serial/RestartMultiNode: node X has unwanted condition "Ready" : Reason "NodeStatusUnknown" Message: "Kubelet stopped posting node status.". will try. #10640

Closed
medyagh opened this issue Feb 26, 2021 · 6 comments · Fixed by #10758
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@medyagh
Copy link
Member

medyagh commented Feb 26, 2021

Example https://storage.googleapis.com/minikube-builds/logs/10638/8b10177/Docker_Linux.html#fail_TestMultiNode%2fserial%2fRestartMultiNode

	I0226 19:02:29.778088   83784 node_ready.go:53] node "multinode-20210226185242-6625-m02" has unwanted condition "Ready" : Reason "NodeStatusUnknown" Message: "Kubelet stopped posting node status.". will try. 
	I0226 19:02:29.781519   83784 node_ready.go:53] node "multinode-20210226185242-6625-m02" has unwanted condition "Ready" : Reason "NodeStatusUnknown" Message: "Kubelet stopped posting node status.". will try. 
	I0226 19:02:29.781569   83784 node_ready.go:38] duration metric: took 4m0.012501852s to wait for WaitForNodeReady...
	I0226 19:02:29.784428   83784 out.go:119] 
	W0226 19:02:29.784579   83784 out.go:181] X Exiting due to GUEST_START: wait 6m0s for node: waiting for node to be ready: wait node ready: timed out waiting for the condition
	X Exiting due to GUEST_START: wait 6m0s for node: waiting for node to be ready: wait node ready: timed out waiting for the condition
	W0226 19:02:29.784629   83784 out.go:181] * 
	* 
	W0226 19:02:29.784676   83784 out.go:181] * If the above advice does not help, please let us know: 
	* If the above advice does not help, please let us know: 
	W0226 19:02:29.784723   83784 out.go:181]   - https://github.com/kubernetes/minikube/issues/new/choose
	  - https://github.com/kubernetes/minikube/issues/new/choose
	I0226 19:02:29.787189   83784 out.go:119] 
** /stderr **
@medyagh medyagh added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 26, 2021
@medyagh medyagh added this to the v.1.19.0-candidate milestone Feb 26, 2021
@sharifelgamal sharifelgamal added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 1, 2021
@jiefenghe
Copy link
Contributor

/assign

@medyagh
Copy link
Member Author

medyagh commented Mar 1, 2021

thanks @jiefenghe for talking this, please let me know if u have any questions
@prezha might have some insight on this, please feel free to brainstorm togheter

@ilya-zuyev
Copy link
Contributor

It looks like the tests started to fail on Feb 16

@ilya-zuyev
Copy link
Contributor

@medyagh
Copy link
Member Author

medyagh commented Mar 3, 2021

	t.Run("serial", func(t *testing.T) {
		tests := []struct {
			name      string
			validator validatorFunc
		}{
			{"FreshStart2Nodes", validateMultiNodeStart},
			{"AddNode", validateAddNodeToMultiNode},
			{"ProfileList", validateProfileListWithMultiNode},
			{"StopNode", validateStopRunningNode},
			{"StartAfterStop", validateStartNodeAfterStop},
			{"DeleteNode", validateDeleteNodeFromMultiNode},
			{"StopMultiNode", validateStopMultiNodeCluster},
			{"RestartMultiNode", validateRestartMultiNodeCluster},
			{"ValidateNameConflict", validatNameConflict},
		}

so it happens after StopMultiNode
and then Starting it again
but not on a Normal FreshStart2Nodes

@prezha
Copy link
Contributor

prezha commented Mar 9, 2021

@jiefenghe i've created pr #10758 describing what i've found and proposing solution, please have a look and share your thoughts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants