** No longer affects: dnsmasq (Ubuntu Lunar)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2026757
Title:
dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates
Status in Ironic
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1991051
Title:
Latest cloud-init release breaks Juju on
Due to a ping on IRC I wanted to summarize the situation here as it
seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out
why and how to fix it)
- if it doesn't work at least fail to
Public bug reported:
Hi,
I've just seen this on reboot - and I have to admit I'm not even entirely sure
we have to fix this as it is a conflict of config <-> system. But let me start
with first things first.
I have a system with a whole bunch of network card.
1. a four port NetXtreme BCM5719
2.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineer
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1961832
Title:
jammy-server-cloudimg-amd64-disk-kvm.img
FYI - as planned (and now that cloud init is fixed) I'm planning to
upload this to Jammy without the path fix. There should be no issue with
that.
But planning ahead, there will later on be a backport of open-vm-tools 11.3.5
with that to >=Focal.
I checked
21.4-0ubuntu1~20.04.1
21.4-0ubuntu1~21.0
While this is important and fixed in the SRU upload of bug 1940871 - the bad
code never reached Bionic/Focal/Hirsute as it was in the interim 21.3 versions.
Therefore the bug starte for these releases is invalid (it isn't there now, and
won't be added in the ongoing SRU).
Setting the states to i
Thanks, consider this done then.
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1940899
Title:
[Feature] Please support N
Public bug reported:
Hi,
chrony did since 21.04 [1] introduce NTS support [2].
There is an article [2] and an FAQ [3] by the upstream maintainer about NTS so
that you know what it is about :-)
Furthermore this is briefly documented in the server-guide [4] and to
look at some code there is an MP
Since it might affect the ability to log into a new spawned system I
think this could be release-critical for Impish. Therefore I flagged it
like that for now - please feel free to downgrade once the root cause is
known and you think a lower rating is appropriate.
** Description changed:
Hi,
Public bug reported:
Hi,
I got to this by my systems complaining to be unable to do ssh-keygen
after deployment. Example:
$ uvt-kvm ssh --insecure impish-kvm 'ssh-keygen -b 2048 -t rsa -f ~/.ssh/id_rsa
-q -N '\'''\'''
Saving key "/home/ubuntu/.ssh/id_rsa" failed: Permission denied
I found that i
Public bug reported:
While looking for other issues I saw the following two doc issues that
could be fixed.
#1 a a
https://cloudinit.readthedocs.io/en/latest/topics/modules.html?highlight=ssh_authorized_keys#authorized-keys
it reads "connect to a a user account on a system"
#2 sudo missing
http
Public bug reported:
New impish instance fails like this:
cloud-init collect-logs
Traceback (most recent call last):
File "/usr/bin/cloud-init", line 33, in
sys.exit(load_entry_point('cloud-init==21.2', 'console_scripts',
'cloud-init')())
File "/usr/lib/python3/dist-packages/cloudinit/c
FYI, for Bionic this isn't a trivial backport.
The change as it was added later would need at least
commit 932862b8 conf: Rework and rename virDomainDeviceFindControllerModel
commit 6ae6ffd8 qemu: Introduce qemuDomainFindSCSIControllerModel
Maybe more.
It is not un-doable, but it gets into an a
>From libvirt package POV this is fixed in >=Focal (20.04) and the only
release left affected is Bionic (18.04, libvirt 4.0).
Fixing it in Bionic is IMHO worth to consider but low prio (if users can
influence, they can set an address to 8-16 and it works, only the
default-no-address use case is b
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1906266
Title:
After upgrade: "libvirt.libvirtError: Re
Public bug reported:
Hey, this certainly isn't the most important case.
But I wanted to report it to make you aware.
For bug 1732028 I was trying different configs.
One was an empty /etc/fstab with the kernel providing the iscsi root.
In that case cloud init runs and since it does not check on R
18 matches
Mail list logo
