** Changed in: neutron
Assignee: (unassigned) => LIU Yulong (dragon889)
** Changed in: neutron
Status: Opinion => 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/1830014
Reviewed: https://review.opendev.org/668675
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=40f1e7c4c22dc6023614b34f28bb7fc416b668a8
Submitter: Zuul
Branch:master
commit 40f1e7c4c22dc6023614b34f28bb7fc416b668a8
Author: Balazs Gibizer
Date: Tue Jul 2 14:56:40 2019
** Changed in: nova
Status: In Progress => 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/1522233
Title:
Failed to migrate encrypted volume
Status
** Also affects: os-brick
Importance: Undecided
Status: New
** No longer affects: os-brick
** Project changed: nova => os-brick
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
for non-physical interfaces, common attributes like mtu were not copied
into the internal state when merging v2 config.
** Changed in: curtin
Status: New => Invalid
** Changed in: cloud-init
Status: New => Confirmed
--
You received this bug notification because you are a member
This bug was fixed in the package nova - 2:18.2.0-0ubuntu2
---
nova (2:18.2.0-0ubuntu2) cosmic; urgency=medium
* Cherry-picked from upstream to ensure no stale
allocations are left over on failed cold
migrations (LP: #1821594).
- d/p/bug_1821594_1.patch: Fix migration
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1835008
Title:
** Changed in: cloud-archive/queens
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/1771506
Title:
Unit test failure with
Reviewed: https://review.opendev.org/668378
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=dfa37b2233b2dbe6dd12ec5e2ee4f1f32a4be4ba
Submitter: Zuul
Branch:master
commit dfa37b2233b2dbe6dd12ec5e2ee4f1f32a4be4ba
Author: Slawek Kaplonski
Date: Mon Jul 1 09:45:38 2019
Public bug reported:
The notification sample test for unshelve waits for the instance to
reach ACTIVE state and then asserts if unshelve.end notification is
emitted properly. However the instance.vm_state is set to ACTIVE
earlier[1] than emitting the unshelve.end notification[2]. This can
cause
I've added snapd so they can look into what's going on with
snapd.seeded.service.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: Incomplete => Invalid
** Summary changed:
- Modules steps not taken into account since 19.1
+
** Changed in: cloud-init
Status: Expired => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1820360
Title:
seed location requires trailing slash
Status in cloud-init:
Public bug reported:
- [x] This doc is inaccurate in this way:
https://developer.openstack.org/api-ref/compute/#servers-actions-
servers-os-instance-actions
The user_id and project_id parameter descriptions for server actions
imply that they are the value of the user/project that owns the
Ups we have to set the microversion into the header. Shame on us. This
bug can be closed :)
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Description of problem:
Memory leak in privsep-helper(neutron agents) when create/destroy action are
executed.
Version-Release number of selected component (if applicable):
How reproducible:
Rocky and Queens are affected
Steps to Reproduce:
1. Deploy Osp 14
2.create the
Public bug reported:
Hey there,
as written in the docs[1] the field block_device_mapping_v2.volume_type
should be supported in microversions later than 2.67. However we have
microversion 2.72 but if we want to use the field we get an error, of
unsupported field:
Request
~~~
POST
** Description changed:
The MTU is not set on the bond, nor vlans on the bond, nor the bridges
attached to the vlans on a network_v2 configuration. It's only set on
the underlying interfaces (eth0, eth1)
This does not happen if given a network_v1 configuration.
+
+ (I'm deploying
Public bug reported:
The MTU is not set on the bond, nor vlans on the bond, nor the bridges
attached to the vlans on a network_v2 configuration. It's only set on
the underlying interfaces (eth0, eth1)
This does not happen if given a network_v1 configuration.
(I'm deploying ubuntu xenial via
18 matches
Mail list logo
