** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu
Public bug reported:
Xenial Bionic and Cosmic are currently running earlier versions of
ubuntu-advantage-tools (10 for xenial and 17 for bionic/cosmic).
ubuntu-advantage-tools 19 and later is a completely rewritten CLI that
is backwards incompatible.
Until ubuntu-advantage-tools >= 19.1 is
Reviewed: https://review.opendev.org/656164
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0f471a47c073eb0cf2ed68c30482e1ae71ff6927
Submitter: Zuul
Branch:master
commit 0f471a47c073eb0cf2ed68c30482e1ae71ff6927
Author: LIU Yulong
Date: Fri Apr 26 15:42:32 2019
https://bugs.launchpad.net/manila-ui/+bug/1177924/comments/34
** Changed in: manila-ui
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
This bug is believed to be fixed in cloud-init in version 19.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
Reviewed: https://review.opendev.org/655929
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9bc45d70c6ba6e6ab02db30a843004cbb57ddc3f
Submitter: Zuul
Branch:master
commit 9bc45d70c6ba6e6ab02db30a843004cbb57ddc3f
Author: Rodolfo Alonso Hernandez
Date: Fri Apr 26
Public bug reported:
Cloud Provider: Amazon Web Services
As is documented in [1], instances on the nitro type hypervisor don't
attach the NVME disks in deterministic order, yielding a different order
of disks, example [2]. This makes it somewhat difficult to format and
partition volumes since
** Also affects: neutron (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Cosmic)
** Changed in: cloud-archive/stein
Status: New => Fix Released
** Description changed:
+ [Impact]
+ Currently if you deploy Openstack with dvr and l3ha enabled (and > 1 compute
host) only instances that are booted on the compute host that is running the VR
master will have access to
Public bug reported:
This involves the following items:
- Support for distributed ingress and egress for IPv6
- Support for running without network nodes. This implies
* Support for distributed DHCP
* Support for distributed SNAT
- Ensuring an OpenFlow-based DVR implementation is written in
Public bug reported:
[l3][scale issue] unrestricted hosting routers in network node increase
service operating pressure
Related problem was reported here:
https://bugs.launchpad.net/neutron/+bug/1828494
These issues have same background, unlimited router creation for entire cluster,
"""
Every
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1606741
Title:
[SRU] Metadata service for instances is
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/stein
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
** Also affects: cloud-archive/rocky
Importance:
This bug was fixed in the package neutron-fwaas-dashboard -
2.0.1-0ubuntu2
---
neutron-fwaas-dashboard (2.0.1-0ubuntu2) eoan; urgency=medium
* d/control: Add Breaks/Replaces to python3-neutron-fwaas-dashboard to
ensure python-neutron-fwaas-dashboard is removed on upgrade (LP:
Public bug reported:
While using the openstack cli and searching by name as any other
resource available, it sends as a query parameter the name of the
resource to search.
This value gets ignored in keystone resulting in the whole list of
endpoint groups returned.
On the openstack cli side, as
Public bug reported:
Rocky with Ryu, dont have a reproduce on this one or don't know what
caused it in the first place.
python-neutron-13.0.3-1.el7.noarch
openstack-neutron-openvswitch-13.0.3-1.el7.noarch
python2-neutron-dynamic-routing-13.0.1-1.el7.noarch
Public bug reported:
Routed provider networks is a feature which uses placement to store information
about segments, the subnets in segments and make possible that nova can use
this information in scheduling.
On master the placement API calls are failing, at first at get_inventory call:
May 09
Launchpad does not expire a bug if the bug is associated with multiple
projects, so (as horizon upstream) I am removing 'horizon' from the
affected projects. If this can be reproduced, please re-add 'horizon'.
** No longer affects: horizon
--
You received this bug notification because you are a
Public bug reported:
When the nova-manage db archive_deleted rows cron jobs from several
cells run in parallel (even if they are randomized during the day if
there are a lot of cells this may happen) they all try to destroy in
bulk the instance_mappings/instance_group_members/request_specs from
Public bug reported:
Description
===
When compute service is down, we choose to evacuate the instance of
corresponding node. If success, there will be two records in allocations table.
Normally, we try to restore the nova-compute service and one of the records
will be deleted when
Ok, thx Brian and Liu for comments on this. So based on Your comments it looks
that this isn't a bug in fact.
I'm then closing this bug as there is nothing to do with it :)
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of
48 matches
Mail list logo
