[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
** 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).
https://bugs.launchpad.net/bugs/1759120
Title:
Objects are not returned if domain name is use
** Changed in: glance
Status: Invalid => In Progress
** Changed in: glance
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1753964
Title:
Image rem
Public bug reported:
When you delete a shadow user and the user tries to log in again through
federation, they'll get a can't find user error. Retrying after 10 (or
so) minutes works.
My Setup
1. devstack-idp is the identity provider for service provider devstack-sp1,
using Keystone to
Reviewed: https://review.openstack.org/556889
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=9ca374091b795d77fe3fba45599e5ad13aed5c51
Submitter: Zuul
Branch:master
commit 9ca374091b795d77fe3fba45599e5ad13aed5c51
Author: Lance Bragstad
Date: Tue Mar 27 15:18:50 201
I've added upstream neutron to the bug. Keeping in mind this is mitaka
and unsupported by upstream, but perhaps someone from upstream knows
whether this is fixed in a mitaka+ release or not.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notificatio
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Medium
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova/queens
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova
Reviewed: https://review.openstack.org/497457
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8e6d5d404cf49e5b68b43c62e7f6d7db2771a1f4
Submitter: Zuul
Branch:master
commit 8e6d5d404cf49e5b68b43c62e7f6d7db2771a1f4
Author: Sahid Orentino Ferdjaoui
Date: Thu Aug 24 09:13:
Public bug reported:
release: Pike
When I try to spawn a 100 VMs at once almost every time it finishes with
a dozen VMs in ERROR state with cause:
Error: Build of instance 30ba80c7-6588-4916-80cb-ed3192b61e36 aborted:
Failed to allocate the network(s), not rescheduling
I debugged this a bit an
Reviewed: https://review.openstack.org/556739
Committed:
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=d9c52bcd54881d336cf1d5a74b4ed3697a1223fe
Submitter: Zuul
Branch:master
commit d9c52bcd54881d336cf1d5a74b4ed3697a1223fe
Author: Zhenmei
Date: Mon Mar 26 22:42:53 2018
10 matches
Mail list logo
