Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ansible_os_family CoreOS != Coreos in ansible >= 2.8.0 #4893

Closed
boxcee opened this issue Jun 17, 2019 · 3 comments
Closed

ansible_os_family CoreOS != Coreos in ansible >= 2.8.0 #4893

boxcee opened this issue Jun 17, 2019 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@boxcee
Copy link

boxcee commented Jun 17, 2019

Had a problem running the cluster.yml playbook today. The solution was to downgrade ansible to 2.7.2. The cluster.yml playbook checks for ansible_os_family in ['CoreOS'], but ansible returns Coreos.

Environment:

  • Cloud provider or hardware configuration:
    bare metal
  • OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
    CoreOS
  • Version of Ansible (ansible --version):
    2.8.0/2.8.1

Kubespray version (commit) (git rev-parse --short HEAD):
2.8.3

Command used to invoke ansible:
ansible-playbook -i ... -b -l ... cluster.yml

Output of ansible run:

- debug:
  msg: "{{ansible_os_family}}"
TASK [bootstrap-os : debug] 
Monday 17 June 2019  17:46:19 +0200 (0:00:01.508)     0:00:08.619
*********** ok: [devcluster76] => {
    "msg": "Coreos"
}

Anything else do we need to know:
I tested with ansible version 2.7.2 where ansible_os_family resolves to CoreOS.

@boxcee boxcee added the kind/bug Categorizes issue or PR as related to a bug. label Jun 17, 2019
@MarkusTeufelberger
Copy link
Contributor

Related to #4778

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 18, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 18, 2019
@boxcee boxcee closed this as completed Oct 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants