search

rancher / qa-tasks

List of QA Backlog
1 stars 1 forks source link

Add wait time to ingress validation allowing even when ingress ip is present during upgrade. #1499

Open ShylajaDevadiga opened 3 months ago

ShylajaDevadiga commented 3 months ago

Automation currently passes ingress test as the ingress ip is present soon after upgrade. We need to allow ingress to settle before validation it. Issue reference: https://github.com/rancher/rke2/issues/6510

$ kubectl get ing -A
NAMESPACE      NAME           CLASS    HOSTS          ADDRESS       PORTS   AGE
test-ingress   test-ingress   <none>   foo1.bar.com   <REDACTED>  80      45s

➜  ~curl -s --header host:foo1.bar.com http://<public ip>/name.html
test-ingress-rz7kd

After upgrade

➜  ~ curl -s --header host:foo1.bar.com http://<public ip>/name.html
test-ingress-rz7kd

$ kubectl get ing -A
NAMESPACE      NAME           CLASS    HOSTS          ADDRESS   PORTS   AGE
test-ingress   test-ingress   <none>   foo1.bar.com             80      4m24s

Fails after a while as IP is removed

➜  ~ curl -s --header host:foo1.bar.com http://<public ip>/name.html
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
fmoral2 commented 2 months ago

after some exhaustive testing we came to conclusion that just setting this to be run in the end, its enough

https://github.com/rancher/distros-test-framework/pull/169