[Expired for Keystone because there has been no activity for 60 days.]
** Changed in: keystone
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1179765
"Seems that its not possible to avoid being admin when getting an
instances network info from Neutron" from
https://review.openstack.org/#/c/56231/ - hence marking this defect as
invalid
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you a
Reverting the above patch as it caused subsequent issues when combined
with patchset 16 of https://review.openstack.org/#/c/50491/
After discussing the issue further, this bug report & patch doesn't
address the underlying issue which is that we're raising 400's based on
typeerrors in the first pla
Appears to have been a problem with our configuration. Will re-open if
the problem arises again.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.la
** Changed in: nova/grizzly
Status: In Progress => Won't Fix
** Changed in: nova/grizzly
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.n
** Changed in: horizon
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1256056
Title:
In Project Overview the Limit Summary for
One of these came from logs.openstack.org/94/58494/3/check/check-
tempest-devstack-vm-full/2ef9650/logs/screen-n-cpu.txt.gz
But this was probably from a "check" run on a proposed commit. I have
been scanning all builds to finalize the whitelist for log errors.
Closing this ticket for now.
** Chan
Not released in a milestone yet
** Changed in: nova
Status: Fix Released => Fix Committed
--
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/1078055
Title:
Some id a
This is not a bug of Neutron, vmware will use "DEFAULT.neutron_ovs_bridge"
value in nova.conf as vm bridge if using OpenStack Networking Service and ovs
l2 agent started.
so set this bug as invalid.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notificat
As far as I can see here, this is not a horizon bug. Nova novnc is part
of nova.
** Changed in: horizon
Status: Triaged => Invalid
** Changed in: horizon
Milestone: icehouse-2 => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
10 matches
Mail list logo