On which version of Ubuntu did you experience this? Whilst the latest
LTS (18.04) and non-LTS (19.04) versions have moved the ntp package to
universe, they still ship with a fully working configuration. Here's an
example from a stock install on an AWS EC2 instance running disco
(19.04):
I don't think this is really the same problem. The init script for NTP
is designed to honour the settings provided by the DHCP client. In most
cases, this is expected, but when the charm is configured, users expect
the charm to manage the local settings for them without needing to
override the
@cpollock: I don't think this is invalid. This is a very poor error
message which gives no pointers about why, and causes logspam. It was
only because of your last update that I realised that I had incorrect
file permissions also.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
I agree with @addyp95 - this is a bug in how libvirt works in IPv6-only
environments, and it is still present on focal. For posterity, the
exact details of the workaround are to add the following line to
/etc/libvirt/qemu.conf:
spice_listen = "::1"
** Changed in: qemu (Ubuntu)
Status:
I've confirmed on a 20.04 system recently installed from the official
server ISO that the passphrase for the newly-created LUKS volume appears
in the following files in /var/log/installer after install:
autoinstall-user-data curtin-install-cfg.yaml curtin-install.log
installer-journal.txt
