Reviewed: https://review.opendev.org/c/openstack/nova/+/803714
Committed:
https://opendev.org/openstack/nova/commit/d4dbcd5fa05ac2f988b65d611f71805f90411581
Submitter: "Zuul (22348)"
Branch:master
commit d4dbcd5fa05ac2f988b65d611f71805f90411581
Author: Lee Yarwood
Date: Fri Aug 6
Public bug reported:
Originally noticed in a TripleO job[1], and after enabling log service
plugin in devstack seeing the similar error in neutron service log.
Following Traceback is seen:-
ERROR neutron_lib.callbacks.manager [None
req-131d215c-1d03-48ce-a16e-28175c0f58ba
Public bug reported:
Creating a fresh bug for this as we haven't seen it in a while since the
libvirt event rewrite landed but it did just cause a gate failure...
https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_5d6/801990/6/gate/tempest-
** Also affects: neutron/stein
Importance: Undecided
Status: New
** Also affects: neutron/queens
Importance: Undecided
Status: New
** Also affects: neutron/rocky
Importance: Undecided
Status: New
** Changed in: neutron/queens
Status: New => Triaged
**
Public bug reported:
Description
===
On the live snapshot feature to have data consistency, the instance can be boot
with image property hw_qemu_guest_agent set to yes and QEMU agent install in
the image. The instance with local storage creates a disk mirror to have a copy
and the
Reviewed: https://review.opendev.org/c/openstack/nova/+/801990
Committed:
https://opendev.org/openstack/nova/commit/2209b0007fe85d7c5439e0bfdfe2120c63898fa2
Submitter: "Zuul (22348)"
Branch:master
commit 2209b0007fe85d7c5439e0bfdfe2120c63898fa2
Author: Felix Huettner
Date: Fri Jul 23
Public bug reported:
According to cloud-init document,
https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#using-instance-data
Both user-data scripts and #cloud-config data support jinja template rendering.
When the first line of the provided user-data begins with, ## template:
Public bug reported:
auto_schedule_new_network_segments() added in
Ic9e64aa4ecdc3d56f00c26204ad931b810db7599 uses new payload notification
listener in old stable branches of Neutron that still use old notify
syntax.
Following branches are affected: stable/stein, stable/rocky,
stable/queens
**
We discussed that RFE on today's drivers meeting
https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.2021-08-06-14.03.log.html#l-14
and we all agreed that current behavior is actually a feature and we shouldn't
change it. It also aligns with the comment #6 from Brian.
So
Public bug reported:
Hi,
Looking at the external networks from the edge environment I see that
these fields are None:
| provider:network_type | None |
| provider:physical_network | None |
Instead we have this:
| segments | [{'provider:network_type': 'flat',
Public bug reported:
Our md-tag-create-multiple (/v2/metadefs/namespaces/{namespace_name}/tags) [1]
API overwrites existing tags for specified namespace rather than creating new
one in addition to the existing tags.
Where as if you try to create different tags using md-tag-create
Reviewed: https://review.opendev.org/c/openstack/nova/+/801714
Committed:
https://opendev.org/openstack/nova/commit/49ba5a763f9d2c7c496f391ca8149a18541bfec7
Submitter: "Zuul (22348)"
Branch:master
commit 49ba5a763f9d2c7c496f391ca8149a18541bfec7
Author: Lee Yarwood
Date: Thu Jul 22
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1928675
13 matches
Mail list logo
