Public bug reported:
It happened at least twice recently in the neutron-ovn-tempest-slow job:
https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_992/periodic/opendev.org/openstack/neutron/master/neutron-
ovn-tempest-slow/992d108/testr_results.html
https:
Well, I don't really know about the root cause and why the
map_instances() wasn't adding the cell UUID directly when it created the
record here first. Now we have a transaction like Mohamed said so it
shouldn't be a problem.
Closing this bug report now.
** Changed in: nova
Status: Incompl
Public bug reported:
Remove check for NB "Gateway_Chassis" table. This table was added in [1]
and is present since v20.03, NB schema version 5.7.0.
[1]https://github.com/ovn-
org/ovn/commit/2ba112125f1a267f5e8d9e1d6328bd1ff8ed808e
** Affects: neutron
Importance: Undecided
Status: N
Reviewed: https://review.opendev.org/c/openstack/tempest/+/874704
Committed:
https://opendev.org/openstack/tempest/commit/11d4fc9e417d5cfcd6c6075e27d052aecc69c385
Submitter: "Zuul (22348)"
Branch:master
commit 11d4fc9e417d5cfcd6c6075e27d052aecc69c385
Author: Ghanshyam Mann
Date: Tue Feb 2
Fixed in master in
https://review.opendev.org/c/openstack/nova/+/807025
** Changed in: nova
Status: New => 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/b
Public bug reported:
Description
===
Given a flavor enriched with the "quota:cpu_quota" property, creation of
servers based on it will fail on system's running under cgroups v2, complaining
that the CPU controller is unavailable even when the kernel does provide it.
Steps to reproduce
=
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) => Bernard Cafarelli (bcafarel)
** Changed in: neutron
Assignee: Bernard Cafarelli (bcafarel) => Jake Yip (waipengyip)
** Changed in: neutron
Status: New => Fix Rel
Fixed in https://review.opendev.org/c/openstack/horizon/+/847985 will
close this bug.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Y
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Y
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Y
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
This bug is believed to be fixed in cloud-init in version 23.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
Public bug reported:
In train, current version is 2.1 instead of 2.10:
(undercloud) [stack@undercloud-0 ~]$ curl http://10.10.10.10:9292 | jq .
{
"versions": [
{
"id": "v2.1",
"status": "CURRENT",
"links": [
{
"rel": "self",
"href": "http://10
it is explcitly not supproted.
we intoduced the condocutor to make sure that nova compute agents do not
have db access directly.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
Reproduced issue on the environment with TF Neutron backend and enabled
'enable_fip_topology_check' config option. OVN backend is not affected
in any case, combination of any Neutron backend and disabled
'enable_fip_topology_check' also not affected.
It is possible to remove
** Changed in: neutron
Status: New => Invalid
--
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/1463631
Title:
60_nova/resources.sh:106:ping_check_public fails inter
Per the discussion, it looks like it is a cloud misconfiguration and I
am going to mark it as invalid for the time being.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to clou
30 matches
Mail list logo
