search

kubernetes-sigs / kubespray

Deploy a Production Ready Kubernetes Cluster
Apache License 2.0
16.01k stars 6.44k forks source link

Fedora CoreOS fails to install PyYAML #10885

Closed Tsuguya closed 6 days ago

Tsuguya commented 8 months ago

What happened?

Failed to execute task Helm | Install PyYaml.

What did you expect to happen?

Complete the installation or skip it.

How can we reproduce it (as minimally and precisely as possible)?

Run the installation with helm_enabled=true

OS

Linux 6.6.9-200.fc39.aarch64 aarch64 NAME="Fedora Linux" VERSION="39.20240112.3.0 (CoreOS)" ID=fedora VERSION_ID=39 VERSION_CODENAME="" PLATFORM_ID="platform:f39" PRETTY_NAME="Fedora CoreOS 39.20240112.3.0"

Version of Ansible

ansible [core 2.15.8]

Version of Python

Python 3.12.1

Version of Kubespray (commit)

c9a44e408

Network plugin used

calico

Full inventory with variables

No response

Command used to invoke ansible

ansible-playbook -i inventory/mycluster/hosts.yaml cluster.yml -b -vv -e kubelet_rotate_server_certificates=true

Output of ansible run

TASK [kubernetes-apps/helm : Helm | Install PyYaml] *** task path: /Users/tsuguya/homedev/kubespray-test/roles/kubernetes-apps/helm/tasks/main.yml:16 fatal: [node1]: FAILED! => {"changed": false, "msg": "missing required arguments: backend, image"}

Anything else we need to know

I'm currently running it with the following changes:

- name: Helm | Install PyYaml
  package:
    name: "{{ pyyaml_package }}"
    state: present
  when:
    - pyyaml_package is defined
    - not is_fedora_coreos

- name: Helm | Install PyYaml [Fedora CoreOS]
  community.general.rpm_ostree_pkg:
    name: python3-pyyaml
  when:
    - is_fedora_coreos
  register: rpm_ostree_install_pyyaml_result

- name: Helm | Reboot if PyYaml was installed [Fedora CoreOS]
  when:
    - rpm_ostree_install_pyyaml_result is defined
    - rpm_ostree_install_pyyaml_result.changed
  reboot:
olinux-dev commented 6 months ago

having the same problem, installing it via fedora_coreos_packages and commenting the 'Helm | Install PyYaml' task works just fine. Is there a reason why we would install it like this instead of just installing it via fedora_coreos_packages?

ByPoP commented 5 months ago

upgrade OS

sudo rpm-ostree upgrade --bypass-driver sudo reboot now

install

sudo rpm-ostree install libselinux-python3 sudo rpm-ostree install python3-pyyaml sudo reboot now

remove this

vi roles/kubernetes-apps/helm/tasks/main.yml

k8s-triage-robot commented 2 months ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 month ago

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

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

You can:

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

/lifecycle rotten

k8s-triage-robot commented 6 days ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 6 days ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/kubespray/issues/10885#issuecomment-2384524512): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.