| 2023-09-15 14:36:20 |
Rudra Trivedi |
bug |
|
|
added bug |
| 2023-09-15 14:39:03 |
Rudra Trivedi |
description |
Mainline kernels do not set the same paramters in /proc as official Ubuntu kernels, specifically `/proc/version_signature`.
On a system with such a kernel installed, checking the status of Ubuntu Pro using `pro status` results in unexpected extra output:
rudra@pro_test:~$ sudo pro status
[sudo] password for rudra:
failed to process /proc/version_signature.
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes enabled Expanded Security Maintenance for Applications
(...)
NOTICES
The current kernel (5.19.17-051917-generic, x86_64) is not supported by livepatch.
...
Either switch to a supported kernel or `pro disable livepatch` to dismiss this warning.
...
rudra@pro_test:~$ canonical-livepatch status
last check: 30 seconds ago
kernel: (unsupported)
server check-in: succeeded
kernel state: kernel not supported by Canonical
This is more problematic in the json output:
rudra@pro_test:~$ sudo pro status --format json
failed to process /proc/version_signature.
{"_doc": "Content provided in json response is currently considered Experimental and may change", "_schema_version": "0.1", "account"
(...)
"description": "Security compliance and audit tools", "description_override": null, "entitled": "yes", "name": "usg", "status": "enabled", "status_details": "Ubuntu Security Guide is active", "warning": null}], "simulated": false, "version": "28.1~22.04", "warnings": []}
While the output does suggest to disable Livepatch (and I can confirm that the error does go away in this case), I believe that such an error should still give a valid json.
In its current state, pgograms like jinja or jq would refuse to process this output.
rudra@pro_test:~$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
rudra@pro_test:~$ apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 28.1~22.04
Candidate: 28.1~22.04
Version table:
*** 28.1~22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
27.7~22.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages |
Mainline kernels do not set the same paramters in /proc as official Ubuntu kernels, specifically `/proc/version_signature`.
On a system with such a kernel installed, checking the status of Ubuntu Pro using `pro status` results in unexpected extra output:
rudra@pro_test:~$ sudo pro status
[sudo] password for rudra:
failed to process /proc/version_signature.
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes enabled Expanded Security Maintenance for Applications
(...)
NOTICES
The current kernel (5.19.17-051917-generic, x86_64) is not supported by livepatch.
...
Either switch to a supported kernel or `pro disable livepatch` to dismiss this warning.
...
rudra@pro_test:~$ canonical-livepatch status
last check: 30 seconds ago
kernel: (unsupported)
server check-in: succeeded
kernel state: kernel not supported by Canonical
This is more problematic in the json output:
rudra@pro_test:~$ sudo pro status --format json
failed to process /proc/version_signature.
{"_doc": "Content provided in json response is currently considered Experimental and may change", "_schema_version": "0.1", "account"
(...)
"description": "Security compliance and audit tools", "description_override": null, "entitled": "yes", "name": "usg", "status": "enabled", "status_details": "Ubuntu Security Guide is active", "warning": null}], "simulated": false, "version": "28.1~22.04", "warnings": []}
While the output does suggest to disable Livepatch (and I can confirm that the error does go away in this case), I believe that such an error should still give a valid json.
In its current state, pgograms like jinja or jq would refuse to process this output.
rudra@pro_test:~$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
rudra@pro_test:~$ apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 28.1~22.04
Candidate: 28.1~22.04
Version table:
*** 28.1~22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
27.7~22.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
rudra@pro_test:~$ uname -a
Linux vpntest 5.19.17-051917-generic #202210240939 SMP PREEMPT_DYNAMIC Mon Oct 24 09:43:01 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
For testing, I installed 5.19.17-051917-generic using the mainline ppa. |
|
| 2023-09-15 14:39:28 |
Rudra Trivedi |
description |
Mainline kernels do not set the same paramters in /proc as official Ubuntu kernels, specifically `/proc/version_signature`.
On a system with such a kernel installed, checking the status of Ubuntu Pro using `pro status` results in unexpected extra output:
rudra@pro_test:~$ sudo pro status
[sudo] password for rudra:
failed to process /proc/version_signature.
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes enabled Expanded Security Maintenance for Applications
(...)
NOTICES
The current kernel (5.19.17-051917-generic, x86_64) is not supported by livepatch.
...
Either switch to a supported kernel or `pro disable livepatch` to dismiss this warning.
...
rudra@pro_test:~$ canonical-livepatch status
last check: 30 seconds ago
kernel: (unsupported)
server check-in: succeeded
kernel state: kernel not supported by Canonical
This is more problematic in the json output:
rudra@pro_test:~$ sudo pro status --format json
failed to process /proc/version_signature.
{"_doc": "Content provided in json response is currently considered Experimental and may change", "_schema_version": "0.1", "account"
(...)
"description": "Security compliance and audit tools", "description_override": null, "entitled": "yes", "name": "usg", "status": "enabled", "status_details": "Ubuntu Security Guide is active", "warning": null}], "simulated": false, "version": "28.1~22.04", "warnings": []}
While the output does suggest to disable Livepatch (and I can confirm that the error does go away in this case), I believe that such an error should still give a valid json.
In its current state, pgograms like jinja or jq would refuse to process this output.
rudra@pro_test:~$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
rudra@pro_test:~$ apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 28.1~22.04
Candidate: 28.1~22.04
Version table:
*** 28.1~22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
27.7~22.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
rudra@pro_test:~$ uname -a
Linux vpntest 5.19.17-051917-generic #202210240939 SMP PREEMPT_DYNAMIC Mon Oct 24 09:43:01 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
For testing, I installed 5.19.17-051917-generic using the mainline ppa. |
Mainline kernels do not set the same paramters in /proc as official Ubuntu kernels, specifically `/proc/version_signature`.
On a system with such a kernel installed, checking the status of Ubuntu Pro using `pro status` results in unexpected extra output:
rudra@pro_test:~$ sudo pro status
[sudo] password for rudra:
failed to process /proc/version_signature.
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes enabled Expanded Security Maintenance for Applications
(...)
NOTICES
The current kernel (5.19.17-051917-generic, x86_64) is not supported by livepatch.
...
Either switch to a supported kernel or `pro disable livepatch` to dismiss this warning.
...
rudra@pro_test:~$ canonical-livepatch status
last check: 30 seconds ago
kernel: (unsupported)
server check-in: succeeded
kernel state: kernel not supported by Canonical
This is more problematic in the json output:
rudra@pro_test:~$ sudo pro status --format json
failed to process /proc/version_signature.
{"_doc": "Content provided in json response is currently considered Experimental and may change", "_schema_version": "0.1", "account"
(...)
"description": "Security compliance and audit tools", "description_override": null, "entitled": "yes", "name": "usg", "status": "enabled", "status_details": "Ubuntu Security Guide is active", "warning": null}], "simulated": false, "version": "28.1~22.04", "warnings": []}
While the output does suggest to disable Livepatch (and I can confirm that the error does go away in this case), I believe that such an error should still give a valid json.
In its current state, pgograms like jinja or jq would refuse to process this output.
rudra@pro_test:~$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
rudra@pro_test:~$ apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 28.1~22.04
Candidate: 28.1~22.04
Version table:
*** 28.1~22.04 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
27.7~22.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
rudra@pro_test:~$ uname -a
Linux pro_test 5.19.17-051917-generic #202210240939 SMP PREEMPT_DYNAMIC Mon Oct 24 09:43:01 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
For testing, I installed 5.19.17-051917-generic using the mainline ppa. |
|
| 2023-09-19 10:56:04 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu): status |
New |
Confirmed |
|
