Subject: Fixed in cloud-init version 22.2.
Comment: This bug is believed to be fixed in cloud-init in version 22.2. If
this is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
module ssh-authkey-fingerprints fails Input/output error:
I've fixed this in https://github.com/canonical/cloud-
init/pull/1340/files (sadly blocked on getting the CLA signed)
I'm interested that you've hit this too @tony-casanova-nc-33-2017.
FWIW, I'm using:
- cloud-init 22.1
- I'm on a Microsoft OS called 'Mariner'
- I'm on VMware vSphere V7 -> I've
I just hit this today (Nutanix AHV) cloud-init also.
From "/var/log/cloud-init.log".
2022-03-16 16:25:18,764 - util.py[WARNING]: Running module
ssh-authkey-fingerprints ()
failed
2022-03-16 16:25:18,764 - util.py[DEBUG]: Running module
ssh-authkey-fingerprints ()
failed
Traceback (most
Andrew, yes, I think that's a reasonable solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
module ssh-authkey-fingerprints fails Input/output error: /dev/console
To manage
I've also hit this (on VMware), and while I suspect that may be due to
some particular funnies of the OS I am on, I agree a defensive fix in
cloud-init to not raise an Exception if you can't write to /dev/console
and fall back to writing to stdout would be welcomed.
Any objections if I raise a PR
Ran into this problem with VMware / OVA setup, took a really long time to
figure out what the problem was. But now after realizing that the problem is
the non-functional /dev/console, isn't thix problem clearly in the image
creation?
Since the OVA doesn't have a serial port configured into the
This also affects .ova cloud-image deployments on ESXi/vSphere, not surprising
since it's similar to what John describes in comment 15. I think this is caused
by the kernel parameter console=ttyS0 and the underlying VM having no serial
port. This should not fail cloud-init and a similar bug was
The code causing the failure (which Paride linked to) does specifically
know that the output is destined for /dev/console:
if console:
conpath = "/dev/console"
if os.path.exists(conpath):
with open(conpath, 'w') as wfh:
wfh.write(text)
There are a slew of bugs and apparently random fallout of /dev/console not
working.
In my opinion, its really *not* helpful to just ignore that 'write' to stdout
fails. Ignoring errors is never really a solution. In this case, cloud-init
may have specifically opened /dev/console. But in
Thanks John for the reproducer.
(Per standup discussion) what we can do is probably handle the case
where /dev/console exists but can't be written to more gracefully. I
think this is the only place where /dev/console is written to:
https://github.com/canonical/cloud-
Thanks John for the reproducer steps and also for the options for
workaround this issue. It does seem like a valid bug that cloud-init
could address.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
This can also be configured to pass by having virtualbox provide a
serial console connect:
1. select image on Left, right click and choose Settings, or hit ctrl+s
2. Choose Serial Ports
3. Enable Port 1 as follows:
a. Enable
b. COM1
c. IRQ: 4
d. I/O Port: 0x3F8
e. Port Mode: Raw File
I can reproduce locally doing the following (fails on focal and groovy).
I did this using the cloud-images.ubuntu.com VMDK, Virtualbox, and a
simple cloud-init with ssh key and username/pw w/ ssh pw auth on. I got
the following error:
```
2020-10-28 13:32:33,680 - util.py[WARNING]: Running module
The problem I hit (LP: #1896604) is not a cloud-init bug.
It seems that nobody stumbled on the original issue in the last ~4
years. Lacking activity and a reproducer I'm marking this as Incomplete,
let's see if anybody chimes it claiming it still affects them.
** Changed in: cloud-init (Ubuntu)
I reset the bug status as after >4 years it may be time to retriage it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
module ssh-authkey-fingerprints fails Input/output error:
This is a linux-aws kernel issue, filed:
https://bugs.launchpad.net/cloud-images/+bug/1896604
We may want to discuss if cloud-init should handle errors in writing to
/dev/console more gracefully.
** Changed in: cloud-init (Ubuntu)
Assignee: Wesley Wiedenmeier (wesley-wiedenmeier) =>
Focal:
root@ip-172-31-24-163:~# dmesg | grep console
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1024-aws
root=PARTUUID=a2f52878-01 ro console=tty1 console=ttyS0
nvme_core.io_timeout=4294967295 panic=-1
[2.184073] ACPI: SPCR: console: uart,mmio,0xc5a0,115200
[
On Focal:
root@ip-172-31-24-163:~# ls -l /dev/console
crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console
root@ip-172-31-24-163:~# echo x > /dev/console
root@ip-172-31-24-163:~#
On Groovy:
root@ip-172-31-20-184:~# ls -l /dev/console
crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console
This is now consistently happening with the Groovy daily images on
i3.metal EC2 instances. Logs attached.
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1473527/+attachment/5412940/+files/cloud-init.tar.gz
--
You received this bug
I modified the script that I wrote to try to reproduce this error and
was able to consistantly see IO errors when the script was added to the
cloud-config-archive being passed to an image. Instead of writing only
to either /dev/console or the real serial device which was /dev/ttyS0
here, each
Something interesting I noticed while looking into this is that when
xenial images are booted without "net.ifnames=0" the
/var/lib/cloud/instance/ directory is not populated. Even if no
datasource is provided for the image it should still create a blank
cloud-config.txt and the directory structure
I don't think that this is related to the cloud-final.service file
including StandardOutput=journal+console, the issue occurs in the same
situations as before with standard output being redirected only to
journal, or to console or to neither
--
You received this bug notification because you are
I spent a while trying to reproduce this well:
- I tried many vm configurations running 'serial-shell-looper', both manually
and started by cloud-init but it didn't break
- I wrote a similar script using util.meta_log to see if the difference in
implementation between python open()
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
module
I've seen this reproduce more and more in curtin tests lately in xenial:
https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15/artifact/output/XenialBcacheBasic/logs/install-serial.log/*view*/
I've seen this reproduce more and more in curtin tests lately in xenial:
https://server-team-jenkins.canonical.com/job/curtin-vmtest-venonat-devel/15/artifact/output/XenialBcacheBasic/logs/install-serial.log/*view*/
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473527
Title:
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
My current guess on this is that the issue stems from
/lib/systemd/system/cloud-final.service
having:
StandardOutput=journal+console
and then also trying to directly write to /dev/console via 'multi_log'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My current guess on this is that the issue stems from
/lib/systemd/system/cloud-final.service
having:
StandardOutput=journal+console
and then also trying to directly write to /dev/console via 'multi_log'.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
i attempted to just have multiple programs open /dev/console (or
/dev/ttyS1) and catch a failure to write in parallel, but couldnt seem
to catch it. heres the attempt.
** Attachment added: serial-shell-looper
i attempted to just have multiple programs open /dev/console (or
/dev/ttyS1) and catch a failure to write in parallel, but couldnt seem
to catch it. heres the attempt.
** Attachment added: serial-shell-looper
33 matches
Mail list logo
