Public bug reported:
The newly added cache API ``PUT /v2/cache/{image_id}`` returns http 200
response to user whereas as per the original proposal [1] it should have
been http 202.
[1] https://opendev.org/openstack/glance-
Reviewed: https://review.opendev.org/c/openstack/glance/+/840215
Committed:
https://opendev.org/openstack/glance/commit/8271cde1e2850ff1870b310801e3fa8c7fbbf998
Submitter: "Zuul (22348)"
Branch:master
commit 8271cde1e2850ff1870b310801e3fa8c7fbbf998
Author: Brian Rosmaita
Date: Mon May 2
** Changed in: python-designateclient
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1259292
Title:
Some tests use
Public bug reported:
The ML2/OVN driver does not yet officially support provisioning
baremetal nodes. This bug is a tracker for that work.
I believe the work can be broken up in two parts:
Part 1: Add support for provisioning baremetal nodes with ML2/OVN +
Neutron DHCP agent. Since the OVN
Public bug reported:
Description
===
The server will fail to hard reboot after an retype operation
is performed on the multi-attach volume of it.
With multiattach the nova will call to volume api to get volume
according to connection_info in block device mappings of nova.
However, the
Public bug reported:
Description
===
There will be redundant bdms in nova after a volume
fails to be detached from the server, ie, the libvirt
has succeeded in detaching the disk and attachment
in cinder has disappeared, but bdm in nova is present.
In such scenario, nova compute service
Public bug reported:
Description
===
We observe some nova-conductor behavior during its startup, and think
that might be not that correct, would like to see if any improvement can
be made for this.
Steps to reproduce
==
- We have a large cellv2 setup, the nova services
7 matches
Mail list logo
