Fix Calico Installation

[nothingcompare2u]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

• when installing calico, the kubespray job may go with the follwing error message:

3:40AM: changed: [g-master5]
3:40AM: Friday 12 May 2023  07:40:42 +0000 (0:00:00.765)       0:45:24.769 ************
3:41AM:
3:41AM: TASK [network_plugin/calico : Calico | Create Calico Kubernetes datastore resources] ***
3:41AM: fatal: [g-master1]: FAILED! => {"changed": false, "msg": "error running kubectl (/usr/local/bin/kubectl apply --force --filename=/etc/kubernetes/kdd-crds.yml) command (rc=1), out='customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/caliconodestatuses.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/ipreservations.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created\ncustomresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org created\n', err='Error from server: error when creating \"/etc/kubernetes/kdd-crds.yml\": etcdserver: request timed out\n'"}
3:41AM:
3:41AM: NO MORE HOSTS LEFT *************************************************************
3:41AM:
3:41AM: PLAY RECAP *********************************************************************
3:41AM: g-master1                  : ok=499  changed=128  unreachable=0    failed=1    skipped=559  rescued=0    ignored=1
3:41AM: g-master2                  : ok=367  changed=101  unreachable=0    failed=0    skipped=507  rescued=0    ignored=1

• So just retry it.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[Calico] Fix installation while applying CRD

[k8s-ci-robot]

Hi @hangscer8. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[MrFreezeex]

Thanks for the contribution, lgtm though I would wait for the CI issue to be resolved before adding lgtm label (apparently we have a problem again with the CI :(). Your error looks a bit suspicious TBH though etcdserver: request timed out as there is a wait for etcd task above that... Eitherway there is a bunch of retries everywhere in the calico code so I'm fine with this.

[MrFreezeex]

Hi again, could you rebase your PR please? I believe the CI issues should be resolved now 🙏

[floryut]

@hangscer8 Thank you for the PR
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, hangscer8

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 [floryut]

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

[oomichi]

Thanks for doing that.

/lgtm