Given we are after RC1 (which means that we only accept regression
bugfixes for RC2 and later versions), I think we should just document
the current caveat in https://docs.openstack.org/api-guide/compute
/accelerator-support.html and trying to backport the bugfix for a later
Ussuri release (say 21.
** Changed in: neutron
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1844607
Title:
log error when create neutron port with wrong subnet
Stat
Fix is already merged
** Changed in: neutron
Assignee: Reedip (reedip-banerjee) => (unassigned)
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https
Public bug reported:
Description
===
the vms can not be force deleted when vm_status is soft-delete and
task-state=deleting
Steps to reproduce
==
1.soft delete the vms
2.force delete the vms which status is soft-delete.
3.down the nova-compute while deleting the vms.
4.re
Public bug reported:
See https://bugs.launchpad.net/glance/+bug/1875439 for background.
** Affects: glance
Importance: Medium
Status: Triaged
** Tags: documentation security
** Changed in: glance
Importance: Undecided => Medium
--
You received this bug notification because y
Public bug reported:
A value for the 'checksum' image property will no longer be computed
from Victoria onwards. The field itself will remain (so no change in
the API response).
Current text is:
Hash that is used over the image data. The Image service uses this value
for verification. The value
In Stein, we merged the ability to have multiple Resource Providers, each of
them being a pGPU.
In Ussuri, we accepted to have a specific vGPU type per pGPU.
Now, I tested the above behaviour with https://review.opendev.org/723858
and it works now, unless you ask for a specific total capacity.
I
That is correct what you wrote above. But tricky part here is generated
policy.json from 'oslopolicy-sample-generator' tool without deprecated
rules is right thing or wrong. Because it can be seen as one of the
valid usgae for deployer who want to switch to new defaults. The only
way for them till
** Also affects: ossn
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1875630
Title:
issue OSSN when glance no longer requires an md5 implementa
Public bug reported:
This bug tracker is for errors with the documentation, use the following as a
template and remove or add fields as you see fit. Convert [ ] into [x] to check
boxes:
- [x] This doc is inaccurate in this way:
At "4. Confirm upload of the image and validate attributes:", th
10 matches
Mail list logo
