[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
The tests were re-triggered and they should not be an issue anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in base-files source package in Jammy: Fix Committed Status in base-files source package in Lunar: Fix Committed Status in base-files source package in Mantic: Fix Committed Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
I have performed the SRU verification with the following script:
--
#!/bin/bash
set -e
series=$1
name=$series-dev
function cleanup {
lxc delete $name --force
}
function on_err {
echo -e "Test Failed"
cleanup
exit 1
}
trap on_err ERR
lxc launch ubuntu-daily:$series $name
sleep 5
# Install latest base-files
lxc exec $name -- apt-get update > /dev/null
lxc exec $name -- apt-get install -y base-files > /dev/null
echo -e "\n* Latest base-files is installed"
echo "###"
lxc exec $name -- apt-cache policy base-files
echo -e "###\n"
echo -e "\n* Installing update-motd"
lxc exec $name -- apt-get install -y update-motd > /dev/null
echo -e "###\n"
echo -e "\n* Check current MOTD message for Support URL"
echo "###"
lxc exec $name -- update-motd
echo -e "###\n"
echo -e "\n* base-files is installed from proposed"
echo "###"
lxc exec $name -- sh -c "echo \"deb http://archive.ubuntu.com/ubuntu
$series-proposed main\" | tee /etc/apt/sources.list.d/proposed.list"
lxc exec $name -- apt-get update > /dev/null
lxc exec $name -- apt-get -t $series-proposed install base-files -y > /dev/null
lxc exec $name -- apt-cache policy base-files
echo -e "###\n"
echo -e "\n* Check updated MOTD message fro Support URL"
echo "###"
lxc exec $name -- update-motd
echo -e "###\n"
cleanup
--
I can confirm that URL has been successfully updated for the MOTD message.
I am also attaching the test results for all the releases target by this change
** Attachment added: "base-files-test-result.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+attachment/5736850/+files/base-files-test-result.tar.xz
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy verification-needed-lunar
verification-needed-mantic verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-jammy verification-done-lunar
verification-done-mantic verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2046356
Title:
Update URL for Support information in MOTD message
Status in base-files package in Ubuntu:
Fix Released
Status in base-files source package in Xenial:
Fix Committed
Status in base-files source package in Bionic:
Fix Committed
Status in base-files source package in Focal:
Fix Committed
Status in base-files source package in Jammy:
Fix Committed
Status in base-files source package in Lunar:
Fix Committed
Status in base-files source package in Mantic:
Fix Committed
Status in base-files source package in Noble:
Fix Released
Bug description:
[Impact]
When users see the MOTD message, they are currently seeing an outdated url
under the support information.
Even though the outdated url redirects to new Ubuntu Pro webpage, we believe
the users should still see
the correct url from the start
[Test Case]
- Launch a LXD container for any of the affected releases
- Install the package with this fix applied
- Install `update-motd` package
- Run `update-motd` and confirm the Support url is now the correct one
[Regression Potential]
If users are parsing MOTD for some reason, the url change might break that
logic now. However, parsing MOTD messages is not a supported flow, so we
believe regression potential is low here.
[Discussion]
Since we want users to be aware of what Ubuntu Pro is, we should highlight
the right product name on any place that is still using the old "advantage"
name. Updating the support URL here is a step into this direction
[Original Bug Description]
On the file 10-help-text, we are printing the following line on MOTD:
* Support: https://ubuntu.com/advantage
We should update the url to https://ubuntu.com/pro instead, as this
will the default url for support information now
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
** Changed in: base-files (Ubuntu Xenial) Status: New => In Progress ** Changed in: base-files (Ubuntu Bionic) Status: New => In Progress ** Changed in: base-files (Ubuntu Focal) Status: New => In Progress ** Changed in: base-files (Ubuntu Jammy) Status: New => In Progress ** Changed in: base-files (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Status in base-files source package in Jammy: In Progress Status in base-files source package in Mantic: In Progress Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
** Description changed: + + [Impact] + When users see the MOTD message, they are currently seeing an outdated url under the support information. + Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see + the correct url from the start + + [Test Case] + + - Launch a LXD container for any of the affected releases + - Install the package with this fix applied + - Install `update-motd` package + - Run `update-motd` and confirm the Support url is now the correct one + + [Regression Potential] + If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. + + [Discussion] + Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction + + [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046356] [NEW] Update URL for Support information in MOTD message
Public bug reported: On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: base-files (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - Update URL for Support information for MOTD message + Update URL for Support information in MOTD message -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965138] [NEW] Desktop application should check for service available information before listing it
Public bug reported: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "jammy-desktop-error.png" https://bugs.launchpad.net/bugs/1965138/+attachment/5569662/+files/jammy-desktop-error.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965138 Title: Desktop application should check for service available information before listing it Status in software-properties package in Ubuntu: New Bug description: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial
Hi Robie, I just realized that I forgot to change the tag when I posted
my test process :(
This is the reason why this package is not on the -updates pocket yet,
right ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
Users are prompted by ucf on upgrade from Trusty to Xenial
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because the user can make an uninformed decision of
keeping the old config file, which will make unattended-upgrades to not work as
we expect.
[Test case]
To reproduce the issue, you can:
1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with
the 50unattended-upgrades change
To verify that the error is fixed:
1. Launch a trusty vm
2. Import this ppa into the system:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the
expected 50unattended-upgrades config file
[Where problems could occur]
The changes in this package should only surface during an upgrade
operation. With this change, we are now delivering a new file to the
system and configuring postinst to use it. Because of that, we believe
this is the only scenario that could be affected in case of a
regression is discovered in the package.
[Discussion]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change
prompt no longer happens from trusty to xenial.
Since we are modifying are features on unattended-upgrades, just
adding a new file to package, we don't believe there is any regression
potential
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
Users are prompted by ucf on upgrade from Trusty to Xenial
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because the user can make an uninformed decision of
keeping the old config file, which will make unattended-upgrades to not work as
we expect.
[Test case]
To reproduce the issue, you can:
1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with
the 50unattended-upgrades change
To verify that the error is fixed:
1. Launch a trusty vm
2. Import this ppa into the system:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the
expected 50unattended-upgrades config file
[Where problems could occur]
The changes in this package should only surface during an upgrade
operation. With this change, we are now delivering a new file to the
system and configuring postinst to use it. Because of that, we believe
this is the only scenario that could be affected in case of a
regression is discovered in the package.
[Discussion]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change
prompt no longer happens from trusty to xenial.
Since we are modifying are features on unattended-upgrades, just
adding a new file to package, we don't believe there is any regression
potential
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial
Thanks for the review Robie, I have tested the package on the proposed pocket by using this script: #!/bin/sh set -x series=trusty name=$series-upgrade multipass delete $name multipass purge multipass launch $series --name $name multipass exec $name -- sudo sh -c "cat
[Touch-packages] [Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial
Thank you for this review Robie, we have now updated the package to only
ship two md5sum. The latest version of 50unattended-upgrades of Trusty
and Xenial.
I have already updated the MR with those changes and I Bryce is
reviewing that changes before uploading the new package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
Users are prompted by ucf on upgrade from Trusty to Xenial
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Triaged
Bug description:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because the user can make an uninformed decision of
keeping the old config file, which will make unattended-upgrades to not work as
we expect.
[Test case]
To reproduce the issue, you can:
1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with
the 50unattended-upgrades change
To verify that the error is fixed:
1. Launch a trusty vm
2. Import this ppa into the system:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the
expected 50unattended-upgrades config file
[Where problems could occur]
The changes in this package should only surface during an upgrade
operation. With this change, we are now delivering a new file to the
system and configuring postinst to use it. Because of that, we believe
this is the only scenario that could be affected in case of a
regression is discovered in the package.
[Discussion]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change
prompt no longer happens from trusty to xenial.
Since we are modifying are features on unattended-upgrades, just
adding a new file to package, we don't believe there is any regression
potential
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial
I will further increase this SRU bug with information that is lacking on
from the original bug proposal:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because the user can make an uninformed decision of
keeping the old config file, which will make unattended-upgrades to not work as
we expect.
[Test case]
To reproduce the isse, you can:
1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with the
50unattende-upgrades change
To verify that the error is fixed:
1. Launch a trusty vm
2. Import this ppa into the system:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the expected
50unattended-upgrades
config file
[Where problems could occur]
The changes is this package should only be surface during an upgrade
operation. Because we are now delivering a new file to the system and
configuring postinst to use it. Because of that, we believe this is the
only scenario that could be affect in case of a regression is discovered
in the package.
---
Finally, if there is any additional information that I need to add to
this SRU, just let me know and I will provide it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to
1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Status in unattended-upgrades package in Ubuntu:
New
Status in unattended-upgrades source package in Xenial:
Triaged
Bug description:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test Case]
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change
prompt no longer happens from trusty to xenial.
[Regression Potential]
Since we are modifying are features on unattended-upgrades, just adding a new
file to package, we don't believe there is any regression potential
[Discussion]
== End SRU Template ==
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915547] [NEW] sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Public bug reported:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 2020-02-17
18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test Case]
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change prompt
no longer happens from trusty to xenial.
[Regression Potential]
Since we are modifying are features on unattended-upgrades, just adding a new
file to package, we don't believe there is any regression potential
[Discussion]
== End SRU Template ==
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
** Affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to
1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Status in unattended-upgrades package in Ubuntu:
New
Status in unattended-upgrades source package in Xenial:
New
Bug description:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test
