#TRT-671 | issue | azure-sdn-serial-techpreview using unexpected disruption values CLOSED | |
Issue 14931036: azure-sdn-serial-techpreview using unexpected disruption values Description: https://sippy.dptools.openshift.org/sippy-ng/jobs/4.12?filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22periodic-ci-openshift-release-master-ci-4.12-e2e-azure-sdn-techpreview-serial%22%7D%5D%7D is often on a couple disruption backends. However the value it claims is expected does not match the data file. Example: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.12-e2e-azure-sdn-techpreview-serial/1590170635655450624 {code} [sig-api-machinery] disruption/cache-kube-api connection/reused should be available throughout the test expand_less 2h19m21s { cache-kube-api-reused-connections was unreachable during disruption testing for at least 2s of 2h19m21s (maxAllowed=1s): } {code} {code} ~/go/src/github.com/openshift/origin remotes/up/release-4.12* 6s ❯ cat ./pkg/synthetictests/allowedbackenddisruption/query_results.json | jq '.[] | select(.Platform == "azure") | select(.FromRelease == "") | select(.BackendName == "cache-kube-api-reused-connections") | select(.Network == "sdn")' { "BackendName": "cache-kube-api-reused-connections", "Release": "4.12", "FromRelease": "", "Platform": "azure", "Architecture": "amd64", "Network": "sdn", "Topology": "ha", "P95": "1.6499999999999908", "P99": "2.9299999999999979" } {code} Where is the 1s limit coming from, it looks like it should be about 3? Is something handling techpreview differently? File is also last updated Oct 21 in release-4.12, soon to be rebased from master we expect. Status: CLOSED |
Found in 0.00% of runs (0.00% of failures) across 258085 total runs and 10716 jobs (21.95% failed) in 123ms - clear search | chart view - source code located on github