bhouse-nexthop commented on PR #14364: URL: https://github.com/apache/cloudstack/pull/14364#issuecomment-6341615091
@DaanHoogland I went through the Marvin logs for tid-17190, and I don't think this one is caused by the PR. - **What failed:** the assertion at `test_vpc_vpn.py:937`, `Failed to connect between VPCs, see VPN state as Connected`. Both `createVpnConnection` jobs succeeded. The passive side of the redundant pair just never reported `Connected` within the ~60 s `wait_until` window. - **ACLs in play at that point:** only the built-in `default_allow` list on both tiers, i.e. protocol `all` with no ports. The test's port-22 rules come after line 937, so they never got created. - **The PR's effect on those rules:** none. It only changes how a tcp/udp rule with no ports or `0:0` is rendered (`--dport` dropped). An `all` rule without ports renders to the same iptables line before and after. These chains filter tier traffic anyway; the IKE/ESP between the routers' public IPs doesn't go through them. - **Rest of the file passed in the same run:** the other three tests in `test_vpc_vpn.py` passed, including the two non-redundant site-to-site VPN tests (`test_01_vpc_site2site_vpn`, `test_01_vpc_site2site_vpn_multiple_options`). - **Seen elsewhere:** `test_01_redundant_vpc_site2site_vpn` has failed on unrelated PRs, e.g. #14310 (tid-17174, earlier today, 470s), #13884, #12900 and the 4.22 health check #12001. A re-run should tell us more if you'd like to be sure. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
