1. This appears to be a bug with permissions on 01-network-manager-
all.yaml being too permissive which raises errors which cloud-init
treats as warnings during `netplan apply` later in boot. This is more
likely an issue with the image itself (as cloud-init doesn't write
/etc/netplan/01-network-manager.yaml. That file is more of a livecd-
rootfs artifact so I've added livecd-rootfs to this bug for triage.
2. I'm a bit confused by this bug referencing Package: cloud-init
25.1.2-0ubuntu0~24.04.1, because the attached logs all show Cloud-init
v. 24.1.3. Can you confirm what version is present in your install
environment?
3. This description appears to translate as "Test failed The equipment
fails the test." I think we'd probably prefer a more specific bug
description, it is always helpful if you can use something like
translate.google.com to make that header English for more broad
readability please.
3. From the looks of this bug, I believe your test harness doesn't like
seeing WARNINGS from cloud-init logs in cloud-init-output.log. These
warnings actually due tothe `netplan apply` call which cloud-init
invokes to apply any network config it has written to
/etc/netplan/50-cloud-init.yaml. Ideally we want livecd-rootfs to set
the appropriate permissions to root-readwrite on these files to avoid
triggering netplan apply exit non-zero.
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2119020
Title:
Проверка не удалась Оборудование не проходит проверку.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2119020/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
