Reviewed: https://review.opendev.org/751019
Committed:
https://git.openstack.org/cgit/openstack/tacker/commit/?id=ab235df2fba385255b1f92c263befd0891d4
Submitter: Zuul
Branch:master
commit ab235df2fba385255b1f92c263befd0891d4
Author: zhoulinhui
Date: Thu Sep 10 23:03:02 2020 +0800
Reviewed: https://review.opendev.org/752067
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=68c202d38ba0648c8a71a7e4c3771ea6c6f60651
Submitter: Zuul
Branch:master
commit 68c202d38ba0648c8a71a7e4c3771ea6c6f60651
Author: Grégoire Unbekandt
Date: Tue Sep 15 15:19:43
** Changed in: nova
Status: Fix Committed => 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/1779287
Title:
placement can throw exception if
Public bug reported:
ovn_octavia_provider.tests.functional.test_integration.TestOvnOctaviaProviderIntegration.test_port_forwarding
is currently failing in the check and gate queues and is under
investigation.
Will mark unstable to get the gate Green.
** Affects: neutron
Importance:
Public bug reported:
The OVN Octavia Provider driver requires a subnet ID be present in the
API call to create a pool. Since this is an optional parameter
according to the API, it should be able to work without one. The
octavia-lib DriverLibrary class provides methods to look it up given
other
This is actually a bug in the Tempest repo, we changed the code in
neutron-tempest-plugin to be better at creating unique subnets in
https://review.opendev.org/#/c/560465/
Wondering if we need to have a similar change in Tempest.
Should we change the component or just add it as affected?
** Changed in: charm-manila-ganesha
Status: In Progress => Fix Released
** Changed in: charm-manila-ganesha
Assignee: Aurelien Lourot (aurelien-lourot) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
Description
===
Following a cinder volume retype on a volume attached to a running
instance, the instance became corrupt and cannot boot into the guest
operating system any more.
Upon further investigating it seems the retype operation failed. The
nova-compute logs
This bug was fixed in the package netplan.io - 0.100-0ubuntu4
---
netplan.io (0.100-0ubuntu4) groovy; urgency=medium
* debian/tests/cloud-init
- Improve reboot test to avoid failure on arm64
-- Lukas Märdian Mon, 21 Sep 2020
12:23:02 +0200
** Changed in: netplan.io
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Bionic)
Public bug reported:
Kuryr-Kubernetes tests running with ovn-octavia-provider started to fail
with "Provider 'ovn' does not support a requested option: OVN provider
does not support allowed_cidrs option" showing up in the o-api logs.
We've tracked that to check [1] getting introduced. Apparently
This is seems to me a deployment issue. Somehow in your environment the
python installation is broken and some of the packages are import from
python 3.7 into the python 3.6 interperter. This is not a nova issue so
I'm setting it to Invalid. If you used any kind of deployment engine
then please
The hypervisor host name is the compute node identity so if you change the
hostname you basically introduce a new compute node into the system while you
silently remove the old one from the system. If you have to change the hostname
the do it the following way:
1) disable the compute node
2)
Public bug reported:
The following three test cases are clashing when creating, at the same time, an
IPv6 subnet with the same CIDR:
- test_dhcpv6_stateless_eui64
- test_dhcpv6_stateless_no_ra
- test_dhcpv6_stateless_no_ra_no_dhcp
Log: https://61069af11b09b96273ad-
Public bug reported:
When using the Neutron CLI, if the SGs are listed and a project is
passed (as filter), even if the project does not exist, a default SG is
created for this project.
This is happening when the user has admin permissions.
Example: http://paste.openstack.org/show/798194/
This
Public bug reported:
In case if there is e.g. SG rule which allows SCTP traffic defined by user,
iptables firewall driver will match such traffic always, even if it's marked as
INVALID by conntrack.
It is like that due to order of rules in iptables:
Chain neutron-openvswi-i0133d93d-e (1
Reviewed: https://review.opendev.org/725397
Committed:
https://git.openstack.org/cgit/openstack/masakari/commit/?id=97e658417b691f6f737599c59726cc49131b05ef
Submitter: Zuul
Branch:master
commit 97e658417b691f6f737599c59726cc49131b05ef
Author: Corey Bryant
Date: Mon May 4 17:11:13 2020
Reviewed: https://review.opendev.org/737261
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=84d4fe177b75569628aec96e43b709b8e29b9e05
Submitter: Zuul
Branch:master
commit 84d4fe177b75569628aec96e43b709b8e29b9e05
Author: LIU Yulong
Date: Tue Mar 10 00:49:44 2020
Public bug reported:
nova fails to correctly account for resources after hypervisor name
changes. For example, if previously the hypervisor name is A, and some
later it switches to A.B, then all of the instances which belong to A
will not be included in the resource computation for A.B although
Public bug reported:
When the content of the float IP port forwarding rule is updated, if the
updated internal_ Ip_ Address and internal_ port_ If the IP address
corresponding to the ID does not match or does not belong to the same route,
the HTTP return code 200 does not report an error；
20 matches
Mail list logo
