[ELIOT-41] [BluVal-Validation-K8S-Conformance-Testcase-Issue: SIG-APPS] Created: 28/Aug/19  Updated: 21/Oct/19  Resolved: 21/Oct/19

Status: Done
Project: Edge Lightweight and IoT
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: Abhijit Dasgupta Assignee: Abhijit Dasgupta
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: ELIOT - Release 2

 Description   

[sig-apps] Daemon set [Serial] should rollback without unnecessary restarts [Conformance]



 Comments   
Comment by Abhijit Dasgupta [ 21/Oct/19 ]

The test case is passed.
After consulting with the Validation team, and taking the new blu val test case suite, had to untaint the Master node, as the test case pass case criteria was the k8s cluster should have minimum two nodes with Ready state and also can be scheduled.

Below is the suggestion from Validation team :-

Hi Abhijit,

The test is failing with the error "Conformance test suite needs a cluster with at least 2 nodes". You can open the sonobuoy archive and check plugins/e2e/results/global/e2e.log for the full log.

I see that your cluster has 2 nodes, so it's possible that the issue is with reading the number of the nodes. The code of the test is at [1] and it uses function GetReadySchedulableNodesOrDie() to retrieve the nodes.

Looking at how the function is implemented [2], it looks like both nodes need to be ready and schedulable. Can you manually verify this is the case?

In any case, this doesn't look like it's a validation issue, more likely it's an issue with the cluster.

Thanks,

Cristina

[1] https://github.com/kubernetes/kubernetes/blob/v1.15.4/test/e2e/apps/daemon_set.go#L386

[2] https://github.com/kubernetes/kubernetes/blob/v1.15.4/test/e2e/framework/util.go#L2621

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Closing the Jira Ticket

Comment by Abhijit Dasgupta [ 09/Oct/19 ]

Have send mail to Validation team, checking what should be done to fix the issue.

Generated at Sat Feb 10 05:53:27 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.