Feel free to backport this since it was introduced in Queens.
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => yenai (yenai2008)
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
**
** Changed in: nova/rocky
Status: In Progress => Invalid
** No longer affects: nova/rocky
--
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/1737050
Title:
No way
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/rocky
Status: New => In Progress
** Changed in: nova/ocata
Also seeing this in stable/queens:
https://review.openstack.org/#/c/649362/
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/queens
Importance: Undecided => Medium
--
You received this
Public bug reported:
Horizon gives error when attempting to update a existing cluster..
[Fri Apr 05 21:29:40.182367 2019] [:error] [pid 50] Traceback (most recent call
last):
[Fri Apr 05 21:29:40.182378 2019] [:error] [pid 50] File
Reviewed: https://review.openstack.org/522245
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=05a73c0f3a9f8edf9024f9870279bc6fb7bba2e7
Submitter: Zuul
Branch:master
commit 05a73c0f3a9f8edf9024f9870279bc6fb7bba2e7
Author: Silvan Kaiser
Date: Wed Nov 22 14:35:11 2017
Reviewed: https://review.openstack.org/522245
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=05a73c0f3a9f8edf9024f9870279bc6fb7bba2e7
Submitter: Zuul
Branch:master
commit 05a73c0f3a9f8edf9024f9870279bc6fb7bba2e7
Author: Silvan Kaiser
Date: Wed Nov 22 14:35:11 2017
Public bug reported:
As reported on the Debian cloud mailing list [1] we should consider
enabling or including a log rotation script.
[1] https://lists.debian.org/debian-cloud/2019/04/msg00022.html
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug
Reviewed: https://review.openstack.org/647784
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=8cc480bd01d21f05296c77db231b706a7dc5b475
Submitter: Zuul
Branch:master
commit 8cc480bd01d21f05296c77db231b706a7dc5b475
Author: LIU Yulong
Date: Tue Mar 26 23:47:11 2019
Also, force_hosts/force_nodes could be accidentally persisted in this
case as well:
https://github.com/openstack/nova/blob/a6963fa6858289d048e4d27ce8e61637cd023f4c/nova/compute/api.py#L3337-L3338
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
I likely need to write a functional test to recreate this first to see
how things fail.
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Public bug reported:
During most move operations we restrict the request spec to the cell the
instance is in before calling the scheduler:
unshelve:
https://github.com/openstack/nova/blob/a6963fa6858289d048e4d27ce8e61637cd023f4c/nova/conductor/manager.py#L822
cold migrate:
Public bug reported:
This is based on code inspection and related to bug 1815153 (see
comments 1-4) but when we rebuild a server with a new image we go
through the scheduler with a special scheduler hint:
Reviewed: https://review.openstack.org/648951
Committed:
https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=7f0b4f3001575d1419c5020e007ce2c841c88f2f
Submitter: Zuul
Branch:master
commit 7f0b4f3001575d1419c5020e007ce2c841c88f2f
Author: Jens Harbott
Date: Mon Apr 1 11:43:28
Public bug reported:
Sometimes when 2 HA routers are created for same tenant in very short
time, it may happen that both routers will have same vr_id assigned thus
it will be same application for keepalived and only one of those routers
will be active on some hosts.
When I spotted it it looked
Reviewed: https://review.openstack.org/646082
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=531fdc336b1b6b74de1b148b0dfe9eebd9e5cdc3
Submitter: Zuul
Branch:master
commit 531fdc336b1b6b74de1b148b0dfe9eebd9e5cdc3
Author: Rodolfo Alonso Hernandez
Date: Sun Mar 24
Public bug reported:
When new network segment range is created for vlan network type and
physical_network is not specified it fails with error 500.
Traceback in neutron-server logs:
ERROR oslo_db.sqlalchemy.exc_filters [None
req-4e6378b0-1bd1-4166-b9f0-88be75d3e029 admin admin] DB exception
https://review.openstack.org/#/c/648522/ introduced the KeyError
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
18 matches
Mail list logo