** Description changed:
When a port's value_specs are updated via a stack update action, the
current value_specs content is wiped and replaced with the new values.
This causes issues in various use cases. For example:
- An SRIOV port has 'binding:profile' data such as {pci_slot=':17
** Description changed:
When a port's value_specs are updated via a stack update action, the
current value_specs content is wiped and replaced with the new values.
This causes issues in various use cases. For example:
- An SRIOV port has 'binding:profile' data such as {pci_slot=':17
Public bug reported:
When a port's value_specs are updated via a stack update action, the
current value_specs content is wiped and replaced with the new values.
This causes issues in various use cases. For example:
- An SRIOV port has 'binding:profile' data such as {pci_slot=':17:02.1',
pci_
sos tests on Noble:
---
*** LXD container:
- tar file created correctly
- sos file correctly uploaded
- no relevant errors in sos_logs/sos.log
- logs collected but issues with:
- ubuntu-advantage* as the package name has changed and it's now
ubuntu-pro* meaning that these lo
Some extra analysis:
I believe the issue was introduced by commit [1] which seems to have
landed in Wallaby.
When trusts are used and based on the changes added by that commit when
the trust is getting regenerated due to the use of a different user, a
new set of creds is generated but only for th
Tested 4.7.2-0ubuntu1~22.04.2 From jammy-updates, same issues with
obfuscation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091858
Title:
[sru] sos upstream 4.8.2
To manage notifications about t
Did some testing in Focal and Jammy:
Jammy:
- tar file created correctly
- no errors in sos_logs/sos.log
- logs collected
- certs and passwords seemingly obfuscated
- no error log file
- IPs and MACs not correctly obfuscated (can see qti a few occurrences, for
example in run/systemd/network/, va
Public bug reported:
Summary:
When a stack is created with a certain user,
"reauthentication_auth_method=trusts" and an update is triggered, the
update will fail with the below error:
$ openstack stack resource list -n 5 teststack
+---+--+
Moved to https://github.com/canonical/lxd/issues/14418
** Bug watch added: github.com/canonical/lxd/issues #14418
https://github.com/canonical/lxd/issues/14418
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
When systemd’s CPUaffinity is used in Ubuntu 22.04 it does not get
applied if the LXD snap version <6.1 is installed. See below:
# with lxd installed, affinity not honored
ubuntu@test:~$ grep -i affinity /etc/systemd/system.conf
CPUAffinity=0-1
ubuntu@test:~$ sudo taskset -c
reported upstream here:
https://storyboard.openstack.org/#!/story/2011251
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085966
Title:
Port extra properties ignored when a port is created via
OS::
For anyone else who stumbles upon this issue, the workaround is to
create the port using OS::Neutron::Port and attach it to the instance
instead of implicitly creating the port via OS::Nova::Server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
When you create a port via OS::Nova::Server, if you only specify a
network ID then the extra properties you pass in the template are
ignored as per the code below:
heat/engine/resources/openstack/nova/server.py:
handle_create()
\_ _build_nics()
\_ if t
Public bug reported:
When you create a port via OS::Nova::Server, if you only specify a
network ID then the extra properties you pass in the template are
ignored as per the code below:
heat/engine/resources/openstack/nova/server.py:
handle_create()
\_ _build_nics()
\_ if there's a port in the
** Description changed:
When you create a port via OS::Nova::Server, if you only specify a
network ID then the extra properties you pass in the template are
ignored as per the code below:
heat/engine/resources/openstack/nova/server.py:
handle_create()
\_ _build_nics()
- \_ if t
tracked upstream here: https://storyboard.openstack.org/#!/story/2011249
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085409
Title:
Heat wrongly passing "no_fixed_ips" to Neutron
To manage notifi
Public bug reported:
When creating nested stacks using OS::Heat::ResourceGroup, I've found
that even if I set heat_template_version in the templates, the version
that gets picked up by the nested stack is always the Kilo version,
i.e., 2015-04-30.
The reason why this happens is because, upon crea
Public bug reported:
Summary:
When creating an instance via the "OS::Nova::Server" resource type in a Heat
template, specifying a network and a subnet to get a port created on the
instance, it fails as below:
2024-10-21 15:11:27.924 5089 ERROR heat.engine.resource nic_info['p
I deployed single-node sunbeam on 22.04 and collected a sosreport using
4.7.2, notes on the testing below:
* No plugin warning or errors, or any errors on the sos logs.
* Hit this issue: https://github.com/sosreport/sos/issues/3683. So re-run the
sosreport w/o --all-logs
* Everything in /var/sna
*** This bug is a duplicate of bug 2065081 ***
https://bugs.launchpad.net/bugs/2065081
I'm also seeing these error messages which could be more relevant:
2024-06-05T09:19:52.551520+02:00 pc gnome-shell[164087]: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in
*** This bug is a duplicate of bug 2065081 ***
https://bugs.launchpad.net/bugs/2065081
I'm seeing a similar behavior and have no graphic cards on my machine
(using the integrated graphics from my AMD CPU). Among other error
messages I'm seeing the below:
2024-06-05T09:19:16.960412+02:00 pc gs
I agree, a user-configured setting should be honored. Another thing to
consider is that according to the Jammy systemd.network man page, the
default should be 'ipv6' so one would expect that to be a global
default, but it gets overridden for link-local IPs due to this commit.
[1] https://manp
Public bug reported:
A customer reported network disconnections on their storage
servers when running 'netplan apply'. The culprit was that
they have link-local addresses configured and the Duplicate
Address Detection (DAD) mechanism was delaying the interfaces
from coming back up.
As a worka
We have at least a customer on Ubuntu Xenial who hits this somewhat
regularly and would very much appreciate this fix getting into SRU
as quickly as possible.
Would you please consider moving this forward using the fastest
path available?
--
You received this bug notification because you are
The same issue on my Lenovo T14s, frequently hanging after suspend. I'm
using Ubuntu 20.04, with HWE kernel version 5.8.0-40-generic. I have two
external monitors with 1980x1080 res, connected through a 2xHDMI to
USB-C connector using DisplayLink.
This is really annoying! Are there any efforts bei
** Also affects: sudo (Ubuntu Bionic)
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/1895757
Title:
Terminal hangs running sudo when "use_pty" is set in /e
** Description changed:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2
** Description changed:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
- Steps to reproduce:
+ Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on
Public bug reported:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2) Ensure that /et
29 matches
Mail list logo
