Public bug reported:
Description
===
When the nova-compute starts to running, the nova-scheduler log displays many
exceptions.
exceptions:
[req-4f1d7888-2324-4c9d-b88b-f468159b1364 None None] Exception during message
handling
(/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/se
[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/1675339
Ti
Reviewed: https://review.openstack.org/468361
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=1e9aca11b9736993e39972a36ecd53765f4b580a
Submitter: Jenkins
Branch:master
commit 1e9aca11b9736993e39972a36ecd53765f4b580a
Author: Jens Rosenboom
Date: Fri May 26 11:02:05 2
Reviewed: https://review.openstack.org/466143
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a2b0824aca5cb4a2ae579f625327c51ed0414d35
Submitter: Jenkins
Branch: master
commit a2b0824aca5cb4a2ae579f625327c51ed0414d35
Author: Guang Yee
Date: Thu May 18 16:38:16 2017 -0700
https://review.openstack.org/#/c/468585/
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => Critical
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova
Status: New => In Progress
Public bug reported:
Spotted in the gate.
Version: stable/newton
test_walk_versions
sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2014,
'Command Out of Sync')
http://logs.openstack.org/96/460696/1/check/gate-neutron-dsvm-
functional-ubuntu-xenial/0e31fb6/testr_results.html.gz
Public bug reported:
I've got confirmation that the chassis_asset_tag DMI value is a hard-
coded identifier for the Azure platform (both Azure and Azure Stack (the
on-premise variant of Azure)).
$ cat /sys/class/dmi/id/chassis_asset_tag
7783-7084-3265-9085-8269-3286-77
The detection logic in bot
Public bug reported:
It's newton.
http://logs.openstack.org/27/467427/1/check/gate-neutron-dsvm-
functional-ubuntu-xenial/2860749/testr_results.html.gz
Traceback (most recent call last):
File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/fixtures/fixture.py",
This goes back to newton:
https://github.com/openstack/nova/blob/stable/newton/nova/compute/api.py#L2341
** Also affects: nova/newton
Importance: Undecided
Status: New
** Changed in: nova/newton
Importance: Undecided => High
--
You received this bug notification because you are a
Here is the problem:
All of your instances are in ERROR state so they are in cell0 and we'll
pull them from cell0 here:
https://github.com/openstack/nova/blob/15.0.3/nova/compute/api.py#L2466
We got 2 back from cell0 but limit was 3, so we make limit=1 here:
https://github.com/openstack/nova/bl
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1685935
Title:
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubunt
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubunt
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
*
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubunt
** No longer affects: nplan (Ubuntu)
** No longer affects: nplan (Ubuntu Xenial)
** No longer affects: nplan (Ubuntu Yakkety)
** No longer affects: nplan (Ubuntu Zesty)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
There is nothing for nova to do with this right? Didn't eventlet get
blacklisted in g-r recently for this?
https://github.com/eventlet/eventlet/issues/401
https://github.com/openstack/requirements/commit/e3c286a2f22011ae129e13892455a4a25bddeb1b
** Changed in: oslo.db
Status: New => Invali
Two things:
1. As Brian pointed out, python-novaclient 8.0.0 dropped this deprecated
command.
2. There is not enough information from this bug report to know what the
actual issue is, so please attach the nova-api logs or a snippet of the
error from them, but we're unable to triage this without m
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubunt
Public bug reported:
This issue was actually nicely written up here: https://iclykofte.com
/physical-host-metrics-in-ceilometer-an-openstack-liberty-tale/ ...but
apparently never made it into a bug/patch. If you supply more than one
driver to compute_monitors in a list per the setting help, the
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John Ledkov] (LP: #1689346, #16843
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John Ledkov] (LP: #1689346, #16843
This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1
---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- net: fix reading and rendering addresses in cidr format.
[Dimitri John Ledkov] (LP: #1689346, #16843
Public bug reported:
http://logs.openstack.org/99/460399/2/check/gate-tempest-dsvm-neutron-
full-ubuntu-xenial/f7eb334/logs/testr_results.html.gz
ft1.2:
tempest.api.identity.v3.test_users.IdentityV3UsersTest.test_user_account_lockout[id-a7ad8bbf-2cff-4520-8c1d-96332e151658]_StringException:
pyt
** Also affects: nova/newton
Importance: Undecided
Status: New
** Changed in: nova/newton
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova/newton
Importance: Undecided => Low
** Changed in: nova/newton
Status: New => In Progress
** Changed in: nova
Dupe of 1692397
** Changed in: nova
Status: New => Won't Fix
--
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/1693911
Title:
compute node statistics will lie if se
*** This bug is a duplicate of bug 1648840 ***
https://bugs.launchpad.net/bugs/1648840
This sounds like a duplicate of bug 1648840 which was fixed and
backported to stable/newton and release in 14.0.3:
https://review.openstack.org/#/c/409706/
stable/mitaka is end of life upstream though so w
Public bug reported:
If a compute node references a deleted service, we will include it in
the compute node statistics output. This happens even if the compute
node record _is_ deleted, because of our join of the services table,
which causes us to get back rows anyway. This results in the stats
sh
What is CSR? Which release of nova is this? Is there more to the error
like a stacktrace because I don't see anything about "prompt" in the
code. Do you have API extensions that aren't in the upstream git repo?
** Changed in: nova
Status: New => Invalid
--
You received this bug notificati
** Also affects: nova/newton
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova
Importance: Undecided => High
** Changed in: nova/newton
Importance: Undecided => High
** Changed in: nova/ocata
Importan
Anything hypervisor specific should probably be somewhere in the manuals
here:
https://docs.openstack.org/ocata/config-
reference/compute/hypervisors.html
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova
Status: New => Opinion
--
You received this bug notification
*** This bug is a duplicate of bug 1643444 ***
https://bugs.launchpad.net/bugs/1643444
** This bug has been marked a duplicate of bug 1643444
TenantUsagesTestJSON.test_list_usage_all_tenants 500 from Db layer
--
You received this bug notification because you are a member of Yahoo!
Enginee
Reviewed: https://review.openstack.org/439960
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=55d42affb7760b836f5aecd613d95bceeffed613
Submitter: Jenkins
Branch:master
commit 55d42affb7760b836f5aecd613d95bceeffed613
Author: Huan Xie
Date: Wed Mar 1 18:58:02 2017 -0800
Reviewed: https://review.openstack.org/467369
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=f022d431e1f844a8faa7ab55597c83179c13022c
Submitter: Jenkins
Branch:master
commit f022d431e1f844a8faa7ab55597c83179c13022c
Author: Lucian Petrut
Date: Tue May 23 22:45:20 2017
Reviewed: https://review.openstack.org/467220
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=3d3e9cdd774efe96f468f2bcba6c09a40f5e71d3
Submitter: Jenkins
Branch:master
commit 3d3e9cdd774efe96f468f2bcba6c09a40f5e71d3
Author: Kevin_Zheng
Date: Tue May 23 20:28:28 2017 +0
It looks like the database migrations weren't run. See:
nova-manage api_db sync
nova-manage db sync
** Changed in: nova
Status: New => Invalid
--
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:
I noticed this here:
https://review.openstack.org/#/c/460177/12/nova/compute/resource_tracker.py
Which is part of a refactor, and that warning actually goes back to
newton:
https://github.com/openstack/nova/commit/9374566d194be1e861e7d08dd0e3b2a615ff408c
It shows up a ton:
Public bug reported:
Noticed what appears to be a race on delete of an instance where we're
deleting resource provider allocations records for a deleted instance
and when we go to get the instance from the database it's already
deleted:
http://logs.openstack.org/32/468232/1/gate/gate-tempest-dsvm
** Also affects: nova/ocata
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/1667679
Title:
Setting quota fails saying admin pr
*** This bug is a duplicate of bug 1667679 ***
https://bugs.launchpad.net/bugs/1667679
Related to https://bugs.launchpad.net/tripleo/+bug/1667679 and
https://review.openstack.org/#/c/438049/
** This bug has been marked a duplicate of bug 1667679
Setting quota fails saying admin project is
*** This bug is a duplicate of bug 1667679 ***
https://bugs.launchpad.net/bugs/1667679
Keystone v2 has been deprecated since I think the Mitaka release, but I
agree that if we don't need to we shouldn't munge the v3 into the URL.
** Also affects: nova/ocata
Importance: Undecided
Sta
Fixed in:
https://git.launchpad.net/cloud-init/commit/?id=2825a917e5fa130818c0d77219f32961b99a057f
** Changed in: cloud-init
Status: New => Fix Released
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
E
Fixed in:
https://git.launchpad.net/cloud-init/commit/?id=e5b2c011440aefe036c71a8c5e8ec547cc80f270
** Changed in: cloud-init
Status: New => Fix Released
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Eng
Reviewed: https://review.openstack.org/414463
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=0df91a7f799060cd2e9b8a0adac1efacb974bcb3
Submitter: Jenkins
Branch:master
commit 0df91a7f799060cd2e9b8a0adac1efacb974bcb3
Author: Tao Li
Date: Fri Dec 23 10:35:01 2016 +0800
Reviewed: https://review.openstack.org/466143
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a2b0824aca5cb4a2ae579f625327c51ed0414d35
Submitter: Jenkins
Branch:master
commit a2b0824aca5cb4a2ae579f625327c51ed0414d35
Author: Guang Yee
Date: Thu May 18 16:38:16 2017 -070
** Also affects: keystone/ocata
Importance: Undecided
Status: New
** Also affects: keystone/newton
Importance: Undecided
Status: New
** Changed in: keystone/ocata
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineeri
I agree with comment #2. It would appear that this is something we
should be doing in devstack and unrelated to the keystone service.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscrib
I don't know what "Why because tenant_id is project_id now." means here.
The default policy for cloudpipe actions is admin-only, so if you're
trying to do this as a non-admin it's going to fail.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you a
The correct way to do it would be to add a tmpfiles.d config file, that
would create the directory at startup. also it's not about keystone, but
about devstack
** Also affects: devstack
Importance: Undecided
Status: New
** Summary changed:
- Start keystone service failed with uwsgi in
** Changed in: nova
Status: New => Invalid
** Also affects: fuel
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
This is not a bug. If you want to add this it will require a blueprint.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Op
Added MOS since I think that's tied to Fuel, plus mitaka is end of life
upstream for nova.
** Also affects: mos
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).
I used the instance uuid to find the request id in the nova-conductor
logs and then looked for that request id in the nova-scheduler logs and
found this:
2017-05-25 21:12:36.102 2562 WARNING nova.scheduler.client.report
[req-8359c011-587a-4c60-95a1-ded9e50b26af 15d62a6cd8db41f48d9a85d9aaff958f
f
Public bug reported:
I am trying to create an openstack environment using Fuel 9.0 -
Openstack Mitaka-9.0.
The issue is related to when creating a vlan link the network name with
vlan id number exceeds the 16 character length so it fails.
the why: There are 2 nodes and a Fuel Server. both nodes
Reviewed: https://review.openstack.org/461494
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=fcfe28192eaa63d2ca000d38bc435a5e662ad8f5
Submitter: Jenkins
Branch:master
commit fcfe28192eaa63d2ca000d38bc435a5e662ad8f5
Author: EdLeafe
Date: Mon May 1 15:32:06 2017 +
Public bug reported:
That's what produced by `keystone-manage doctor` when no caching is
enabled.
WARNING: `keystone.conf [caching] enabled` is not enabled.
Caching greatly improves the performance of keystone, and it is highly
recommended that you enable it.
There's no [caching] sectio
Public bug reported:
When running an instance on a network with ipv6-address-mode
dhcpv6-stateful, the instance fails to receive responses from the DHCP
server. The workaround is to add an explicit security group rule
allowing
--proto udp --dst-port 546 --ethertype IPv6
and then the DHCP handsha
Reviewed: https://review.openstack.org/421818
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=45fd7eef6eb0fe5c760338953c91c046730f153c
Submitter: Jenkins
Branch:master
commit 45fd7eef6eb0fe5c760338953c91c046730f153c
Author: Miguel Angel Ajo
Date: Wed Jan 18 11:46:34
Reviewed: https://review.openstack.org/460616
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=62878ef5a6c9f6a2c727c91397830387425c4d37
Submitter: Jenkins
Branch:master
commit 62878ef5a6c9f6a2c727c91397830387425c4d37
Author: Dan Smith
Date: Thu Apr 27 07:55:40 2017 -070
** Changed in: neutron
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1597461
Title:
L3 HA: 2 masters after reboot of controller
Status in neutr
Public bug reported:
in controller+2 Compute node instance is not getting evacuated from one
compute node to other compute node. On evacuation it gets stuck with state as
rebuilding on the source node.
Below was logged in the destination compute node
(/var/log/nova/nova-compute.log):
2017-04-1
Public bug reported:
Description
===
When creating a server,
if a compute node doesn't belong any cell and nova-scheduler selects the host,
creating a server fails (HostMappingNotFound) and a server status become stuck
in 'BUILD'.
The server cannot be deleted by "Delete server" API.
Thi
Public bug reported:
When I got the federated user project list, the error is as bellow:
2017-05-26 15:12:54.685 12742 ERROR keystone.common.wsgi File
"/usr/lib/python2.7/site-packages/keystone/common/wsgi.py", line 228, in
__call__
2017-05-26 15:12:54.685 12742 ERROR keystone.common.wsgi
69 matches
Mail list logo
