[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).
[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).
Reviewed: https://review.openstack.org/566947
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=d501960d7e8474927ebd6d6abc52350a0f23275a
Submitter: Zuul
Branch:master
commit d501960d7e8474927ebd6d6abc52350a0f23275a
Author: Brian Rosmaita
Date: Tue May 8 12:54:24 2018
Reviewed: https://review.openstack.org/574229
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=0796adbd87a026f917beee8002b1ca82f48ab3cb
Submitter: Zuul
Branch:master
commit 0796adbd87a026f917beee8002b1ca82f48ab3cb
Author: tstappae
Date: Mon Jun 11 13:32:42 2018
Reviewed: https://review.openstack.org/576136
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=db8da4942f1bf6c506701be5a98e55cd11d11052
Submitter: Zuul
Branch:master
commit db8da4942f1bf6c506701be5a98e55cd11d11052
Author: Matt Riedemann
Date: Mon Jun 18 13:23:14 2018
Reviewed: https://review.openstack.org/559552
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=b385864c5d8c85c8911483b76c7787b33ebd84a3
Submitter: Zuul
Branch:master
commit b385864c5d8c85c8911483b76c7787b33ebd84a3
Author: wangxiyuan
Date: Sun Apr 8 14:57:18 2018
Public bug reported:
In the page of
https://docs.openstack.org/neutron/latest/admin/fwaas-v1-scenario.html
the configuration is confused.
The configration in step 1 is:
[fwaas]
driver =
neutron_fwaas.services.firewall.drivers.linux.iptables_fwaas.IptablesFwaasDriver
enabled = True
But in the
Everything goes through nova-conductor for database updates so if that's
down, you have problems. You can reset the state of the instance using
the reset state API (as admin):
https://docs.openstack.org/python-openstackclient/latest/cli/command-
objects/server.html#server-set
nova server set
This is already fixed in master (rocky) and stable/queens:
https://review.openstack.org/#/q/I5c0a6389b759153bae06fa43846f03ac083c3db4
** Changed in: nova
Status: New => Fix Released
** Changed in: nova
Assignee: (unassigned) => caoyuan (cao-yuan)
--
You received this bug
This isn't a nova bug. Check your db configuration, maybe you have too
many open connections or the host running the db is overwhelmed.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: nova/pike
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/1777129
Title:
live migration doc says
Public bug reported:
I noticed this from the nova-compute logs attached to bug 1777157:
2018-06-15 16:23:46.954 7 ERROR nova.compute.manager
[req-69050681-be73-48c5-be25-993f05b0b47e e511323a68a740f597880a1b056e3918
28f4e0797d544d758700e5be42aa82c6 - default default] [instance:
Something is wrong with your configuration, there is no RPC API call
during validate_networks from the API if you're using neutron. Only
nova-network would have an RPC API call for validate_networks. Are you
using nova-network? If not, you should have use_neutron=True in
nova.conf.
** Changed in:
What is the error from the nova-api logs?
** Changed in: nova
Status: New => Incomplete
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Typo in the bug description, it's not "amdb-no-ssb" it's amd-no-ssb.
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
**
Reviewed: https://review.openstack.org/572168
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=f98f239a15d68344f84ca755dd8a55698d528b1c
Submitter: Zuul
Branch:master
commit f98f239a15d68344f84ca755dd8a55698d528b1c
Author: Swaminathan Vasudevan
Date: Mon Jun 4
Public bug reported:
It looks like neutron-rally-neutron job is failing 100% times for
stable/pike and stable/ocata branches.
For stable/pike examples of failures are:
http://logs.openstack.org/73/575773/3/check/neutron-rally-neutron/7d0b7e0/logs/devstacklog.txt.gz#_2018-06-18_14_55_27_399
Public bug reported:
_update_available_resource() in nova/compute/resource_tracker.py invokes
_init_compute_node() which internally calls _update() and once again _update()
is invoked at the end of _update_available_resource().
Public bug reported:
OpenStack Queens release.
With developer panel and profiler enabled, you can select "Profile
Current Page" to create a new profiler trace. That initializes a
profiler instance here:
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova
Importance: High => Medium
--
You received this bug notification because you
This is already fixed in the neutron master branch,
https://review.openstack.org/#/c/566491/
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
This has already been fixed in the neutron master branch,
https://review.openstack.org/#/c/566491/
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
Seen here:
http://logs.openstack.org/01/571201/1/gate/nova-
cells-v1/56392c6/logs/screen-n-cell-
child.txt.gz?level=TRACE#_Jun_18_14_14_15_307670
The new tempest test is using 2.63 with trusted certs for rebuild which
isn't supported with cells v1.
Jun 18 14:14:15.307670
Public bug reported:
Hi,
I was trying to rebuild a VM after switching off the existing VM. But i
got the below error,
[root@gec-* ~]# nova rebuild ***0445424001 _ldap_rhel5u11_64_091117
--poll
+---+
|
Public bug reported:
In addition to the existing 'virt-ssbd', future AMD CPUs will have _two_
ways to deal with SSBD (Speculative Store Bypass Disable). To that AMD
will be introducing two more[1][2] CPU flags:
amd-ssbd
amdb-no-ssb
It is recommended to add the above two flags to the
Public bug reported:
This is very similar to bug 1773945 but has a specific recreate:
1. create server
2. while it's a build request (before scheduling), immediately list servers
with the id from server in #1 as the marker and filter using the 'ip' filter -
it doesn't matter what the value is
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
Public bug reported:
Seen here:
http://logs.openstack.org/10/515210/39/check/barbican-simple-crypto-
devstack-
tempest/7b7f049/logs/screen-n-cpu.txt.gz?level=TRACE#_Jun_15_18_35_04_327368
Jun 15 18:35:04.310640 ubuntu-xenial-inap-mtl01-165445 nova-compute[1555]:
ERROR
Public bug reported:
These warnings are over the nova-api logs in the reference CI job:
http://logs.openstack.org/10/515210/39/check/barbican-simple-crypto-
devstack-
tempest/7b7f049/logs/screen-n-api.txt.gz?level=TRACE#_Jun_15_18_30_55_364299
Jun 15 18:30:55.364299
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: __
- [ x] This is a doc addition request.
- [ x] I have a fix
Public bug reported:
We have 250 instances on a compute node and the resource tracker
periodic task is taking very long:
2018-06-17 10:30:56.194 1658 DEBUG oslo_concurrency.lockutils [req-
fb2573f9-3862-45db-b546-7a00fdd9a871 - - - - -] Lock "compute_resources"
released by
Public bug reported:
https://developer.openstack.org/api-ref/compute/#create-server
In the "Create Server" API, the 'trusted_image_certificates' parameter
should be before 'os:scheduler_hints' parameters because the
'trusted_image_certificates' parameter is inside of the 'server'
object(dict).
32 matches
Mail list logo