Enabling of Pro Services Does Not Update when using airgapped mirrors over http://
- Focal (20.04)
- Bug #2031192
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-advantage-tools (Ubuntu) |
Fix Released
|
High
|
Lucas Albuquerque Medeiros de Moura | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When users create an airgapped environement, they may create APT mirrors for the ESM services that share a common base URL. For example, in this bug here, the user was mirroring their services one:
http://
http://
http://
http://
http://
http://
As we can see, all services share the
http://
Since the Pro client was looking for unique urls to distinguish enabled services in the machine, this setup was not working.
Now, instead of looking at the APT url, we are also looking at the suite (i.e. bionic-
If we identify that both APT url and suite are in the output of apt-cache policy
with the right permission number, we say that the service is enabled.
This will unblock users that want to use the same APT url for their airgapped setup.
Additionally, we have discussed this issue with the Landscape team and they assured us that we will always have an unique combination of APT url and suite.
[Test cases]
We have setup an integration test for this scenario on the Pro client codebase.
We will link the test result here.
[ Regression Potential ]
We believe we are now improving our check to see if the service is enabled or not, as we are now considering a combination that we now will be unique. Therefore, the only regression potential we can think is the situation were we mistakenly create that combination (APT url + suite) or check it in a wrong way in the output of apt-cache policy.
However, we believe our integration tests should be enough to assert that this is not the case.
[ Original Description]
contract server is airgapped and running
uaclient is pointing to the airgapped contract server to get entitlements
Additionally, using a landscape server and it's underlying reprepro to mirror ESM and FIPs for airgap, this forces using http
apt update is working over landscape over multiple repos.
pro attach subscriptioncon
next
pro enable service is creating /etc/apt/
For example: pro enable esm-apps
Service Status is not getting updating
pro status is showing after enablement of esm-apps
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes disabled Expanded Security Maintenance for Applications
esm-infra yes disabled Expanded Security Maintenance for Infrastructure
Editing 90ubuntu-advantage to append http:// get rids of the apt update working but service status is not changing.
Issuing pro enable esm-apps appends another entry and is a loop
ubuntu-
["2023-
["2023-
["2023-
["2023-
["2023-
For auditing purposes the status of subscription and it's services is important to be correct. Additionally to insure correct packages for fips get installed.
summary: |
- Enabling of Pro Service Does Not Update when using airgapped mirrors + Enabling of Pro Services Does Not Update when using airgapped mirrors over http:// |
description: | updated |
Lucas Albuquerque Medeiros de Moura (lamoura) wrote : | #1 |
Steven LaCosse (motosteven) wrote : | #2 |
Thanks Lucas for looking into this.
In my original report, I've been testing the ua contract server as the same machine I'm trying to enable the airgapped subscription to, which also happens to be joined to the landscape server.
I have not created a repo profile to enable the esm repos via landscape.
I've tried what you've suggested.
When the repo path already has http:// in the service repo path prior to attaching the sub and enabling this removes the the http error when enabling esm-apps.
The prior error was
["2023-
With esm-apps repo already in service repo with http, unfortunately enabling esm-apps still shows the same problem of not showing the service enabled
Enabling esm-apps does create the /etc/apt/
So the repo packages are available to use, apt update shows this
apt update
Hit:1 http://
Hit:2 http://
Hit:3 http://
Hit:4 http://
Hit:5 http://
But it still does not change the status of the subscription service enablement
pro status
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes disabled Expanded Security Maintenance for Applications
esm-infra yes disabled Expanded Security Maintenance for Infrastructure
livepatch yes disabled Canonical Livepatch service
realtime-kernel yes disabled Ubuntu kernel with PREEMPT_RT patches integrated
usg yes disabled Security compliance and audit tools
Steven LaCosse (motosteven) wrote : | #3 |
More information when trying to enable service
The line may be more relevant and maybe blocking it.
["2023-
pro enable esm-apps
One moment, checking your subscription first
Updating package lists
Ubuntu Pro: ESM Apps enabled
["2023-
["2023-
["2023-
["2023-
["2023-
["2023-
["2023-
["2023-
["2023-
["2023-
Lucas Albuquerque Medeiros de Moura (lamoura) wrote : | #4 |
Hi motosteven,
Thanks for the updates here. Just to double check, can you send the full output of both of these commands:
$ apt update
$ apt-cache policy
For the esm services, we use the output of apt-cache policy as a way to check if the service is enabled or not. So it will probably give us a clue of what is happening here.
Steven LaCosse (motosteven) wrote : | #5 |
Hi Lucus,
My example issue will be issuing apt update and apt-cache policy after a fresh attach and enable esm-apps
This adds the esm-security repo into ubuntu-
cat /etc/apt/
deb http://
# deb-src http://
# deb http://
# deb-src http://
If I manually comment out the jammy-esm-
apt update
Hit:1 http://
Hit:2 http://
Hit:3 http://
Hit:4 http://
Hit:5 http://
Hit:6 http://
Hit:7 http://
Reading package lists...
Building dependency tree...
Reading state information...
44 packages can be upgraded. Run 'apt list --upgradable' to see them.
apt-cache policy
Package files:
100 /var/lib/
release a=now
500 http://
release a=jammy-
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
release a=jammy,
origin landscapeserver
500 http://
Lucas Albuquerque Medeiros de Moura (lamoura) wrote : | #6 |
Hi motosteven,
It seems that everything is correct on both of these commands.
Can you run this python script here on the affected machine and report the output of it:
---------------
from uaclient.
from uaclient.config import UAConfig
esm_apps = ESMAppsEntitlem
ret, reason = esm_apps.
print(ret, reason)
-----------------
Steven LaCosse (motosteven) wrote : | #7 |
UserFacingStatu
Lucas Albuquerque Medeiros de Moura (lamoura) wrote : | #8 |
Okay, that is curious.
Can you provide the full content of the aptURL overwrite you are using ? I just want to double check if that URL might be causing this issue
Steven LaCosse (motosteven) wrote : | #9 |
For the airgapped contract server the override aptURL in the yml file is:
This took some trial and error for me to get originally but this allowed enable to find the repo.
http://
I've been trying to play around with it but with no luck by editing the suites including on top of the overrides.
directives:
aptKey: REDACTED
aptURL: http://
suites:
- jammy-apps-security
- jammy-apps-updates
- bionic-
- bionic-apps-updates
entitled: true
obligations:
overrides:
- directives:
suites:
- bionic-
- bionic-
selector:
series: bionic
- directives:
suites:
- jammy-esm-
- jammy-esm-
selector:
series: jammy
- affordances:
- amd64
- i386
- i686
- s390x
- x86_64
series:
bionic:
suites:
- bionic-
- bionic-apps-updates
jammy:
suites:
- jammy-apps-security
- jammy-apps-updates
type: esm-apps
Lucas Albuquerque Medeiros de Moura (lamoura) wrote : | #10 |
Thanks for that motosteven,
Can you change the URL to not include the last "/":
http://
I think that is causing the issue. Can you please test it again on a clean machine and report if the service turns out enabled in the end.
Steven LaCosse (motosteven) wrote (last edit ): | #11 |
Hi Lucas,
I remembered why I had to add the / and it was because it wasn't working as expected and doing odd behavior as well.
I have changed the override to remove the / and try what you ask for more bug report logs.
But from a "fresh ubuntu-
Please see ubuntu-
after "pro attach"
["2023-
pro status is showing that the service is enabled but this is not true
SERVICE ENTITLED STATUS DESCRIPTION
esm-apps yes enabled Expanded Security Maintenance for Applications
esm-infra yes enabled Expanded Security Maintenance for Infrastructure
livepatch yes disabled Canonical Livepatch service
realtime-kernel yes disabled Ubuntu kernel with PREEMPT_RT patches integrated
usg yes disabled Security compliance and audit tools
It's in a broken state at this point.
pro enable esm-apps
One moment, checking your subscription first
Ubuntu Pro:...
Lucas Albuquerque Medeiros de Moura (lamoura) wrote (last edit ): | #12 |
Okay, I think I understand what the problem is. We check if a esm service is enabled by looking at the specified aptURL in the output of apt-cache policy. Since that URL also appear on other apt sources (i.e. jammy/universe), we will think that the esm services are both enabled.
This is a bug on our side as we understand we need a better strategy to see if the services are indeed enabled.
However, until we can deliver that fix, would it be possible to host the esm mirrors on a different path ?
We would need an unique path for both esm-infra and esm-apps for this to work as is.
But please, let us know if it is not possible to change the path for the esm apt mirrors.
Steven LaCosse (motosteven) wrote (last edit ): | #13 |
Hi Lucas,
I am hosting esm, cis, fips, and fips-updates for on-prem landscape in the ubuntu distribution but they are all under unique series as recommended by landscape so packages do not overlap.
IE:
http://
http://
http://
http://
http://
http://
and so on
Just to understand the workaround:
Are you suggesting to put of all of these cis{usg}/esm/fips under a different distribution like
http://
For now I'd rather just enable each apt repo via landscape repo profile or a different configuration management tool and wait for a fix for correct service enablement. The newer landscape client/server has ability to report status of ubuntu pro services so there is added benefit to get this working for on-prem repos, landscape and airgapped environments.
Thanks,
Steven
Lucas Albuquerque Medeiros de Moura (lamoura) wrote : | #14 |
Hi motosteven,
The problem is on the base url (everything that comes before the /ubuntu bit) itself:
http://
We need that base url to be unique for each service. For example:
http://
http://
Another possibility is to also create an alias address for those apt sources and if the alias path are unique, it should also work as expected.
Regarding the fix, we will probably be able to deliver it on November, which is the month we will release a new version of the library. I will let you know if that changes.
Changed in ubuntu-advantage-tools (Ubuntu): | |
assignee: | nobody → Lucas Albuquerque Medeiros de Moura (lamoura) |
status: | New → Triaged |
Steven LaCosse (motosteven) wrote : | #15 |
Thanks for your clarification Lucas, for now it's too much effort to change the repo pulls, but good to note for the workaround. Looking forward to the fix.
Grant Orndorff (orndorffgrant) wrote : | #16 |
Thanks for the discussion here and discovering these bugs. We hope to fix these soon, but just to set expectations, we will probably get to this in the 24.04 cycle, so it will be a few months.
Changed in ubuntu-advantage-tools (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
Andreas Hasenack (ahasenack) wrote : Please test proposed package | #17 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in ubuntu-advantage-tools (Ubuntu Noble): | |
status: | New → Fix Committed |
tags: | added: verification-needed verification-needed-noble |
Changed in ubuntu-advantage-tools (Ubuntu Mantic): | |
status: | New → Fix Committed |
tags: | added: verification-needed-mantic |
Andreas Hasenack (ahasenack) wrote : | #18 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in ubuntu-advantage-tools (Ubuntu Jammy): | |
status: | New → Fix Committed |
tags: | added: verification-needed-jammy |
Andreas Hasenack (ahasenack) wrote : | #19 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in ubuntu-advantage-tools (Ubuntu Focal): | |
status: | New → Fix Committed |
tags: | added: verification-needed-focal |
Andreas Hasenack (ahasenack) wrote : | #20 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in ubuntu-advantage-tools (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: | added: verification-needed-bionic |
Andreas Hasenack (ahasenack) wrote : | #21 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in ubuntu-advantage-tools (Ubuntu Xenial): | |
status: | New → Fix Committed |
tags: | added: verification-needed-xenial |
Andreas Hasenack (ahasenack) wrote : | #22 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32~16.04) | #23 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32~23.10) | #24 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
update-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32~24.04) | #25 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
update-motd/unknown (s390x)
wsl-pro-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32~22.04) | #26 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
ubuntu-
update-motd/unknown (armhf)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32~20.04) | #27 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Andreas Hasenack (ahasenack) wrote : Please test proposed package | #28 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #29 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #30 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #31 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #32 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #33 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.1~24.04) | #34 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
wsl-pro-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.1~20.04) | #35 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.1~16.04) | #36 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Launchpad Janitor (janitor) wrote : | #37 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
-- Lucas Moura <email address hidden> Tue, 14 May 2024 11:22:35 +0200
Changed in ubuntu-advantage-tools (Ubuntu): | |
status: | Triaged → Fix Released |
Andreas Hasenack (ahasenack) wrote : Please test proposed package | #38 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #39 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #40 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #41 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #42 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #43 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.1~16.04) | #44 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.1~24.04) | #45 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.2~24.04) | #46 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
ubuntu-
update-motd/unknown (s390x)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.2~16.04) | #47 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.2~23.10) | #48 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
update-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.2~22.04) | #49 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.2~20.04) | #50 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.2~18.04) | #51 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
ubuntu-
update-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Andreas Hasenack (ahasenack) wrote : Please test proposed package | #52 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #53 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #54 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #55 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #56 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Andreas Hasenack (ahasenack) wrote : | #57 |
Hello Steven, or anyone else affected,
Accepted ubuntu-
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.3~16.04) | #58 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
ubuntu-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-advantage-tools/32.3~24.04) | #59 |
All autopkgtests for the newly accepted ubuntu-
The following regressions have been reported in tests triggered by the package:
software-
wsl-pro-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
Renan Rodrigo (renanrodrigo) wrote : | #60 |
The verification for the main SRU bug (https:/
No need to re-do all automation for 32.3, as explained in:https:/
So I am marking verification-done for all releases.
tags: |
added: verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-mantic verification-done-noble verification-done-xenial removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-noble verification-needed-xenial |
Andreas Hasenack (ahasenack) wrote : | #61 |
Doing an early release of this according to point 7 in the plan from https:/
autopkgtests are clear now
Launchpad Janitor (janitor) wrote : | #62 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* Backport 32.3 to noble (LP: #2060732)
ubuntu-
* d/apparmor: adjust the profiles to account for usr-merge consequences
(LP: #2067319)
ubuntu-
* d/apparmor: adjust rules for violations found during testing (LP: #2066929)
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
ubuntu-
* d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
* d/apparmor: introduce new ubuntu_
* New upstream release 32 (LP: #2060732)
- api:
+ u.pro.attach.
with token
+ u.pro.services.
+ u.pro.services.
+ u.pro.detach.v1: add support for detach operation
+ u.pro.status.
+ u.pro.services.
+ u.pro.security.
if needed
- apt_news: add architectures and packages selectors filters for apt news
- cli:
+ improved cli/log message for unexpected errors (GH: #2600)
+ properly handle setting empty config values (GH: #2925)
- cloud-init: support ubuntu_pro user-data
- collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
- config: create public and private config (GH: #2809)
- entitlements:
+ update logic that checks if a service is enabled (LP: #2031192)
- fips: warn/confirm with user if enabling fips downgrades the kernel
- fix: warn users if ESM cache cannot be updated (GH: #2841)
- logging:
+ use journald logging for all systemd services
+ add redundancy to secret redaction
- messaging:
+ add consistent messaging for end of contract state
+ make explicit that unattached enable/disable is a noop (GH: #2487)
+ make explicit that disabling a disabled service is a noop
+ make explicit that enabling an enabled service is a noop
- notices: filter unreadable notices when listing notices (GH: #2898)
-- Renan Rodrigo <email address hidden> Tue, 28 May 2024 15:15:48 -0300
Changed in ubuntu-advantage-tools (Ubuntu Noble): | |
status: | Fix Committed → Fix Released |
Andreas Hasenack (ahasenack) wrote : Update Released | #63 |
The verification of the Stable Release Update for ubuntu-
Launchpad Janitor (janitor) wrote : | #64 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* Backport 32.3 to mantic (LP: #2060732)
ubuntu-
* d/apparmor: adjust the profiles to account for usr-merge consequences
(LP: #2067319)
ubuntu-
* d/apparmor: adjust rules for violations found during testing (LP: #2066929)
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
ubuntu-
* d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
* d/apparmor: introduce new ubuntu_
* New upstream release 32 (LP: #2060732)
- api:
+ u.pro.attach.
with token
+ u.pro.services.
+ u.pro.services.
+ u.pro.detach.v1: add support for detach operation
+ u.pro.status.
+ u.pro.services.
+ u.pro.security.
if needed
- apt_news: add architectures and packages selectors filters for apt news
- cli:
+ improved cli/log message for unexpected errors (GH: #2600)
+ properly handle setting empty config values (GH: #2925)
- cloud-init: support ubuntu_pro user-data
- collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
- config: create public and private config (GH: #2809)
- entitlements:
+ update logic that checks if a service is enabled (LP: #2031192)
- fips: warn/confirm with user if enabling fips downgrades the kernel
- fix: warn users if ESM cache cannot be updated (GH: #2841)
- logging:
+ use journald logging for all systemd services
+ add redundancy to secret redaction
- messaging:
+ add consistent messaging for end of contract state
+ make explicit that unattached enable/disable is a noop (GH: #2487)
+ make explicit that disabling a disabled service is a noop
+ make explicit that enabling an enabled service is a noop
- notices: filter unreadable notices when listing notices (GH: #2898)
-- Renan Rodrigo <email address hidden> Tue, 28 May 2024 15:15:45 -0300
Changed in ubuntu-advantage-tools (Ubuntu Mantic): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #65 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* Backport 32.3 to jammy (LP: #2060732)
ubuntu-
* d/apparmor: adjust the profiles to account for usr-merge consequences
(LP: #2067319)
ubuntu-
* d/apparmor: adjust rules for violations found during testing (LP: #2066929)
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
ubuntu-
* d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
* d/apparmor: introduce new ubuntu_
* New upstream release 32 (LP: #2060732)
- api:
+ u.pro.attach.
with token
+ u.pro.services.
+ u.pro.services.
+ u.pro.detach.v1: add support for detach operation
+ u.pro.status.
+ u.pro.services.
+ u.pro.security.
if needed
- apt_news: add architectures and packages selectors filters for apt news
- cli:
+ improved cli/log message for unexpected errors (GH: #2600)
+ properly handle setting empty config values (GH: #2925)
- cloud-init: support ubuntu_pro user-data
- collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
- config: create public and private config (GH: #2809)
- entitlements:
+ update logic that checks if a service is enabled (LP: #2031192)
- fips: warn/confirm with user if enabling fips downgrades the kernel
- fix: warn users if ESM cache cannot be updated (GH: #2841)
- logging:
+ use journald logging for all systemd services
+ add redundancy to secret redaction
- messaging:
+ add consistent messaging for end of contract state
+ make explicit that unattached enable/disable is a noop (GH: #2487)
+ make explicit that disabling a disabled service is a noop
+ make explicit that enabling an enabled service is a noop
- notices: filter unreadable notices when listing notices (GH: #2898)
-- Renan Rodrigo <email address hidden> Tue, 28 May 2024 15:15:42 -0300
Changed in ubuntu-advantage-tools (Ubuntu Jammy): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #66 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* Backport 32.3 to focal (LP: #2060732)
ubuntu-
* d/apparmor: adjust the profiles to account for usr-merge consequences
(LP: #2067319)
ubuntu-
* d/apparmor: adjust rules for violations found during testing (LP: #2066929)
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
ubuntu-
* d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
* d/apparmor: introduce new ubuntu_
* New upstream release 32 (LP: #2060732)
- api:
+ u.pro.attach.
with token
+ u.pro.services.
+ u.pro.services.
+ u.pro.detach.v1: add support for detach operation
+ u.pro.status.
+ u.pro.services.
+ u.pro.security.
if needed
- apt_news: add architectures and packages selectors filters for apt news
- cli:
+ improved cli/log message for unexpected errors (GH: #2600)
+ properly handle setting empty config values (GH: #2925)
- cloud-init: support ubuntu_pro user-data
- collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
- config: create public and private config (GH: #2809)
- entitlements:
+ update logic that checks if a service is enabled (LP: #2031192)
- fips: warn/confirm with user if enabling fips downgrades the kernel
- fix: warn users if ESM cache cannot be updated (GH: #2841)
- logging:
+ use journald logging for all systemd services
+ add redundancy to secret redaction
- messaging:
+ add consistent messaging for end of contract state
+ make explicit that unattached enable/disable is a noop (GH: #2487)
+ make explicit that disabling a disabled service is a noop
+ make explicit that enabling an enabled service is a noop
- notices: filter unreadable notices when listing notices (GH: #2898)
-- Renan Rodrigo <email address hidden> Tue, 28 May 2024 15:15:39 -0300
Changed in ubuntu-advantage-tools (Ubuntu Focal): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #67 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* Backport 32.3 to bionic (LP: #2060732)
ubuntu-
* d/apparmor: adjust the profiles to account for usr-merge consequences
(LP: #2067319)
ubuntu-
* d/apparmor: adjust rules for violations found during testing (LP: #2066929)
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
ubuntu-
* d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
* d/apparmor: introduce new ubuntu_
* New upstream release 32 (LP: #2060732)
- api:
+ u.pro.attach.
with token
+ u.pro.services.
+ u.pro.services.
+ u.pro.detach.v1: add support for detach operation
+ u.pro.status.
+ u.pro.services.
+ u.pro.security.
if needed
- apt_news: add architectures and packages selectors filters for apt news
- cli:
+ improved cli/log message for unexpected errors (GH: #2600)
+ properly handle setting empty config values (GH: #2925)
- cloud-init: support ubuntu_pro user-data
- collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
- config: create public and private config (GH: #2809)
- entitlements:
+ update logic that checks if a service is enabled (LP: #2031192)
- fips: warn/confirm with user if enabling fips downgrades the kernel
- fix: warn users if ESM cache cannot be updated (GH: #2841)
- logging:
+ use journald logging for all systemd services
+ add redundancy to secret redaction
- messaging:
+ add consistent messaging for end of contract state
+ make explicit that unattached enable/disable is a noop (GH: #2487)
+ make explicit that disabling a disabled service is a noop
+ make explicit that enabling an enabled service is a noop
- notices: filter unreadable notices when listing notices (GH: #2898)
-- Renan Rodrigo <email address hidden> Tue, 28 May 2024 15:15:36 -0300
Changed in ubuntu-advantage-tools (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #68 |
This bug was fixed in the package ubuntu-
---------------
ubuntu-
* Backport 32.3 to xenial (LP: #2060732)
ubuntu-
* d/apparmor: adjust the profiles to account for usr-merge consequences
(LP: #2067319)
ubuntu-
* d/apparmor: adjust rules for violations found during testing (LP: #2066929)
ubuntu-
* d/apparmor: allow access for /etc/os-release on all supported
profiles (LP: #2065573)
* apport: get path for timer job status from the correct place (LP: #2065616)
ubuntu-
* d/postinst: ensure migrations happen in correct package postinst (GH: #2982)
* d/apparmor: introduce new ubuntu_
* New upstream release 32 (LP: #2060732)
- api:
+ u.pro.attach.
with token
+ u.pro.services.
+ u.pro.services.
+ u.pro.detach.v1: add support for detach operation
+ u.pro.status.
+ u.pro.services.
+ u.pro.security.
if needed
- apt_news: add architectures and packages selectors filters for apt news
- cli:
+ improved cli/log message for unexpected errors (GH: #2600)
+ properly handle setting empty config values (GH: #2925)
- cloud-init: support ubuntu_pro user-data
- collect-logs: update default output file to pro_logs.tar.gz (LP: #2033313)
- config: create public and private config (GH: #2809)
- entitlements:
+ update logic that checks if a service is enabled (LP: #2031192)
- fips: warn/confirm with user if enabling fips downgrades the kernel
- fix: warn users if ESM cache cannot be updated (GH: #2841)
- logging:
+ use journald logging for all systemd services
+ add redundancy to secret redaction
- messaging:
+ add consistent messaging for end of contract state
+ make explicit that unattached enable/disable is a noop (GH: #2487)
+ make explicit that disabling a disabled service is a noop
+ make explicit that enabling an enabled service is a noop
- notices: filter unreadable notices when listing notices (GH: #2898)
-- Renan Rodrigo <email address hidden> Tue, 28 May 2024 15:15:32 -0300
Changed in ubuntu-advantage-tools (Ubuntu Xenial): | |
status: | Fix Committed → Fix Released |
Hi motosteven,
Thanks for reporting this. I have one idea, which I want to verify if it will work.
On clean machine, please setup the airgapped contract server so that the services repo paths already have the http:// protocol on them. After that, try attaching again and let me know what happens.