Fail to install on fresh OS
SoulRaven opened this issue · 11 comments
hello,
i have a test bench with Ubuntu 22.04 with fresh install.
After the first run i get this error:
https://pastebin.com/cqkrpav2
after the second run i get this:
https://pastebin.com/ynN7X677
the playbook is like this:
- name: Kubernetes deploy
collections: []
hosts: [ 'hp_t620' ]
gather_facts: True
become: True
environment: '{{ inventory__environment | d({})
| combine(inventory__group_environment | d({}))
| combine(inventory__host_environment | d({})) }}'
vars:
pip_install_packages:
- name: docker
kubernetes_allow_pods_on_master: true
pre_tasks:
- name: Install packages needed for deploy
package:
name:
- apt-utils
state: latest
roles:
- role: geerlingguy.pip
tags: []
- role: geerlingguy.docker
tags: []
- role: geerlingguy.kubernetes
tags: []
docker_compose_version: "v2.6.0"
and
kubernetes_version: '1.24'
any idea what is wrong ?
The CI tests are also failing on Calico networking tasks currently. I may need to bump the version defaults for this role. https://github.com/geerlingguy/ansible-role-kubernetes/actions
hello,
to what version?
i bumped to 1.24 and nothing and also the network is Flannel not Calico.
@SoulRaven I've also run into a problem with a fresh install of Ubuntu 22.04. For me, the issue was related to containerd. Specifically the "cri" plugin being disabled in /etc/containerd/config.toml.
disabled_plugins = ["cri"]
I threw a task in to remove that and a handler to restart containerd.
@SoulRaven I've also run into a problem with a fresh install of Ubuntu 22.04. For me, the issue was related to containerd. Specifically the "cri" plugin being disabled in /etc/containerd/config.toml.
disabled_plugins = ["cri"]
I threw a task in to remove that and a handler to restart containerd.
i know, i just fix this a few days ago, but quit to use Kubernetes, i hard as hell to have some UI that is working out of the box. For me now i am testing k3s, and is more easy to spin up a cluster
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
Is it possible to re-open this issue? I'm also experiencing the same errors on a fresh Ubuntu server 22.04 install
I may need to bump the version defaults for this role
What version defaults were you referring @geerlingguy ?
please /reopen :)
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.