Public bug reported:
Description
===
evacuate an instance on non-shared storage succeeded and boot image is
rebuilt
Steps to reproduce
==
1. Create a two compute nodes cluster without shared storage
2. boot a image backed virtual machine
3. shutdown down the compute node
Public bug reported:
Hi everyone, we are creating an Octavia LB and using a tenant network as
LB network. The Virtual IP which allocated to the LB is not advertised
via BGP.
After some source code investigation we have seen that the port owner
must be "compute:nova" and port must be attached to a
Reviewed: https://review.opendev.org/c/openstack/neutron/+/880621
Committed:
https://opendev.org/openstack/neutron/commit/f23d7af8d7e36b9d52a8c8ccf64355e22f3adb9c
Submitter: "Zuul (22348)"
Branch:master
commit f23d7af8d7e36b9d52a8c8ccf64355e22f3adb9c
Author: Ihtisham ul Haq
Date: Mon Apr
Reviewed: https://review.opendev.org/c/openstack/neutron-lib/+/883345
Committed:
https://opendev.org/openstack/neutron-lib/commit/c5ca1ddf420b827e4684dee6a6495475014a91e3
Submitter: "Zuul (22348)"
Branch:master
commit c5ca1ddf420b827e4684dee6a6495475014a91e3
Author: Slawek Kaplonski
Date:
Reviewed: https://review.opendev.org/c/openstack/neutron/+/883239
Committed:
https://opendev.org/openstack/neutron/commit/a612346146db2f9e70a23af55eb7502655666940
Submitter: "Zuul (22348)"
Branch:master
commit a612346146db2f9e70a23af55eb7502655666940
Author: Alexander
Date: Mon May 15 19:
Hi there! Thanks for your report.
My initial thought on this is that maybe if you want to prevent a user
from modifying the security group of other user, using different
projects might be a good idea for that, since then the user will be
isolated on their project and not able to change the securit
Public bug reported:
This bug describes a race condition during deletion of a bare metal
(Ironic) instance when automated cleaning is enabled in Ironic (which is
the default).
# Steps to reproduce
As a race condition, this one is not easy to reproduce, although it has
been seen in the wild on se
Adding Nova because the report indicates that the volume is migrated to
a different ceph pool but the instance points to the old location.
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Status: Invalid => 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/1733861
Public bug reported:
The 'default' security group is applied to all VMs in a tenant. This
means that tampering with it from one user can prevent other users' VMs
from working (e.g. deleting the "ssh ingress" rule). While you can limit
actions on the whole security group matching the "name" field
(
Fixed in 9bd06d24a.
** Changed in: glance
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1885288
Title:
cinder glance_store docs out of date
Statu
This issue was fixed in the openstack/nova 25.2.0 release.
** Changed in: kolla-ansible/zed
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.launc
This issue was fixed in the openstack/glance_store 3.0.1 release.
** Changed in: nova/yoga
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.launch
This issue was fixed in the openstack/glance_store 4.3.1 release.
** Changed in: nova/antelope
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.laun
Reviewed:
https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/882815
Committed:
https://opendev.org/openstack/neutron-dynamic-routing/commit/bf54f03ce58aaac3bfc1f201c7d4af66f5e2cb11
Submitter: "Zuul (22348)"
Branch:master
commit bf54f03ce58aaac3bfc1f201c7d4af66f5e2cb11
Author:
** Also affects: nova
Importance: Undecided
Status: New
--
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/2019948
Title:
[alembic] Alembic operations require keyw
** Also affects: nova
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2019946
Title:
[S-RBAC] context.elevated() me
Public bug reported:
Since [1] (release 1.11.0), the Alembic operations "now enforce keyword-only
arguments as passed as keyword and not positionally" (from the commit message).
Detected in the "neutron-functional-with-sqlalchemy-master" CI job.
Errors:
https://storage.gra.cloud.ovh.net/v1/AUTH_
Public bug reported:
Currently context.elevated() method just ensures that "admin" role is set in
context.roles. But e.g. in case when noauth method pipeline is used in Neutron,
context from environ will not have any role set and it may fail if e.g. some
API policy is allowed for "role:reader"
19 matches
Mail list logo
