> Separately we really ought to port networkd from dbus communication to
varlink such that it can be used safely on critical boot path. The rest
of the Systemd critical components are already using varlink.
+1
> did you mean to mark Ubuntu(Systemd) as affected?
Yes, I'll update that thanks.
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Upstream PR landed with a fix for this issue allowing cloud-init to ignore
duplicate macs as seen on mellanox subordinate devices.
https://github.com/canonical/cloud-init/pull/1853.
We have also released this into Ubuntu Lunar 23.04 as cloud-init version
22.4-0ubuntu4.
Our plan is also to
Public bug reported:
Cloud-init is seeing intermittent failures while running `netplan
apply`, which appears to be caused by a missing resource at the time of
call.
The symptom in cloud-init logs looks like:
Running ['netplan', 'apply'] resulted in stderr output: Failed to
connect system bus:
Reviewed: https://review.opendev.org/c/openstack/neutron/+/865032
Committed:
https://opendev.org/openstack/neutron/commit/0ef4f988254457ae460f192a334ccd6776688afb
Submitter: "Zuul (22348)"
Branch:master
commit 0ef4f988254457ae460f192a334ccd6776688afb
Author: Slawek Kaplonski
Date: Fri
Public bug reported:
When try to create a health monitor on OVN LBs using the API to create
fully populated loadbalancers, where the pool object will include the
information about the HM to be created.
These become stuck in PENDING_CREATE and is not functional at all. If I
delete it, the LB it
Public bug reported:
Originally reported at:
https://bugzilla.redhat.com/show_bug.cgi?id=2093901
Prerequisites:
1. OVN 21.09+ that includes
https://github.com/ovn-org/ovn/commit/3ae8470edc648b7401433a22a9f15053cc7e666d
2. Existing metadata namespace created by OVN agent before commit
Public bug reported:
See failed test
tempest.api.compute.admin.test_security_groups.SecurityGroupsTestAdminJSON.test_list_security_groups_list_all_tenants_filter
in
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_63d/614484/10/check/tempest-
Public bug reported:
The nova-api raises exception on attempt to get VMs sorted by i.e.
task_state key.
Here are steps-to-reproduce:
- create two VMs: vm1 in ACTIVE state (cell1) and vm2 in ERROR state (cell0)
- try to list servers sorted by sort_key=task_state
[root@node0 ~]# openstack server
** Tags added: ovs
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1996788
Title:
The virtual network is broken on the node after
Public bug reported:
Several occurrences during the last day:
*
https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_578/864215/2/check/neutron-ovs-tempest-multinode-full/5780784/testr_results.html
*
This issue was fixed in the openstack/neutron rocky-eol release.
** Changed in: cloud-archive/rocky
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron stein-eol release.
** Changed in: neutron/stein
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron rocky-eol release.
** Changed in: neutron/rocky
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron stein-eol release.
** Changed in: cloud-archive/stein
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron rocky-eol release.
** Changed in: cloud-archive/rocky
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron queens-eol release.
** Changed in: cloud-archive/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron queens-eol release.
** Changed in: neutron/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This issue was fixed in the openstack/neutron queens-eol release.
** Changed in: cloud-archive/queens
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Description
===
This is not a Nova bug per se, but rather an issue with Arista and potentially
other network fabrics.
I have observed a case where VMs are inaccessible by network traffic
after live migrating on certain fabrics, in this case, Arista VXlan,
despite
20 matches
Mail list logo
