| 2023-01-27 12:53:44 |
Oliver Grawert |
bug |
|
|
added bug |
| 2023-01-28 11:06:20 |
Explicit Fullname |
bug |
|
|
added subscriber Explicit Fullname |
| 2023-01-30 19:04:17 |
Renan Rodrigo |
ubuntu-advantage-tools (Ubuntu): status |
New |
Triaged |
|
| 2023-01-30 19:04:19 |
Renan Rodrigo |
ubuntu-advantage-tools (Ubuntu): status |
Triaged |
In Progress |
|
| 2023-01-30 19:04:23 |
Renan Rodrigo |
ubuntu-advantage-tools (Ubuntu): assignee |
|
Renan Rodrigo (renanrodrigo) |
|
| 2023-02-03 13:39:35 |
grantiago |
bug |
|
|
added subscriber grant amaral |
| 2023-02-24 08:50:22 |
Markus Ueberall |
bug |
|
|
added subscriber Markus Ueberall |
| 2023-03-14 06:08:56 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2023-03-15 16:13:32 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~orndorffgrant/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/438992 |
|
| 2023-03-16 01:19:19 |
Grant Orndorff |
description |
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before creating the esm-apt-cache or displaying the message. The end result is that message don't get displayed on unsupported systems
[Test Case]
On an fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
|
| 2023-03-16 01:19:53 |
Grant Orndorff |
description |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before creating the esm-apt-cache or displaying the message. The end result is that message don't get displayed on unsupported systems
[Test Case]
On an fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before configuring the esm-apt-cache. The end result is that messages don't get displayed on unsupported systems
[Test Case]
On an fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
|
| 2023-03-16 01:20:02 |
Grant Orndorff |
description |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before configuring the esm-apt-cache. The end result is that messages don't get displayed on unsupported systems
[Test Case]
On an fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before configuring the esm-apt-cache. The end result is that messages don't get displayed on unsupported systems
[Test Case]
On a fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
|
| 2023-03-23 02:23:12 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2023-03-23 10:23:51 |
Renan Rodrigo |
description |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before configuring the esm-apt-cache. The end result is that messages don't get displayed on unsupported systems
[Test Case]
On a fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
[Impact]
Users of unsupported architectures (such as armhf) could see the messages about updates available in Ubuntu Pro, even though they aren't really available to that machine.
The fix is to check the supported architectures of esm before configuring the esm-apt-cache. The end result is that messages don't get displayed on unsupported systems
[Test Case]
On a fresh armhf container (or other unsupported architecture):
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked. (That means that apt won't attempt to download any potential esm updates.)
Machines which had already downloaded the sources lists should have those removed.
On a fresh armhf container (or other unsupported architecture):
- Running latest released u-a-t:
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
The directory will contain the sources list files for esm-apps at least.
- Upgrade to u-a-t 27.14:
```
/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
ls /var/lib/ubuntu-advantage/apt-esm/etc/apt/sources.list.d
```
That directory should not exist or not have any contents if the fix worked.
If you don't have a real or virtual armhf system, you can trick pro-client by doing something like the following:
DO NOT do this on a real machine you care about - only do it in a throwaway container/VM
```
echo -e '#!/usr/bin/bash\necho armhf' | tee /usr/bin/dpkg
```
[Regression Potential]
The fix reduces the number of machines that will get messages. If we made a mistake, it may mean that machines that should get messages won't.
[Discussion]
This was implemented in a more generic way that just looking at architectures, so it will cover other situations like unsupported releases or kernels if those ever apply.
[Original Description]
a user that is not running amd64 or i386 currently gets the notification for ESM security packages ... only after they signed up for pro they get an error message that their architecture is not supported.
We should either hide the esm update notification completely on such architectures (arm64/aarch64 in this case) or make it clear in the initial message that only x86 architectures are supported.
the related forum post can be found at:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/28 |
|
| 2023-04-06 21:30:13 |
Andreas Hasenack |
ubuntu-advantage-tools (Ubuntu Kinetic): status |
New |
Fix Committed |
|
| 2023-04-06 21:30:15 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-04-06 21:30:17 |
Andreas Hasenack |
bug |
|
|
added subscriber SRU Verification |
| 2023-04-06 21:30:23 |
Andreas Hasenack |
tags |
|
verification-needed verification-needed-kinetic |
|
| 2023-04-06 21:35:00 |
Andreas Hasenack |
ubuntu-advantage-tools (Ubuntu Jammy): status |
New |
Fix Committed |
|
| 2023-04-06 21:35:09 |
Andreas Hasenack |
tags |
verification-needed verification-needed-kinetic |
verification-needed verification-needed-jammy verification-needed-kinetic |
|
| 2023-04-06 21:39:42 |
Andreas Hasenack |
ubuntu-advantage-tools (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2023-04-06 21:39:50 |
Andreas Hasenack |
tags |
verification-needed verification-needed-jammy verification-needed-kinetic |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
|
| 2023-04-06 21:45:39 |
Andreas Hasenack |
ubuntu-advantage-tools (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2023-04-06 21:45:48 |
Andreas Hasenack |
tags |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic |
|
| 2023-04-06 21:51:14 |
Andreas Hasenack |
ubuntu-advantage-tools (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2023-04-06 21:51:24 |
Andreas Hasenack |
tags |
verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic |
verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-xenial |
|
| 2023-04-11 15:43:34 |
Grant Orndorff |
attachment added |
|
verification-2004018.tar.gz https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2004018/+attachment/5663035/+files/verification-2004018.tar.gz |
|
| 2023-04-11 15:43:59 |
Grant Orndorff |
tags |
verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-xenial |
verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic verification-done-xenial |
|
| 2023-04-19 01:31:25 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2023-04-19 01:31:59 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-04-19 01:32:48 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2023-04-19 01:33:17 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-04-19 01:33:44 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-04-19 01:34:12 |
Launchpad Janitor |
ubuntu-advantage-tools (Ubuntu Kinetic): status |
Fix Committed |
Fix Released |
|
