| 2020-05-01 00:51:27 |
Lee Trager |
bug |
|
|
added bug |
| 2020-05-01 00:53:01 |
Lee Trager |
description |
When region or rack controllers send what operating system they are on they are reporting the Ubuntu core version, not the operating system that is actually running.
LXD is able to get this information correctly when running in a Snap. I recently migrated the controller code to use the same LXD library to get OS information. MAAS is missing some Snap permission which the LXD has as the same code path is being used. |
When region or rack controllers send what operating system they are on they are reporting the Ubuntu core version, not the operating system that is actually running.
LXD is able to get this information correctly when running in a Snap. I recently migrated the controller code to use the same LXD library to get OS information. MAAS is missing some Snap permission which the LXD has as the same code path is being used.
If an LXD Pod is added this causes the OS information to flip between the Ubuntu Core version the Snap uses and the Ubuntu version the OS is using as this information is refreshed for the controller and Pod. |
|
| 2020-05-01 18:48:24 |
Alberto Donato |
maas: milestone |
2.8.0b3 |
2.8.0rc1 |
|
| 2020-05-01 19:20:17 |
Lee Trager |
description |
When region or rack controllers send what operating system they are on they are reporting the Ubuntu core version, not the operating system that is actually running.
LXD is able to get this information correctly when running in a Snap. I recently migrated the controller code to use the same LXD library to get OS information. MAAS is missing some Snap permission which the LXD has as the same code path is being used.
If an LXD Pod is added this causes the OS information to flip between the Ubuntu Core version the Snap uses and the Ubuntu version the OS is using as this information is refreshed for the controller and Pod. |
When region or rack controllers send what operating system they are on they are reporting the Ubuntu core version, not the operating system that is actually running.
LXD is able to get this information correctly when running in a Snap. I recently migrated the controller code to use the same LXD library to get OS information. MAAS is missing some Snap permission which the LXD has as the same code path is being used.
$ sudo curl -G --unix-socket "/var/snap/lxd/common/lxd/unix.socket" "lxd/1.0" 2>/dev/null | jq -r '.metadata.environment | .os_name + " " + .os_version'
Ubuntu 20.04
$ maas $PROFILE rack-controllers read | jq -r '.[] | .osystem + " " + .distro_series'
ubuntu-core 18
If an LXD Pod is added this causes the OS information to flip between the Ubuntu Core version the Snap uses and the Ubuntu version the OS is using as this information is refreshed for the controller and Pod. |
|
| 2020-05-01 19:24:35 |
Lee Trager |
bug task added |
|
snapd |
|
| 2020-05-04 16:44:21 |
Ian Johnson |
snapd: status |
New |
Incomplete |
|
| 2020-05-05 16:53:15 |
Adam Collard |
maas: assignee |
|
Lee Trager (ltrager) |
|
| 2020-05-05 20:43:42 |
Lee Trager |
maas: status |
Triaged |
In Progress |
|
| 2020-05-05 20:51:16 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/383467 |
|
| 2020-05-11 11:44:42 |
Alberto Donato |
maas: milestone |
2.8.0b4 |
2.8.0rc1 |
|
| 2020-05-21 20:48:13 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2020-06-04 12:41:11 |
Alberto Donato |
maas: status |
Fix Committed |
Fix Released |
|
| 2020-06-22 09:12:37 |
Samuele Pedroni |
snapd: status |
Incomplete |
Invalid |
|
