included to
the list, since they use the same libvirt driver for KVM based systems.
** Affects: nova
Importance: Undecided
Assignee: Sudipta Biswas (sbiswas7)
Status: New
** Changed in: nova
Assignee: (unassigned) => Sudipta Biswas (sbiswas7)
--
You received this
to use the monitor metric object
instead of the current non object implementation.
** Affects: nova
Importance: Undecided
Assignee: Sudipta Biswas (sbiswas7)
Status: New
** Tags: low-hanging-fruit
** Changed in: nova
Assignee: (unassigned) = Sudipta Biswas (sbiswas7
** Changed in: glance
Assignee: Sudipta Biswas (sbiswas7) = (unassigned)
** Changed in: glance
Status: In Progress = Incomplete
** Changed in: glance
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Assignee: Sudipta Biswas (sbiswas7)
Status: New
** Tags: network
** Changed in: nova
Assignee: (unassigned) = Sudipta Biswas (sbiswas7)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https
Public bug reported:
Using Kilo.
When I edit the Allocation pool for a given subnet by Editing the subnet.
The Save operation succeeds but the Allocation Pool values aren't updated
and the older values are still displayed (used).
Tried this from the neutron cli and the neutron subnet-update
I can confirm the bug - and it gets reproduced easily with the steps mentioned.
However, the problem seems to be in the horizon code and doesn't seem to be in
neutron. Also all the logs you have pasted, doesn't seem to be relevant.
In the dashboard/api/lbass.py file:
def _vip_get(request,
It appears that nova relies completely on glance for the error code and
hence the fix at one point in glance is enough to fix this bug. Marking
this nova side of the fix as 'Invalid' post chatting with Nikhil on IRC.
** Changed in: nova
Status: Confirmed = Invalid
--
You received this
information should include the supported version number as well.
This would atleast give an idea to the user on the supported level on the
controller/conductor APIs.
** Affects: nova
Importance: Undecided
Assignee: Sudipta Biswas (sbiswas7)
Status: New
** Changed in: nova
I think I have covered the reason for marking this invalid in my
previous comments.
** Changed in: nova
Status: Incomplete = Invalid
** Changed in: nova
Assignee: Sudipta Biswas (sbiswas7) = (unassigned)
--
You received this bug notification because you are a member of Yahoo
:
if quotas.get('port', -1) = -1:
# Unlimited Port Quota
return num_instances
This will allow nova to react correctly with the documentation in
neutron as well.
** Affects: nova
Importance: Undecided
Assignee: Sudipta Biswas (sbiswas7)
Status: New
*** This bug is a duplicate of bug 1327124 ***
https://bugs.launchpad.net/bugs/1327124
This has been fixed in Kilo as a part of this bug: 1327124
https://review.openstack.org/#/c/98340/ -- The fix in this review should
have addressed this.
Marking this as a dup.
** This bug has been marked
*** This bug is a duplicate of bug 1247844 ***
https://bugs.launchpad.net/bugs/1247844
** This bug has been marked a duplicate of bug 1247844
PortLimit thrown when specifying used fixed ip
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
back an exception to the
agent - saying the reporting state failed with the appropriate message.
This can be achieved by bubbling an exception from the report_state
method on a timestamp miss match to the OVS agent.
** Affects: neutron
Importance: Undecided
Assignee: Sudipta Biswas
: neutron
Importance: Undecided
Assignee: Sudipta Biswas (sbiswas7)
Status: New
** Changed in: neutron
Assignee: (unassigned) = Sudipta Biswas (sbiswas7)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron
Public bug reported:
Deploys fail with Network uuid requires a subnet in order to boot
instances on. when done with networks which don't have an associated
subnet.
It seems that this error was introduced after the following code was
integrated:
Public bug reported:
Recently a change in the nova/network/neutronv2/api.py file is causing
nova boots to fail for networks that do not have a subnet associated
with them.
The following line in the api.py file is causing the issue:
for net in nets:
if not
** Also affects: nova
Importance: Undecided
Status: New
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1304409
Title:
VMs can't be booted with
Public bug reported:
When a user runs an action against an object in neutron for which they
don't have authority to (perhaps their role allows read of the object,
but not update), they get the message The resource could not be found.
For example: User doesn't have the privilege to edit a network
18 matches
Mail list logo
