Public bug reported:
After providing a patch to bind sriov vfs in mlnx devices after moving to
switchdec, we saw in some cases that the names of the representors were
reserved before for the vfs and that failed to get the old names again of the
vfs after binding them and name them as ethX.
This
It is fixed by https://review.opendev.org/c/openstack/horizon/+/774922
** Changed in: horizon
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad
As mentioned in the above comments it is already fixed by
https://review.openstack.org/c/614893/.
So changing bug status to Fix Released and regarding the same issue in Queen
and Rocky branch, you
can apply the same fix in your env. I don't have an evn. to check if above
patch not work in the ol
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
Public bug reported:
Description
===
I have performed fault injection in openstack nova by changing the code of
compute/api.py (inserting a representative/probable bug) and then ran the unit,
functional and integration tests and discover that some of the bugs inserted
were not detected
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-oslo.privsep (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Hirsu
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1853613
Title:
VMs don't get ip from dhcp after compute resta
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1864822
Title:
Openvswitch Agent - Connexion openvswitch DB B
*** This bug is a duplicate of bug 1841104 ***
https://bugs.launchpad.net/bugs/1841104
Marked as a duplicate: the good news is that we've released a fix for
this!
** This bug has been marked a duplicate of bug 1841104
Openstack's vendor_data2.json is not handled
--
You received this bug
*** This bug is a duplicate of bug 1841104 ***
https://bugs.launchpad.net/bugs/1841104
** This bug is no longer a duplicate of bug 1829410
vendor_data2 not supported
** This bug has been marked a duplicate of bug 1841104
Openstack's vendor_data2.json is not handled
--
You received this
** Summary changed:
- Images v2 api metadef vulnerability
+ [OSSN-0088] Images v2 api metadef vulnerability
** Also affects: ossn
Importance: Undecided
Status: New
** Changed in: ossn
Status: New => Fix Released
** Changed in: ossn
Importance: Undecided => Critical
** Chang
We'll be switching this bug public shortly along with bug 1916926 under
a single publication (OSSN-0088).
** Description changed:
- This issue is being treated as a potential security risk under
- embargo. Please do not make any public mention of embargoed
- (private) security vulnerabilities bef
Yes, I think it's
https://review.opendev.org/c/openstack/neutron/+/760967 but you're
right, it's fixed now. Thanks for pointing it out!
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
** Description changed:
- This issue is being treated as a potential security risk under
- embargo. Please do not make any public mention of embargoed
- (private) security vulnerabilities before their coordinated
- publication by the OpenStack Vulnerability Management Team in the
- form of an offi
Fixed by https://review.opendev.org/c/openstack/neutron/+/758391
** Changed in: neutron
Status: In Progress => Fix Released
** Changed in: neutron
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
Public bug reported:
I spent some time understanding how to rescue instances which are boot-
from-volume.
After finding a setup which would rescue instances properly with
hw_rescue_device=disk and hw_rescue_bus=usb, switching the rescue bus to
hw_rescue_bus=scsi resulted in an Ubuntu Focal instan
Public bug reported:
>From an environment where all storage is on ceph, it was not possible to
omit the --image parameter when rescuing a boot-from-volume instance as
suggested near the end of this doc:
https://docs.openstack.org/nova/latest/user/rescue.html
The doc implies that omitting --image
Public bug reported:
"network_vlan_ranges" allows to define a list of physical networks and
VLAN ranges [1]. But is possible to just define the physical network
without the VLAN ID ranges; in that case, the VLAN driver should take
all valid VLAN IDs (from 1 to 4094).
If no VLAN range is defined,
After https://review.opendev.org/c/openstack/neutron/+/778080 was merged
I didn't saw it anymore in CI. So I'm closing that LP now.
** Changed in: neutron
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1881095
Title:
[OVN] Router availability zones support
Status in neutron
Job has been fixed at DevStack:
https://review.opendev.org/c/openstack/devstack/+/753575
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchp
Fixed at: https://review.opendev.org/c/openstack/neutron/+/768277
** Changed in: neutron
Status: New => Fix Committed
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is su
Public bug reported:
Error example:
https://40b5766ce602bfb4b663-445d4465f34d2b24df5d805a76ff9803.ssl.cf1.rackcdn.com/765846/7/check
/neutron-functional-with-uwsgi/928e7cf/testr_results.html
Stacktrace:
ft1.14:
neutron.tests.functional.services.ovn_l3.test_plugin.TestRouter.test_gateway
Neutron fix is released upstream and backported all the way to Train.
** Changed in: neutron
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1896734
Titl
Public bug reported:
When having sriov configured in mlnx interfaces and we are using MLNX
ofed, In reboot case we'll have race between sriov_config service and
openibd service which loads mlx drivers, sometimes it causes failures in
starting sriov_config service correctly
** Affects: neutron
34 matches
Mail list logo
