Public bug reported:
How to reproduce:
1) Set new_facade = True in any OVO object. I tried PortBinding(), Port() and
Network().
2) Run python -m testtools.run neutron/tests/unit/objects/test_network.py
or python -m testtools.run neutron/tests/unit/objects/test_port.py
3) Example of failures:
=
Public bug reported:
400 is missing in "Create resource provider" API
https://developer.openstack.org/api-ref/placement/#create-resource-provider
https://github.com/openstack/nova/blob/c9087bd6c5ed0ec0e7c8fcd8f48c1fcb9f3d6a4a/nova/api/openstack/placement/handlers/resource_provider.py#L101
400 is
Reviewed: https://review.openstack.org/340614
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=b3f39244a3eacd6fb141de61850cbd84fecdb544
Submitter: Zuul
Branch:master
commit b3f39244a3eacd6fb141de61850cbd84fecdb544
Author: ankitagrawal
Date: Wed Sep 23 03:58:19 2015 -070
Reviewed: https://review.openstack.org/545211
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=28fb47092f3751de11cc8e61f06e451a2fa268f2
Submitter: Zuul
Branch:master
commit 28fb47092f3751de11cc8e61f06e451a2fa268f2
Author: Abhishek Kekane
Date: Tue Feb 20 16:04:23 2018
Public bug reported:
Description
===
As described in [1], Hyper-V driver supports NUMA placement policies.
But it doesn't support cpu pinning policy[2].
So the host should be excluded in NUMATopologyFilter if the end user try to
build a VM with cpu pinning policy.
[1]
https://docs.open
*** This bug is a duplicate of bug 1749640 ***
https://bugs.launchpad.net/bugs/1749640
** This bug is no longer a duplicate of bug 1749641
Overcloud deployment failing in promotion jobs at glance-manage db_sync
** This bug has been marked a duplicate of bug 1749640
db sync fails for mysq
Public bug reported:
Description
===
If libvirt is unable to detach a volume because it's still in-use by the guest
(either mounted and/or file opened), nova returns a traceback.
Steps to reproduce
==
* Create an instance with volume attached using heat
* Make sure there
Public bug reported:
Keystone implemented scope_types for oslo.policy RuleDefault objects in
the Queens release. In order to take full advantage of scope_types,
keystone is going to have to evolve policy enforcement checks in the
user API. This is documented in each patch with FIXMEs [0].
The fol
Public bug reported:
Keystone implemented scope_types for oslo.policy RuleDefault objects in
the Queens release. In order to take full advantage of scope_types,
keystone is going to have to evolve policy enforcement checks in the
user API. This is documented in each patch with FIXMEs [0].
The fol
Public bug reported:
Keystone implemented scope_types for oslo.policy RuleDefault objects in
the Queens release. In order to take full advantage of scope_types,
keystone is going to have to evolve policy enforcement checks in the
user API. This is documented in each patch with FIXMEs [0].
The fol
Public bug reported:
Keystone implemented scope_types for oslo.policy RuleDefault objects in
the Queens release. In order to take full advantage of scope_types,
keystone is going to have to evolve policy enforcement checks in the
user API. This is documented in each patch with FIXMEs [0].
The fol
Public bug reported:
When generating the sphinx doc in Debian Sid with Python 3.6 for the
Queens RC1 release of Nova, I get the below stack dump, though it passes
under Python 2.7. A fix would be more than welcome, cause I'm removing
all traces of Python 2.7, including sphinx stuff and all modules
Public bug reported:
If you try to boot and instance and delete it early before scheduling,
the '_delete_while_booting' codepath hits
`_attempt_delete_of_buildrequest` which tries to remove the block device
mappings.
However, if the cloud contains compute nodes before Pike, no block
device mappin
Public bug reported:
Keystone implemented scope_types for oslo.policy RuleDefault objects in
the Queens release. In order to take full advantage of scope_types,
keystone is going to have to evolve policy enforcement checks in the
user API. This is documented in each patch with FIXMEs [0].
The fol
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => melanie witt (melwitt)
** Changed in: nova/pike
Status: New => In Progress
** Cha
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: Ne
Reviewed: https://review.openstack.org/546108
Committed:
https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=d3352ff422db6ba6a5e7bd4f7220af0d97efd0ac
Submitter: Zuul
Branch:master
commit d3352ff422db6ba6a5e7bd4f7220af0d97efd0ac
Author: Chris Dent
Date: Tue Feb 20 10:31:
Reviewed: https://review.openstack.org/541055
Committed:
https://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/commit/?id=91d182f2d3fc300a55f4821d2091bc36701ff5d7
Submitter: Zuul
Branch:master
commit 91d182f2d3fc300a55f4821d2091bc36701ff5d7
Author: Akihiro Motoki
Date: Tue Feb
Public bug reported:
When doing a rebuild-to-same-host but with a different image, all we
really want to do is ensure that the image properties for the new image
are still valid for the current host. Accordingly we need to go through
the scheduler (to run the image-related filters) but we don't w
This is a regression introduced with change
I11746d1ea996a0f18b7c54b4c9c21df58cc4714b which was backported all the
way to stable/newton upstream:
https://review.openstack.org/#/q/I11746d1ea996a0f18b7c54b4c9c21df58cc4714b
** Changed in: nova
Importance: Undecided => High
** Changed in: nova
Reviewed: https://review.openstack.org/546069
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=465ad6f3197b8591a401a9f0db2fabf6c70fdfce
Submitter: Zuul
Branch:master
commit 465ad6f3197b8591a401a9f0db2fabf6c70fdfce
Author: Sławek Kapłoński
Date: Tue Feb 20 09:24:38 20
Public bug reported:
As of stable/pike if we do a rebuild-to-same-node with a new image, it
results in ComputeManager.rebuild_instance() being called with
"scheduled_node=" and "recreate=False". This results in a new
Claim, which seems wrong since we're not changing the flavor and that
claim coul
Reviewed: https://review.openstack.org/545820
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=92959238a3e408e810ccd4f3d3d453a35afb5bba
Submitter: Zuul
Branch:master
commit 92959238a3e408e810ccd4f3d3d453a35afb5bba
Author: Sławek Kapłoński
Date: Mon Feb 19 13:28:57 20
Public bug reported:
Keystone implemented scope_types for oslo.policy RuleDefault objects in
the Queens release. In order to take full advantage of scope_types,
keystone is going to have to evolve policy enforcement checks in the
user API. This is documented in each patch with FIXMEs [1].
The fol
** Changed in: neutron
Status: Confirmed => Fix Released
** Changed in: neutron
Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpa
As it was stated above by the Ironic team, they provided a new feature
for deterministicly provide the network ports.
Setting accordingly that bug report as Wontfix.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engi
** Changed in: neutron
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1730845
Title:
[RFE] support a port-behind-port API
Status in neutron:
Incom
Honestly, I wonder if LVM sparse LVs worked. Looks like we don't have
any functiona tests for that (just the unittests) and we merged the
blueprint by 5 years ago.
If you also see that comment in
https://github.com/openstack/nova/blob/c1eb6f0/nova/virt/libvirt/imagebackend.py#L688-L689
looks like
This is also a problem in python-cinderclient which logs the response
body:
https://github.com/openstack/python-
cinderclient/blob/84346b5dba784bfeb3a53ae83d400ba264263cf6/cinderclient/apiclient/client.py#L141
** Also affects: python-cinderclient
Importance: Undecided
Status: New
** Ch
Actually cinderclient should be fixed:
https://review.openstack.org/#/c/395119/
** No longer affects: python-cinderclient
--
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/1
Public bug reported:
putting space before
verbose = true
will make
systemctl status neutron-dhcp-agent.service
to fail.
Removing space will fix it, but this should NOT happen is this is plain
text file (not Yaml or similar) and thus shouldn't make difference if
there is space or not.
Ce
Public bug reported:
This is mainly following https://docs.openstack.org/neutron/pike/admin
/config-qos.html, steps to reproduce:
1. Admin creates qos policy "default" in admin project
2. User creates network "mynet" in user project
3. Admin applies qos policy to tenant network via "openstack net
Public bug reported:
According to https://docs.openstack.org/neutron-dynamic-
routing/latest/contributor/testing.html no automatic scheduling of BGP
speakers to dynamic routing agents is happening. However at least of
Pike this is no longer true: The first speaker that is being created is
automati
Public bug reported:
Hello everyone,
Seems I caught a race condition bug in neutron-l3-agent.
We have automated tests. One of the test performs the following scenario.
Creates different resources such as network, subnet and so on. Then the test
connects the subnet to a router and perform other
Public bug reported:
Since db_sync is now internally using EMC pattern we need to revisit the
entire database rolling upgrades documentation.
** Affects: glance
Importance: High
Assignee: Abhishek Kekane (abhishek-kekane)
Status: New
** Changed in: glance
Assignee: (unass
Reviewed: https://review.openstack.org/542858
Committed:
https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=fb27465c6fb734d7106130765f918ed91bc329ad
Submitter: Zuul
Branch:master
commit fb27465c6fb734d7106130765f918ed91bc329ad
Author: Brent Eagles
Date: Fri Feb 9 1
Reviewed: https://review.openstack.org/541250
Committed:
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=03b6cc81876df2423c17532b8f2e0ef2bbb6a84b
Submitter: Zuul
Branch:master
commit 03b6cc81876df2423c17532b8f2e0ef2bbb6a84b
Author: Hunt Xu
Date: Tue Feb 6 18:21:21 2018
Public bug reported:
The neutron-specs docs is currently failing in master, preventing to
merge anything (and get nice HTML previews in gerrit changes for new
specs):
2018-02-19 13:31:49.216472 | ubuntu-xenial | Warning, treated as error:
2018-02-19 13:31:49.216571 | ubuntu-xenial |
/home/zuul/s
38 matches
Mail list logo
