Multi-attach functionality is now implemented in both Cinder and Nova,
which should make this bug invalid. In case the symptom appears again
the bug shall be re-opened.
Blueprint page with more details:
https://blueprints.launchpad.net/nova/+spec/multi-attach-volume
** Changed in: nova
Public bug reported:
The scheduler will request an infinitely-large host set from placement
during scheduling operations. This may be very large on big clouds and
makes for a huge JSON response from placement to scheduler each time a
single host needs to be selected.
** Affects: nova
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.
- [X] I have a fix to
I agree with Sean. It is worth tackled as a cross project topic.
As an individual project, neutron triages this in the same way as nova
does.
** Changed in: neutron
Status: New => Opinion
** Changed in: neutron
Importance: Undecided => Wishlist
--
You received this bug notification
Public bug reported:
SchedulerReportClient._delete_inventory uses the DELETE
/resource_providers/{u}/inventories API, which does not provide a way to
send the generation down (see related bug [1]), and is therefore subject
to concurrency errors.
Until/unless an alternative becomes available, we
Public bug reported:
Placement has a few APIs which affect resource provider generation, but
which do not accept the current resource provider generation and
therefore cannot ensure consistency. They are as follows:
DELETE /resource_providers/{u}/inventories
DELETE
Reviewed: https://review.openstack.org/535700
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=11222bbf777a9418b9262bf56a61e5f3aa5f6501
Submitter: Zuul
Branch:master
commit 11222bbf777a9418b9262bf56a61e5f3aa5f6501
Author: deepak_mourya
Public bug reported:
Introduced here:
https://review.openstack.org/#/c/535642/4/nova/tests/functional/api/openstack/placement/gabbits
/allocation-candidates.yaml
Seen failing here later in the series:
http://logs.openstack.org/10/539310/1/check/nova-tox-functional/a6ba562
Nevermind the issue is here:
https://review.openstack.org/#/c/537351/3/nova/api/openstack/placement/util.py
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
** Also affects: manila
Importance: Undecided
Status: New
** Changed in: manila
Assignee: (unassigned) => zhongjun (jun-zhongjun)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Reviewed: https://review.openstack.org/536182
Committed:
https://git.openstack.org/cgit/openstack/cinder/commit/?id=d24963f7e84b519864ece4fce99f9b0da0204da4
Submitter: Zuul
Branch:master
commit d24963f7e84b519864ece4fce99f9b0da0204da4
Author: junboli
Date: Mon Jan
Public bug reported:
In bug/1744965(https://bugs.launchpad.net/nova/+bug/1744965), it is
reported that the way emulator_threads_policy allocates the extra cpu
resource for emulator is not optimal.
This report reports the bug also stays when `cpu_thread_policy=isolate`.
The instance I use for
You need to verify that the credentials you are using do in fact have
the correct permissions to create an image. There may be a --debug
option to the openstack client you can use to find out where the 401 is
occurring and what credentials are being used for the call to the Images
API. Check the
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1730637
[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 neutron.
>From Scott's comments and John's comments in the linked bug, this does
not seem to be a Juju but cloud-init issue only.
** Changed in: juju
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
If we create new port(binded somewhere) with following condition, an
Error occurred.
Jan 31 11:30:00 furukawa-verify-devstack neutron-server[25204]: DEBUG
neutron_fwaas.db.firewall.v2.firewall_db_v2 [None
req-f3c0994c-1547-410a-8bf8-b4b459e0dfba None None]
Looks like there's nothing for Glance to do on this. Thanks for doing
the research to track down the fix, Abhishek.
** Changed in: glance
Status: New => Triaged
** Changed in: glance
Importance: Undecided => Medium
** Changed in: glance
Status: Triaged => Fix Released
**
Reviewed: https://review.openstack.org/538676
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=49fd528b7b814e8e8dab1fb238a79924fbf059b7
Submitter: Zuul
Branch:master
commit 49fd528b7b814e8e8dab1fb238a79924fbf059b7
Author: Akihiro Motoki
Date: Mon
Public bug reported:
Documentation is missing about network_data.json.
The only available documentation is from the original spec which is a
bit out of sync with the implementation:
http://specs.openstack.org/openstack/nova-
specs/specs/liberty/implemented/metadata-service-network-info.html
For
Reviewed: https://review.openstack.org/538585
Committed:
https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=adefc64f21d8329ae5729d4a450b165728d29a8b
Submitter: Zuul
Branch:master
commit adefc64f21d8329ae5729d4a450b165728d29a8b
Author: Sławek Kapłoński
Reviewed: https://review.openstack.org/538961
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=4a2c9a4887a219a6d4dfe83c430b040713fc4109
Submitter: Zuul
Branch:master
commit 4a2c9a4887a219a6d4dfe83c430b040713fc4109
Author: Matt Riedemann
Date: Mon
** Changed in: sahara
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.launchpad.net/bugs/1266962
Title:
Remove set_time_override in timeutils
Status in Ceilometer:
Reviewed: https://review.openstack.org/537933
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6553a632399d77bb7c31690dd8284992eb6afb92
Submitter: Zuul
Branch:master
commit 6553a632399d77bb7c31690dd8284992eb6afb92
Author: Balazs Gibizer
Date:
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => In Progress
** Changed in: nova/pike
Importance: Undecided => High
** Changed in: nova/pike
Public bug reported:
When deploying LXD containers using Juju and MAAS, the LXD containers
launch with no network connectivity because cloud-init fails with the
following stack trace:
Cloud-init v. 17.1 running 'init-local' at Tue, 30 Jan 2018 22:12:46 +. Up
1.00 seconds.
2018-01-30
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => In Progress
** Changed in: nova/ocata
Assignee: (unassigned) => Danil Akhmetov (dinobot)
** Changed in: nova/ocata
Assignee: Danil Akhmetov (dinobot) => György
Reviewed: https://review.openstack.org/530662
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=65736fd7d49284efd6c28be21aceb0ba1ea0ec4a
Submitter: Zuul
Branch:master
commit 65736fd7d49284efd6c28be21aceb0ba1ea0ec4a
Author: Andreas Karis
Date: Mon Jan
Reviewed: https://review.openstack.org/536293
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=312327b75989fe0aad209c56671c583e33709303
Submitter: Zuul
Branch:master
commit 312327b75989fe0aad209c56671c583e33709303
Author: Takashi NATSUME
Public bug reported:
Per the discussion in [1], the ironic nodes added to the node cache in
the ironic virt driver may be missing the required field resource_class,
as this field is not in _NODE_FIELDS. In practice, this is typically not
an issue (possibly never), as the normal code path uses a
You have been subscribed to a public bug:
Invalid query parameter could lead to HTTP 500, although Nova used JSON Schema
verification
to check input query params, but query like:
GET /servers?limit=%88 will still lead to HTTP 500, as it failed to parse at
webob which is
pre JSON Schema check.
Public bug reported:
Invalid query parameter could lead to HTTP 500, although Nova used JSON Schema
verification
to check input query params, but query like:
GET /servers?limit=%88 will still lead to HTTP 500, as it failed to parse at
webob which is
pre JSON Schema check.
GET
** Also affects: cinder
Importance: Undecided
Status: New
--
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/1746202
Title:
Invalid query parameter could lead to
Public bug reported:
Hello,
I am using the Pike OpenStack version for ubuntu server 16.04. And the
following guide to carry out the installation.
https://docs.openstack.org/pike/install/
I have recently installed and updated OpenStack and precisely if I have
seen that they have changed the
Public bug reported:
The neutron service support the pagination for networks and routers.
But the horizon does not support it.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Hi,
Description / Steps to reproduce
When instances are launched, they get the following console/serial
configuration :
\n
If I look at the permissions for the console.log I see :
[root@
Public bug reported:
`enabled_vgpu_types` flag has been set in nova.conf to set enabled vgpu type of
current host. The example is wrong, it should be
[devices]
enabled_vgpu_types = ['GRID K100', 'Intel GVT-g', 'MxGPU.2', 'nvidia-11']
Check nova/conf/devices.py to see the example.
**
37 matches
Mail list logo