microk8s.daemon-containerd is filling my syslog with "zfs does not implement Usage() yet" messages

[bjf]

I'm running Ubuntu 20.04 with zfs as root and microk8s.daemon-containerd is spewing errors about "zfs does not implement Usage() yet"

inspection-report-20200330_144131.tar.gz

[balchua]

Hi @bjf is it working?
If not, you can refer to the docs here and scroll to the section which talks about zfs.
Thanks

[bjf]

Oh, it's working just fine. The problem is that it's constantly spewing errors into syslog. Brad

…

On Mon, Mar 30, 2020 at 3:13 PM balchua ***@***.***> wrote: Hi @bjf <https://github.com/bjf> is it working? If not, you can refer to the docs here <https://microk8s.io/docs/install-alternatives> and scroll to the section which talks about zfs. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1077 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ7G5TU45BITWPDJ27XHHTRKEKRFANCNFSM4LXARU4A> .

-- Brad Figg [email protected] http://www.canonical.com

[balchua]

I think containerd log is set to debug.
You can edit the file /var/snap/microk8s/current/args/containerd and add this line --log-level fatal
After that you can do a microk8s.stop and then microk8s.start.
Can you see if this works? Thanks

[bjf]

That did "fix" my issue.

…

On Mon, Mar 30, 2020 at 3:47 PM balchua ***@***.***> wrote: I think containerd log is set to debug. You can edit the file /var/snap/microk8s/current/args/containerd and add this line --log-level fatal After that you can do a microk8s.stop and then microk8s.start. Can you see if this works? Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1077 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJ7G5TFUKFHXVUG7SYTRI3RKEOQDANCNFSM4LXARU4A> .

-- Brad Figg [email protected] http://www.canonical.com

[balchua]

Great. Thanks

[tvansteenburgh]

Wait, shouldn't we consider making this the default?

[balchua]

Sorry about closing it sooner. Maybe info or error.

[ktsakalozos]

I am +1 to reducing the log level.

This specific log message [1] is marked as error so if we are to silence it we would need to log almost nothing. I am not so sure this is the right approach. We gather containerd logs via the microk8s.inspect script to figure out if something is wrong.

In its default setup on zfs MicroK8s uses the native snapshoter so you normally do not see this message.

[1] https://github.com/containerd/zfs/blob/9abf673ca6ff9ab8d9bd776a4ceff8f6dc699c3d/zfs.go#L133
[2] containerd/zfs#17

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dalbani]

The ZFS snapshotter plugin has been fixed in containerd/zfs#38.
And the fix is marked for inclusion in containerd 1.5 in containerd/containerd#5243.
What does this mean for MicroK8s? In terms of when it will land in a stable release.
I suppose quite far down the line, right? Because I read that MicroK8s 1.21 will use containerd version 1.4.
Given how annoying those log message are, is there a way to compile and include the fix manually in MicroK8s or something like that?