[VAL-81] kube-sonobuoy container doesn't start in timeout(20s) Created: 31/Oct/19  Updated: 09/Dec/19  Resolved: 09/Dec/19

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

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


 Description   

After 20s since starting the containers they are still not found.

Conformance.Conformance :: Run k8s conformance test using sonobuoy
==============================================================================
Run Sonobuoy Conformance Test error retrieving results: unable to upgrade connection: container not found ("kube-sonobuoy")

 

 Comments   
Comment by Valentin Radulescu [ 31/Oct/19 ]

Hi,

Timeout has already been increased but still the issue reproduces.

See https://gerrit.akraino.org/r/c/validation/+/1820

/Valentin Radulescu

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