DistUpgradeViewNonInteractive crashes / requires interaction
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Cosmic |
Invalid
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Invalid
|
Medium
|
Unassigned | ||
ubuntu-release-upgrader (Ubuntu) |
Fix Released
|
Medium
|
Brian Murray | ||
Bionic |
Fix Released
|
Undecided
|
Brian Murray | ||
Cosmic |
Fix Released
|
Undecided
|
Brian Murray | ||
Disco |
Fix Released
|
Undecided
|
Brian Murray | ||
Eoan |
Fix Released
|
Medium
|
Brian Murray |
Bug Description
[Impact]
The NonInteractive view of ubuntu-
[Test Case]
You need to create a situation where you'll receive a conffile prompt since the handling of those is broken.
1) On a bionic system modify /etc/update-
2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeView
3) Observe the upgrade hang on the '/etc/update-
"2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-
2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile"
With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging.
[Regression Potential]
The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong.
[Original Description]
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeView
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.
/sbin/ldconfig.
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/
Configuration file '/etc/cron.
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile
Changed in apt (Ubuntu): | |
importance: | Undecided → Medium |
Changed in ubuntu-release-upgrader (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Brian Murray (brian-murray) |
tags: | removed: rls-ee-incoming |
description: | updated |
tags: | added: id-5cd5d40bf1c69c651a522b2f |
description: | updated |
description: | updated |
tags: |
added: verification-done-cosmic removed: verification-needed-cosmic |
Changed in ubuntu-release-upgrader (Ubuntu Bionic): | |
assignee: | nobody → Brian Murray (brian-murray) |
status: | New → In Progress |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in apt (Ubuntu Eoan): | |
status: | Incomplete → Invalid |
Changed in apt (Ubuntu Disco): | |
status: | Confirmed → Won't Fix |
Changed in apt (Ubuntu Cosmic): | |
status: | Confirmed → Invalid |
Changed in apt (Ubuntu Bionic): | |
status: | Confirmed → Invalid |
If I remember correctly David was having a similar issue when upgrading some charm systems. Is that right David?