microk8s: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
This just started happening today, after an auto-refresh to v1.20.9. It persists even after a snap restart microk8s.
$ microk8s.status
microk8s is running
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
/snap/microk8s/2338/bin/dqlite: symbol lookup error: /snap/microk8s/2338/bin/dqlite: undefined symbol: sqlite3_system_errno
high-availability: no
datastore master nodes: none
datastore standby nodes: none
addons:
enabled:
dns # CoreDNS
ha-cluster # Configure high availability on the current node
storage # Storage class; allocates storage from host directory
disabled:
[...]
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 7
- Comments: 19 (5 by maintainers)
New snap revisions (2361 and 2362) should be on 1.20/edge, 1.20/beta and 1.20/candidate. This revision is now going through testing to be released on the 1.20/stable channel.
As @balchua mentioned, this issue was patched a few weeks ago in all tracks (1.19, 1.20, 1.21 and latest). Our CI did not pick up the change on the 1.20 branch. I cannot offer more insight as to why this is the case, I need to do some investigation.
Apologies for the inconvenience.
It looks like the fix on this is already merged. https://github.com/ubuntu/microk8s/pull/2428 I wonder if this is already released.