Update Calico to v3.27.3

[hakman]

No description provided.

[justinsb]

From one the mount-bpffs logs: calico-node: error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory

It's on all the nodes, but e.g. https://gcsweb.k8s.io/gcs/kubernetes-jenkins/pr-logs/pull/kops/16363/pull-kops-e2e-cni-calico-ipv6/1759139852261003264/artifacts/cluster-info/kube-system/calico-node-8xp9w/

Maybe we need to install libpcap in nodeup when using calico?

[hakman]

/test pull-kops-kubernetes-e2e-ubuntu-gce-build

[hakman]

/test pull-kops-kubernetes-e2e-ubuntu-gce-build

[hakman]

Related to projectcalico/calico#8541. We will wait for v3.27.3.

[k8s-ci-robot]

@hakman: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-cni-calico-ipv6	b5813b2	link	false	/test pull-kops-e2e-cni-calico-ipv6

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[hakman]

@rifelpet Could you check this error with IPv6? Looks related to #16448.

Error: error determining default DNS zone: error querying zones:
error listing hosted zones: operation error Route 53:
ListHostedZones, failed to resolve service endpoint, endpoint rule error,
Invalid Configuration: Missing Region

[rifelpet]

Yes I'll take a look. The old code wasn't specifying a region either so there must be a behavioral change in v2 that isnt documented in the migration guide.

https://github.com/kubernetes/kops/pull/16448/files#diff-8b59c898fa44da5fbbb0cf9868a918db03cdefe41c6855ef5840762ba9837455

it only happens in the ipv6 job too.

[hakman]

Yes I'll take a look. The old code wasn't specifying a region either so there must be a behavioral change in v2 that isnt documented in the migration guide.

https://github.com/kubernetes/kops/pull/16448/files#diff-8b59c898fa44da5fbbb0cf9868a918db03cdefe41c6855ef5840762ba9837455

it only happens in the ipv6 job too.

Exactly. Could we merge this and the cherry-pick in the mean time?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rifelpet]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment