E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)

[TJ]

20.04.1, when applying updates, 'full log' is reporting for every package install:

E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)

This should either be corrected (by mounting devpts into the /target/ or redirecting the error to /dev/null to avoid causing the administrator wasting time trying to determine if there's a fault with the installation.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mark (dkx888)]

On a vanilla Ubuntu Server Installation (20.04) I always get multiple errors of:
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device).

This problem still seems to exist.

[v. (tishma)]

Is there any workaround for this? Latest Ubuntu Server 20.04 installation is having this failure in a loop :(

[justin (jlintz)]

Confirmed this as of 20.04.3 as well

[Iusico Maxim (iusmac)]

Same problem on Ubuntu Server (21.10). Got an infinite loop after installation
completed and updates started installing.

As workaround I simply switched to tt2 (Ctrl+Alt+F2) and forced to reboot:
$ systemctl reboot -i

Then, manually upgrade once logged in:
$ sudo apt upgrade

[Besmir Zanaj (besmirzanaj-gmail)]

My builds of Ubuntu 18.04 with packer were ~12-20 mins. With subiquity and these new "features" it takes 45+ minues and I am spending more time dealing with bugs rather than building systems. Please fix these crucial things.

@ubuntu team: If you introduce these bugs, at least leave debian installer in place till you fix these. It does not make any sense to replace a fully functioning technology with something that hasn't been fully tested.

https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1901482
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975

[Dan Bungert (dbungert)]

It seems there are two different conversations happening on this bug:

1) Dozens of instances of "E: Can not write log" in the installation journal but the install otherwise appears OK

2) Infinite loop during installation

What needs to be done about the "E: Can not write log" messages is clear. I'm less clear how to produce the infinite loop during installation. If someone can provide reproduction steps for the infinite loop, that would help. Thanks.

[sharif uddin (shorif2000)]

i came across this. my host hardware running ubuntu 22.04 lts

using kvm to spin a vm again ubuntu 22.04lts during this install:

once it reaches the end of the install it goes in endless loop so i just select "cancel update and reboot" which also takes a while to happen

[djzhu (djzhu)]

I deploy ubuntu 18.04 on virtualbox meet this problem.
Came across this by just reboot the system force after select "cancel update and reboot" options.