kubernetesbare-metalk8s-sig-cluster-lifecycleawskubesprayhigh-availabilityansiblekubernetes-clustergce
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
dc9d3bf39d
ant31-patch-1
component_hash_update/master
component_hash_update/release-2.28
floryut-patch-1
lean/pre-commit-hook-2
master
master-patch-updates
optional-coredns
packet-test
pre-commit-hook
reduce-vm-requests
release-2.10
release-2.11
release-2.12
release-2.13
release-2.14
release-2.15
release-2.16
release-2.17
release-2.18
release-2.19
release-2.20
release-2.21
release-2.22
release-2.23
release-2.24
release-2.25
release-2.26
release-2.27
release-2.28
release-2.7
release-2.8
release-2.9
remove-ci-ok-to-test
revert-11831-ipv6only
symlinketcd
test-CI
test-ci
test-precommit
test/flatcar-4081
update-approvers-ant31
1.3.0
1.3.0_k1.1.3
1.4.0
1.5.0
test-tag-1
v1.0
v1.0.0
v1.0.1
v1.1
v1.1.0
v1.1.3
v2.0.0
v2.0.1
v2.1.0
v2.1.1
v2.1.2
v2.10.0
v2.10.3
v2.10.4
v2.11.0
v2.11.1
v2.11.2
v2.12.0
v2.12.1
v2.12.10
v2.12.2
v2.12.3
v2.12.4
v2.12.5
v2.12.6
v2.12.7
v2.12.8
v2.12.9
v2.13.0
v2.13.1
v2.13.2
v2.13.3
v2.13.4
v2.14.0
v2.14.1
v2.14.2
v2.15.0
v2.15.1
v2.16.0
v2.17.0
v2.17.1
v2.18.0
v2.18.1
v2.18.2
v2.19.0
v2.19.1
v2.2.0
v2.2.1
v2.20.0
v2.21.0
v2.22.0
v2.22.1
v2.22.2
v2.23.0
v2.23.1
v2.23.2
v2.23.3
v2.24.0
v2.24.1
v2.24.2
v2.24.3
v2.25.0
v2.25.1
v2.26.0
v2.27.0
v2.27.1
v2.28.0
v2.28.1
v2.3.0
v2.4.0
v2.5.0
v2.6.0
v2.7.0
v2.8.0
v2.8.1
v2.8.2
v2.8.3
v2.8.4
v2.8.5
v2.9.0
Retrying to load conntrack modules was bound to fail due to the way, the current `when` conditions were utilized. It was based on the assumption, that in case of success, the registered variable would have an `rc` attribute with the value `0`. Unfortunately, the `rc` attribute is only present in case of a failure, where it's value is >1. The result of `community.general.modprobe` in case of success looks like this: ``` { "changed": false, "msg": "All items completed", "results": [ { "ansible_loop_var": "item", "changed": false, "failed": false, "invocation": { "module_args": { "name": "nf_conntrack", "params": "", "persistent": "present", "state": "present" } }, "item": "nf_conntrack", "name": "nf_conntrack", "params": "", "state": "present" } ], "skipped": false } ``` While it looks like this in case of a failure: ``` { "changed": false, "failed": true, "msg": "One or more items failed", "results": [ { "ansible_loop_var": "item", "attempts": 3, "changed": false, "failed": true, "invocation": { "module_args": { "name": "nf_conntrack_doesnotexist", "params": "", "persistent": "present", "state": "present" } }, "item": "nf_conntrack_doesnotexist", "msg": "modprobe: FATAL: Module nf_conntrack_doesnotexist not found in directory /lib/modules/5.14.0-570.32.1.el9_6.x86_64\n", "name": "nf_conntrack_doesnotexist", "params": "", "rc": 1, "state": "present", "stderr": "modprobe: FATAL: Module nf_conntrack_doesnotexist not found in directory /lib/modules/5.14.0-570.32.1.el9_6.x86_64\n", "stderr_lines": [ "modprobe: FATAL: Module nf_conntrack_doesnotexist not found in directory /lib/modules/5.14.0-570.32.1.el9_6.x86_64" ], "stdout": "", "stdout_lines": [] } ], "skipped": false } ``` By evaluating `failed` instead, this issue can be prevented. See also: - https://github.com/kubernetes-sigs/kubespray/issues/11340 Co-authored-by: Max Gautier <mg@max.gautier.name> |
1 month ago | |
---|---|---|
.. | ||
kube.py | kube.py support kubeconfig (#9982) | 2 years ago |