[IEC-15] Investigate failing Aggreg test in kube-conformance e2e.test Created: 22/Jul/19  Updated: 18/Feb/20  Resolved: 18/Feb/20

Status: Done
Project: Integrated Edge Cloud
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: Alexandru Avadanii Assignee: Alexandru Avadanii
Resolution: Done Votes: 0
Labels: Release_2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to VAL-8 Run k8s conformance test for arm64 Done

 Description   

Even after bumping the k8s tests to 1.15.x baseline, which includes proper support for the etcd container image selection (previous versions hardcoded an x86 specific image), the Aggregation layer testcase still fails on IEC, for both x86_64 and aarch64 architectures.

This might be a configuration issue or an incompatible testing suite configuration, but we're still investigating the exact rootcause.

 Comments   
Comment by Cristina Pauna [ 18/Feb/20 ]

Using the same k8s version both for the cluster and the tests fixes the issue

Comment by Alexandru Avadanii [ 30/Jul/19 ]

Quick update:

  • up to and including K8s 1.13, the Aggreg test was not part of the Conformance suite, hence we never tested it by default, since we used e2e.test from K8s 1.11 or 1.13;
  • the test is failing with K8s 1.13 and 1.14 / kubernetes-cni 0.6.0/0.7.5 on all tested architectures (x86_64, aarch64);
  • the test is passing with K8s 1.15 (1.15.1) / kubernetes-cni 0.7.5;
  • it looks like CNI is not responsible for the issue;

So, bumping K8s to 1.15 should automatically fix the problem.

I will continue the investigation a bit, hopefully I can find the exact rootcause.

Generated at Sat Feb 10 06:02:09 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.