Public bug reported:
Examples of failures:
https://zuul.openstack.org/build/d2f120a01f21495c8e7502cd523f562a
https://zuul.openstack.org/build/d2f120a01f21495c8e7502cd523f562a
Failing tests:
neutron.tests.unit.db.test_securitygroups_db.SecurityGroupDbMixinTestCase.test_delete_security_group_in_us
Public bug reported:
Examples of failure:
https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_187/808179/4/check/neutron-
tempest-plugin-scenario-linuxbridge/1872c37/testr_results.html
https://3889a6aa6ea3f28e18b7-a85364018f10e4ce6159c46d9b375288.ssl.cf1.
[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).
https://bugs
Reviewed: https://review.opendev.org/c/openstack/ossa/+/811181
Committed:
https://opendev.org/openstack/ossa/commit/51a1bf0699128c8ddcb7567347cee69492601091
Submitter: "Zuul (22348)"
Branch:master
commit 51a1bf0699128c8ddcb7567347cee69492601091
Author: Jeremy Stanley
Date: Mon Sep 27 15:0
Seems it's fixed with
https://github.com/openstack/neutron/commit/7f063223553a18345891bf42e88989edb67038e7,
no longer seeing issue in TripleO job:-
https://d0e3fd572414115f797b-39524de8c5a1fb89d206195b6f692473.ssl.cf5.rackcdn.com/808056/1/check/tripleo-
ci-
centos-8-standalone/6cb888b/logs/underclo
** Project changed: neutron => null-and-void
** Information type changed from Public to Private Security
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1905392
Title:
xanax online cod o
Public bug reported:
Environment:
L3 agent configuration: agent_mode=dvr_snat.
The L3 agent is located in a controller node, acting as a DVR edge router (no
HA).
Description:
When "process_floating_ip_nat_rules_for_centralized_floatingip" is called, this
method should check first if "self.snat_
Apologies, it looks like:
https://review.opendev.org/660363
is fixed in Ubuntu bionic and queens, but
https://review.opendev.org/c/openstack/nova/+/711279/
is not yet fixed in bionic (nor queens or rocky in case we need it for
upgrades).
** Changed in: cloud-archive/queens
Status: Fix Rele
This is already fixed in bionic and the queens cloud archive for Ubuntu.
** Changed in: cloud-archive
Status: New => Invalid
** Changed in: cloud-archive/queens
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, w
FYI, this bug was fixed in the upstream branch v21.06.0 this is the
patch:
https://github.com/ovn-
org/ovn/commit/578238b36073256c524a4c2b6ed7521f73aa0019
** Changed in: networking-ovn
Status: New => Confirmed
** Changed in: networking-ovn
Assignee: (unassigned) => Erlon R. Cruz (som
Public bug reported:
cloud-init fails in "crawl_metadata" phase in first boot of Ubuntu 20.04
VM on Azure cloud. After few reboots, the cloud-init succeeds in "crawl
metadata" phase and it then regenerates the ssh host keys. The
communication between hosts of the cluster is broken thereafter, and
** Changed in: nova
Status: Invalid => In Progress
--
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/1943778
Title:
No db access allowed in nova-compute:
Status in
12 matches
Mail list logo
