Livepatch seems to be relying on the output of /etc/lsb-release to verify compatibility on all operations (including disable/status/etc). I would say editing /etc/lsb-release or /etc/os-release is not something supported from the Pro side.
I see the report says you are using Ubuntu Jammy Jellyfish (22.04). If that is the case, and the /etc/lsb-release was edited back to the original content, then Livepatch should work fine.
Can you please confirm the content of /etc/lsb-release now, and the output you see when disabling/enabling Livepatch again?
Hello, jkwang28, thanks for reporting this bug.
Livepatch seems to be relying on the output of /etc/lsb-release to verify compatibility on all operations (including disable/ status/ etc). I would say editing /etc/lsb-release or /etc/os-release is not something supported from the Pro side.
I see the report says you are using Ubuntu Jammy Jellyfish (22.04). If that is the case, and the /etc/lsb-release was edited back to the original content, then Livepatch should work fine.
Can you please confirm the content of /etc/lsb-release now, and the output you see when disabling/enabling Livepatch again?