sysctl-setup.yml doesn't recognize Ubuntu 20.04

[ea-p]

Received this error while using this role to install k8s on an ubuntu 20.04 server.

{
"msg": "Failed to reload sysctl: kernel.panic = 10\nnet.ipv6.conf.all.disable_ipv6 = 1\nsysctl: cannot stat /proc/sys/net/bridge/bridge-nf-call-iptables: No such file or directory\n",
"invocation": {
"module_args": {
"name": "net.bridge.bridge-nf-call-iptables",
"value": "1",
"state": "present",
"reload": true,
"sysctl_set": false,
"ignoreerrors": false,
"sysctl_file": "/etc/sysctl.conf"
}
},
"_ansible_no_log": false,
"changed": false,
"item": "net.bridge.bridge-nf-call-iptables",
"ansible_loop_var": "item",
"_ansible_item_label": "net.bridge.bridge-nf-call-iptables"
}

This is from the server:
"ansible_distribution": "Ubuntu",
"ansible_distribution_file_parsed": true,
"ansible_distribution_file_path": "/etc/os-release",
"ansible_distribution_file_variety": "Debian",
"ansible_distribution_major_version": "20",
"ansible_distribution_release": "focal",
"ansible_distribution_version": "20.04",

Maybe switch from "ansible_distribution" to "ansible_os_family": "Debian"

[geerlingguy]

Strangely, I'm also running into this on Debian 10 over in geerlingguy/raspberry-pi-dramble#187

[stale]

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.

[rdxmb]

not stale, see existing PR

[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.

[rdxmb]

/reopen please

[stale]

This issue is no longer marked for closure.

[stale]

This issue is no longer marked for closure.

[ccokee]

I'm using this role in CentOS 7 on Vagrant (centos/7 box) and I'm stepping in the same problem with sysctl-setup.yml