hide upgrade notifications on unsupported arches
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-advantage-tools (Ubuntu) |
Fix Released
|
Undecided
|
Renan Rodrigo | ||
| Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
| Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
| Focal |
Fix Released
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
| Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
Bug 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/
ls /var/lib/
```
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/
ls /var/lib/
```
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/
ls /var/lib/
```
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/
```
[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:
| Changed in ubuntu-advantage-tools (Ubuntu): | |
| status: | New → Triaged |
| status: | Triaged → In Progress |
| assignee: | nobody → Renan Rodrigo (renanrodrigo) |
| Renan Rodrigo (renanrodrigo) wrote | #1 |
| Renan Rodrigo (renanrodrigo) wrote | #2 |
| description: | updated |
| description: | updated |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in ubuntu-advantage-tools (Ubuntu): | |
| status: | In Progress → Fix Released |
| description: | updated |
| Andreas Hasenack (ahasenack) wrote Please test proposed package | #4 |
| Changed in ubuntu-advantage-tools (Ubuntu Kinetic): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed verification-needed-kinetic |
| Changed in ubuntu-advantage-tools (Ubuntu Jammy): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed-jammy |
| Andreas Hasenack (ahasenack) wrote | #5 |
| Changed in ubuntu-advantage-tools (Ubuntu Focal): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed-focal |
| Andreas Hasenack (ahasenack) wrote | #6 |
| Andreas Hasenack (ahasenack) wrote | #7 |
| Changed in ubuntu-advantage-tools (Ubuntu Bionic): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed-bionic |
| Andreas Hasenack (ahasenack) wrote | #8 |
| Changed in ubuntu-advantage-tools (Ubuntu Xenial): | |
| status: | New → Fix Committed |
| tags: | added: verification-needed-xenial |
| Grant Orndorff (orndorffgrant) wrote | #9 |
| tags: |
added: verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic verification-done-xenial removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-xenial |
| Andreas Hasenack (ahasenack) wrote | #10 |
| Launchpad Janitor (janitor) wrote | #11 |
| Changed in ubuntu-advantage-tools (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Chris Halse Rogers (raof) wrote Update Released | #12 |
| Launchpad Janitor (janitor) wrote | #13 |
| Changed in ubuntu-advantage-tools (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #14 |
| Changed in ubuntu-advantage-tools (Ubuntu Focal): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #15 |
| Changed in ubuntu-advantage-tools (Ubuntu Jammy): | |
| status: | Fix Committed → Fix Released |
| Launchpad Janitor (janitor) wrote | #16 |
| Changed in ubuntu-advantage-tools (Ubuntu Kinetic): | |
| status: | Fix Committed → Fix Released |
From the discourse discussion:
> Hello all,
> So, after taking a look, arm64 is actually supported and should be available to Pro users.
> This was fixed in the backend today. People who attach from now on will have full access to esm-> infra and esm-apps from Bionic onwards.
> If you are attached already, please:
> - Run sudo pro status and check there is a message saying that a contract change happened, and > asking you to run sudo pro refresh
> - Well, run sudo pro refresh to get the new (and correct) contract data
> - Run sudo pro status again: you should see esm-apps now available.
> - Enable it with sudo pro enable esm-apps
> As for other architectures (armhf, for instance) which are actually unsupported - we are working > to avoid showing that updates are available, and will provide more info on the bug that Oliver opened.