[VAL-73] k8s conformance tests forcing pod kube-system to exist Created: 28/Oct/19  Updated: 06/Nov/19  Resolved: 06/Nov/19

Status: Done
Project: Validation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Yolanda Robla Mota Assignee: Valentin Radulescu
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This is a pod that is depending on implementation. For openshift, this pod does not exist, so it's causing the validation to fail. I had to manually create a dummy kube-system pod for test to pass.
So this test should be optional, or allow for some specific test depending on the platform. In openshift is not valid to check for pods, but better to check for cluster operators.



 Comments   
Comment by Valentin Radulescu [ 06/Nov/19 ]

Hi,

I think this can be closed. The patch has been merged.

Valentin Radulescu

Comment by Valentin Radulescu [ 01/Nov/19 ]

Hi,

I sent a first patch for review:
https://gerrit.akraino.org/r/c/validation/+/1899

Valentin Radulescu

Comment by Cristina Pauna [ 28/Oct/19 ]

Ok, thanks for the clarification. We do that test only to verify we have connectivity, I think we can use a more generic kubectl command for that (like getting the version, or the nodes).

Comment by Yolanda Robla Mota [ 28/Oct/19 ]

This is not even failing in sonobuoy, it's before it. The code that is failing is: https://github.com/akraino-edge-stack/validation/blob/master/tests/k8s/conformance/conformance.robot#L83

Comment by Cristina Pauna [ 28/Oct/19 ]

Hi Yolanda,

Can you please specify the name of the test that is failing and attach the sonobuoy log archive with the failure?

Thanks,

Cristina

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