Marco Braga
Marco Braga
/test pull-cloud-provider-aws-e2e
/test pull-cloud-provider-aws-e2e
unrelated failure in the lb-internal tests which expects to fail (hairpinning). Checking if it was flake: /test pull-cloud-provider-aws-e2e
Review comments addressed, new e2e added and e2e passing on CI. This PR is ready for review. PTAL? Thanks
e2e test [`[cloud-provider-aws-e2e] loadbalancer CLB with managed Security Group must update to BYO Security Group` was added](https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/cloud-provider-aws/1209/pull-cloud-provider-aws-e2e/1952377003214639104#1:build-log.txt%3A2104), here are the logs of the step which performs the Service update/checks: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/cloud-provider-aws/1209/pull-cloud-provider-aws-e2e/1952377003214639104#1:build-log.txt%3A2140-2167...
/test pull-cloud-provider-aws-e2e
> FAIL: expected managed security group "sg-0a917e4b14501635f" removed by controller, got "sg-0a917e4b14501635f" Checking if I need to enhance the controller update the sg: /test pull-cloud-provider-aws-e2e
increase verbosity /test pull-cloud-provider-aws-e2e
e2e job green. I am also leaving the e2e more verbose in case of test network failures, helping devs troubleshooting easier CI logs of internal connectivity / internal LB. LMK...
Converting to draft while I return on it to rebase and run deepen investigation on e2e failures.