[Expired for cloud-init because there has been no activity for 60 days.]
** Changed in: cloud-init
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
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:
- [ ] This doc is inaccurate in this way: __
- [ ] This is a doc addition request.
- [ ] I have a fix to
Since this report concerns a possible security risk, an incomplete
security advisory task has been added while the core security reviewers
for the affected project or projects confirm the bug and discuss the
scope of any vulnerability along with potential solutions.
** Also affects: ossa
Reviewed: https://review.opendev.org/673023
Committed:
https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=fa5ebc4b98e4964b73210e38772af50e2524be3b
Submitter: Zuul
Branch:master
commit fa5ebc4b98e4964b73210e38772af50e2524be3b
Author: Rodolfo Alonso Hernandez
Date:
*** This bug is a security vulnerability ***
Public security bug reported:
Background of the Issue
===
Customers expect that when they set Neutron security group rules such that all
traffic is blocked that all traffic is in fact blocked by the Neutron firewall
driver.
Reviewed: https://review.opendev.org/637305
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=bf67b3c88409d2f0b2086d363ed91394953d85ba
Submitter: Zuul
Branch:master
commit bf67b3c88409d2f0b2086d363ed91394953d85ba
Author: erus
Date: Tue Feb 19 17:32:07 2019 -0300
Since this is for new users only, the admin will need to provide the
user with enough information to be able to change their password before
first login, like some kind of onboarding packet. This would have to
include their user ID. There's no way that keystone could supply the
user's ID without
Marking wontfix based on above comment, feel free to reopen if you want
to discuss it further.
** Changed in: keystone
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 isn't really a good idea. The way keystone's internal notification
framework is implemented, errors in that framework can leave the DB in
inconsistent states. If this were to be implemented any implementations
that are 3rd party could not reasonably be supported by the Keystone
team
Public bug reported:
As of the reporting of this bug, router migrations are the largest
contributor of failures of the neutron-tempest-plugin-dvr-multinode-
scenario job. Over a 7 days period these are the failures observed:
test_qos_basic_and_update 48
test_from_dvr_to_dvr_ha 39
Public bug reported:
When dashboard has a custom theme it is shown on the drop down menu as
"custom".
Is it possible to change the name of the theme from "custom" or can this
feature be added?
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug
Actually ignore comment 15, claim_resources didn't raise
AllocationUpdateFailed until Stein:
https://github.com/openstack/nova/commit/37301f2f278a3702369eec957402e36d53068973
So the bug doesn't apply to Rocky or Queens.
** No longer affects: nova/rocky
** No longer affects: nova/queens
--
Public bug reported:
ENV: stable/queens
But master has basically same code, so the issue may also exist.
Config: L2 ovs-agent with enabled openflow based security group.
Recently I run one extreme test locally, booting 2700 instances for one single
tenant.
The instance will be booted in 2000
I'll be backporting the non-fill provider mapping part of this to rocky
and queens since the code fix and functional tests related to bug
1837955 rely on changes from the series that fixed this bug.
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects:
What version of os-brick are you using? There might be fixes in newer
releases of os-brick but you'd have to check the change log probably.
Lee Yarwood might be familiar with any related changes to os-brick as
well.
** Tags added: libvirt live-migration volumes
** Also affects: os-brick
Reviewed: https://review.opendev.org/669190
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6be668e51992df53a4d871bea70bc738a9beacb8
Submitter: Zuul
Branch:master
commit 6be668e51992df53a4d871bea70bc738a9beacb8
Author: John Garbutt
Date: Thu Jul 4 15:06:17 2019 +0100
Public bug reported:
Dear all,
we are using `oslo_messaging_notifications` configured in Neutron server [1] to
receive updates about floating ip (FIP) associations and disassociations to
process
them with an in-house tool. This works well in almost all cases, except one.
The cases that are
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:
- [ ] This doc is inaccurate in this way: __
- [ ] This is a doc addition request.
- [ ] I have a fix to
Public bug reported:
Description
===
Simultaneous requests to reboot and delete an instance _will_ race as only the
call to delete takes a lock against the instance.uuid.
One possible outcome of this seen in the wild with the Libvirt driver is
that the request to soft reboot will
Public bug reported:
Description
===
When I live-migrate a VM boot from volume on 3par storage (we're using
multipath for redundancy), it failed because of nova-compute calling os-
brick to flush wrong device mapper, that device mapper is belong to the
volume of another VM that lie on
Public bug reported:
Description
===
I created one instance boot from volume.
After deleting the instance when it's building,
the volume's status was reserved.
Steps to reproduce
==
* I created one instance with `openstack server create --volume vol-for-vm1-50G
--flavor
21 matches
Mail list logo
