failed task

[dimsunv]

OS Centos-Stream 8

TASK [bootstrap-os : Install libselinux python package] ********************************************************************************************************************* [WARNING]: Updating cache and auto-installing missing dependency: python3-apt fatal: [node-2]: FAILED! => {"changed": false, "cmd": "apt-get update", "msg": "[Errno 2] No such file or directory: b'apt-get': b'apt-get'", "rc": 2, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} fatal: [node-3]: FAILED! => {"changed": false, "cmd": "apt-get update", "msg": "[Errno 2] No such file or directory: b'apt-get': b'apt-get'", "rc": 2, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} fatal: [node-1]: FAILED! => {"changed": false, "cmd": "apt-get update", "msg": "[Errno 2] No such file or directory: b'apt-get': b'apt-get'", "rc": 2, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

[silverfisk]

I get the same problem on CentOS 9. Running Ansible from Fedora 37 ansible [core 2.12.5] python version = 3.11.4 (main, Jun 7 2023, 00:00:00) [GCC 12.3.1 20230508 (Red Hat 12.3.1-1)] jinja version = 3.1.2 libyaml = True

[rcbandit111]

Any progress on this? I get the same issue?

[VannTen]

I don't think we support centos stream.

Anyhow, can you provide the info asked in the bug report template ? There is not enough info here to draw any conclusions.

[VannTen]

/triage needs-information

[directdevice]

Seems to be a duplicate of #1047 I can barely expect "apt-get" to be present in any CentOS based distribution Thus, the wrong node OS version might be taken from a previously cached fact

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[VannTen]

/close Per above

[k8s-ci-robot]

@VannTen: Closing this issue.

In response to this:

/close Per above

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.