** Also affects: neutron-dynamic-routing (Ubuntu)
Importance: Undecided
Status: New
** Changed in: neutron-dynamic-routing (Ubuntu Focal)
Importance: Undecided => High
** Changed in: neutron-dynamic-routing (Ubuntu Focal)
Status: New => Triaged
** Changed in: neutron-dynamic-
** Changed in: masakari (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: masakari (Ubuntu Groovy)
Status: New => Triaged
** Also affects: mistral
Importance: Undecided
Status: New
** Also affects: mistral (Ubuntu)
Importance: Undecided
Status: New
** Ch
** Changed in: manila (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: manila (Ubuntu Groovy)
Status: New => Triaged
** Also affects: masakari
Importance: Undecided
Status: New
** Also affects: masakari (Ubuntu)
Importance: Undecided
Status: New
** Chan
** Also affects: manila
Importance: Undecided
Status: New
** Also affects: manila (Ubuntu)
Importance: Undecided
Status: New
** Changed in: manila (Ubuntu Focal)
Importance: Undecided => High
** Changed in: manila (Ubuntu Focal)
Status: New => Triaged
--
You recei
** Also affects: magnum (Ubuntu)
Importance: Undecided
Status: New
** Changed in: magnum (Ubuntu Focal)
Importance: Undecided => High
** Changed in: magnum (Ubuntu Focal)
Status: New => Triaged
** Changed in: magnum (Ubuntu Groovy)
Importance: Undecided => High
** Changed
Public bug reported:
When run on the log output from Amazon Linux 2 (see bug 1876323),
`analyze` fails to find any log lines to process. Currently, it treats
this as a normal situation and emits:
$ cloud-init analyze show -i ~/Downloads/uhJNysgm.txt
-- Boot Record 01 --
The total time elapsed si
Public bug reported:
This is a more general version of bug 1876323: `cloud-init analyze`
relies on the log format that upstream ships in order to detect log
lines. This means that if logging configuration by users or downstream
packagers diverges (as is the case on Amazon Linux 2, for example), t
** Also affects: networking-hyperv (Ubuntu)
Importance: Undecided
Status: New
** Also affects: networking-l2gw
Importance: Undecided
Status: New
** Also affects: networking-l2gw (Ubuntu)
Importance: Undecided
Status: New
** Changed in: networking-l2gw (Ubuntu Focal)
** Also affects: networking-bagpipe
Importance: Undecided
Status: New
** Also affects: networking-bagpipe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: networking-bagpipe (Ubuntu Focal)
Importance: Undecided => High
** Changed in: networking-bagpipe (Ubuntu Foc
** Also affects: oslo.service
Importance: Undecided
Status: New
** Also affects: python-oslo.service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-oslo.service (Ubuntu Focal)
Importance: Undecided => High
** Changed in: python-oslo.service (Ubuntu Focal)
** Also affects: ironic-inspector (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ironic-inspector (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ironic-inspector (Ubuntu Focal)
Status: New => Triaged
** Changed in: ironic-inspector (Ubuntu Groovy)
I
** Also affects: ironic (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ironic (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ironic (Ubuntu Focal)
Status: New => Triaged
** Changed in: ironic (Ubuntu Groovy)
Importance: Undecided => High
** Changed
** Also affects: barbican (Ubuntu)
Importance: Undecided
Status: New
** Changed in: barbican (Ubuntu Focal)
Importance: Undecided => High
** Changed in: barbican (Ubuntu Focal)
Status: New => Triaged
** Changed in: barbican (Ubuntu Groovy)
Importance: Undecided => High
**
** Also affects: designate
Importance: Undecided
Status: New
** Also affects: designate (Ubuntu)
Importance: Undecided
Status: New
** Changed in: designate (Ubuntu Focal)
Importance: Undecided => High
** Changed in: designate (Ubuntu Focal)
Status: New => Triaged
*
Public bug reported:
Hi,
We have an openstack ansible rocky 18.1.2 setup. It was working working fine.
As part of an upgrade
we have reinstalled it. Now we are unable to create any vms. We have four
compute nodes.
When we try to create a vm on a specific compute node, it is failing, showing
no
Reviewed: https://review.opendev.org/724957
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=ed3bb4e1fb07c2817b4b7ad2e3e069f78bd839ba
Submitter: Zuul
Branch:master
commit ed3bb4e1fb07c2817b4b7ad2e3e069f78bd839ba
Author: Takashi Natsume
Date: Sat May 2 14:35:12 2020 +0
Public bug reported:
As a result of https://review.opendev.org/#/c/708985/, the sync util can
fail because it tries to look up the ovsdb connection from the
mechanism_manager under 'ovn' but the sync util registers under 'ovn-
sync'.
** Affects: neutron
Importance: Undecided
Assignee: T
This bug was fixed in the package cinder - 2:16.0.0~b3~git2020041012
.eb915e2db-0ubuntu2
---
cinder (2:16.0.0~b3~git2020041012.eb915e2db-0ubuntu2) groovy; urgency=medium
* d/p/monkey-patch-original-current-thread.patch: Cherry-picked from
https://review.opendev.org/724754. This
** Changed in: python-cinderclient
Status: Confirmed => 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.net/bugs/1744670
Title:
In pike ssl deployment hor
** Project changed: neutron => designate
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1876198
Title:
Setting unlimited qouta for zone
Status in Designate:
New
Bug description:
in
20 matches
Mail list logo
