Public bug reported:
On Ubuntu Core 24 calling the command line
useradd --extrausers --groups somegroup somenewuser
... fails with:
useradd: cannot lock /etc/group; try again later.
It worked on 22.04. /etc is not writable. It also fails if somegroup is
a group in extrausers.
** Affects:
I have looked into it a bit. I have noticed that some functions were not
inlined in 5.15, but were inlined in 5.4. For example `lzma_literal` and
`lzma_match` (see difference in System.map). After removing
`CONFIG_DEBUG_SECTION_MISMATCH=y` from `debian/rules.d/0-common-vars.mk`
(I am not sure why
Public bug reported:
On 2.1-14-g2e17a0d6-0ubuntu1~22.04.3
`cloud-init status` reports `status: not-run` even though
`/usr/lib/systemd/system-generators/cloud-init-generator` has run as
generator and marked it as disabled.
The right status which is also what focal gives is `status: disabled`.
We have a related issue in Ubuntu Core 22. It fails the same way. But in
our case it fails because systemd-networkd is not running, because
subiquity has stopped it before calling "netplan apply". And then
"networkctl reload" of course fails.
Was systemd-networkd running when you called "netplan