Users are prompted by ucf on upgrade from Trusty to Xenial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unattended-upgrades (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Lucas Albuquerque Medeiros de Moura |
Bug Description
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-
[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-
To verify that the error is fixed:
1. Launch a trusty vm
2. Import this ppa into the system:
https:/
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-
[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-
--- /etc/apt/
+++ /etc/apt/
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-
+ "${distro_
"${distro_
// 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_
+ "${distro_
+ "${distro_
// "${distro_
// "${distro_
// "${distro_
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-
- Add 50unattended-
- Add md5sum of the current xenial 50unattende-
- 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:/
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-
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-
config files
* data: add xenial md5sum of 50unattented-
* debian/postint: make ucf command reference the md5sum history file
Changed in unattended-upgrades (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Lucas Albuquerque Medeiros de Moura (lamoura) |
description: | updated |
summary: |
- sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to - 1.1ubuntu1.18.04.7~16.04.7 ) Xenial + Users are prompted by ucf on upgrade from Trusty to Xenial |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
tags: |
added: verification-done removed: verification-needed |
I will further increase this SRU bug with information that is lacking on from the original bug proposal:
[Impact] 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.
During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-
[Test case]
To reproduce the isse, you can:
1. Launch a trusty vm upgrades change
2. Perform a do-release-upgrade and observe that you will be prompted with the 50unattende-
To verify that the error is fixed:
1. Launch a trusty vm /launchpad. net/~lamoura/ +archive/ ubuntu/ unattended- upgrades- ppa upgrades
2. Import this ppa into the system:
https:/
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-
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