** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engin
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: nova
Importance: Undecided => Medium
--
You received this bug notification becau
It looks like the [neutron] section of your nova.conf used by the nova
API service is not configured properly for nova to communicate with
neutron, see:
https://docs.openstack.org/nova/latest/configuration/config.html#neutron
https://docs.openstack.org/neutron/stein/install/controller-install-
ub
Not a nova bug.
** Changed in: nova
Status: Fix Committed => Invalid
--
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/1829161
Title:
Could not install packages due
** Also affects: nova/rocky
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/1820125
Title:
Libvirt driver ungracefully explode
** Changed in: nova
Importance: Undecided => High
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Tags added: libvirt scheduler upgrade
** Changed in: nova/rocky
Status: New => Triaged
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Importance: Undecided => Low
** Changed in: nova/stein
Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)
--
You received
sqlalchemy docs:
https://docs.sqlalchemy.org/en/13/changelog/migration_09.html#new-query-
options-api-load-only-option
Added cinder since this also hits in cinder jobs in logstash.
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Importance: Undecided => Low
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova/stein
Assignee: (unassigned)
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Andrey Volkov (avolkov)
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/rocky
Assignee: (unassigned) => Andrey Volkov (avolkov)
** Changed in: nova/rocky
Status: New
** Tags added: evac
** Tags removed: evac
** Tags added: evacuate performance
** Changed in: nova
Importance: Undecided => Low
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: no
I'm going to mark this as Invalid given the old release (newton) and the
fact it might already be fixed if you can upgrade.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStac
*** This bug is a duplicate of bug 1825020 ***
https://bugs.launchpad.net/bugs/1825020
** This bug has been marked a duplicate of bug 1825020
resize of instance, that was booted from volume, trigger image size check
then fails resize
--
You received this bug notification because you are
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.
Public bug reported:
This came up in review here:
https://review.opendev.org/#/c/667177/8/nova/virt/libvirt/driver.py@9175
And was confirmed in a functional test patch here:
https://review.opendev.org/#/c/670393/
There are some known things that get left behind when recovering a guest
on the s
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/rocky
Status: New => Confirmed
** Changed in: nova/stein
Status: New => Confirmed
** Changed in: nova/rocky
Import
*** This bug is a duplicate of bug 1750618 ***
https://bugs.launchpad.net/bugs/1750618
OK I found something which might be the reason you're hitting this.
There was a fix that was backported to newton upstream:
https://review.opendev.org/#/q/I11746d1ea996a0f18b7c54b4c9c21df58cc4714b
Which c
Public bug reported:
- [x] This doc is inaccurate in this way:
https://developer.openstack.org/api-ref/compute/#servers-actions-
servers-os-instance-actions
The user_id and project_id parameter descriptions for server actions
imply that they are the value of the user/project that owns the server
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => Fix Released
** Changed in: no
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => In Progress
** Changed in: no
** Changed in: nova/rocky
Status: In Progress => Fix Released
--
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/1821696
Title:
Failed to start instances with encrypt
The DiskFilter was deprecated in Stein
https://review.opendev.org/#/c/596502/ and this bug was reported before
the scheduler was using placement for disk filtering in Pike, so it may
not be valid anymore. If you think it is, please recreate on the latest
release of Stein 19.* and re-open with new d
I have a feeling this is probably fixed since Pike or at least Rocky
because the DiskFilter has been deprecated in favor of using the
placement service for filtering hosts based on DISK_GB inventory which
accounts for root, ephemeral and swap disk. Furthermore
https://review.opendev.org/#/c/580720/
Public bug reported:
This is a follow up to bug 1834694 with the debug information here:
https://review.opendev.org/#/c/668252/1/nova/scheduler/host_manager.py@626
This is on an overloaded system where conductor and mysql are having
problems and database connections are getting dropped.
On the
This goes back to Rocky when the CPUWeigher was added:
https://review.opendev.org/#/c/379525/
** Changed in: nova
Status: New => Triaged
** Changed in: nova
Importance: Undecided => High
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/ste
Public bug reported:
This is similar to bug 1834691 in that the CPUWeigher can hit this
error:
Jun 28 20:26:07 devstack nova-scheduler[24099]: ERROR oslo_messaging.rpc.server
[None req-df4ac006-fddf-4e6f-9c5e-1c352be60d9b admin admin] Exception during
message handling
Jun 28 20:26:07 devstack n
The HostState.failed_builds change was introduced in Rocky and
backported through to Pike:
https://review.opendev.org/#/q/I71c56fe770f8c3f66db97fa542fdfdf2b9865fb8
** Tags added: scheduler
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/stein
Im
b8329a58e62c8a89204fdeaa16dca/nova/scheduler/host_manager.py#L787
Ah bingo if the compute node hasn't had resource usage updated yet we
don't set the failed_builds attribute:
https://github.com/openstack/nova/blob/231908a7f42b8329a58e62c8a89204fdeaa16dca/nova/scheduler/host_manager.p
** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** No l
*** This bug is a duplicate of bug 1666831 ***
https://bugs.launchpad.net/bugs/1666831
I think this may have been fixed with
https://review.opendev.org/#/c/566367/.
** Tags added: ceph libvirt
** This bug has been marked a duplicate of bug 1666831
Nova recreates instance directory after m
** Changed in: nova
Assignee: Matt Riedemann (mriedem) => Miguel Ángel Herranz Trillo
(maherranzt)
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importa
This is the related mailing list thread:
http://lists.openstack.org/pipermail/openstack-
discuss/2019-June/007363.html
I've proposed that when forcefully rebuilding the cache, since we don't
know which ports nova created on behalf of the user, we should detect
that and set preserve_on_delete=True
** Changed in: nova
Status: New => Invalid
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova/pike
Importance: Undecided => Low
** Changed in: nova/rocky
Importance: Undecided => Low
** Changed in
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => Confirmed
** Changed in: nova/stein
Importance: Undecided => Medium
--
You received this bug notification because yo
Public bug reported:
Seeing this in CI jobs:
http://logs.openstack.org/45/666845/1/check/neutron-tempest-dvr-ha-
multinode-
full/5b09053/controller/logs/screen-n-cpu.txt#_Jun_26_13_51_48_973568
Jun 26 13:51:48.973568 ubuntu-bionic-ovh-bhs1-0008373888 nova-compute[27912]:
ERROR nova.compute.mana
** 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.launchpad.net/bugs/1830417
Title:
NoVNCConsoleTestJSON.test_novnc fails in nova-multi-cell job since
5/20
Statu
Public bug reported:
Seen in a stable/stein change here:
http://logs.openstack.org/43/665143/1/check/tempest-slow-
py3/c36a4a8/compute1/logs/screen-neutron-
agent.txt.gz?level=TRACE#_Jun_24_10_58_51_041785
Jun 24 10:58:50.296667 ubuntu-bionic-ovh-gra1-0008250201 neutron-
openvswitch-agent[15936]
** Also affects: neutron/stein
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Also affects: neutron/queens
Importance: Undecided
Status: New
** Also affects: neutron/pike
Importance: Undecided
Status: New
** Also affects: neutron
the openstack CLIs but those could maybe be done in
separate changes.
** Affects: neutron
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: Triaged
** Tags: doc quotas
** Changed in: neutron
Status: New => Triaged
** Changed in: neutron
Importa
Goes back to pike:
https://review.opendev.org/#/c/490952/4/doc/source/admin/quotas.rst@89
And since the command usage was changed during the doc import, it likely
means the whole page needs to be validated for accuracy at this point.
** Changed in: nova
Status: New => Triaged
** Changed
I'm going to mark this as not fixed yet because it introduced a
regression for same host resize + revert and the fix is being reverted
on master since it broke neutron's CI jobs:
https://review.opendev.org/#/c/667035/
** Changed in: nova
Status: Fix Released => Triaged
--
You received th
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Confirmed
** Changed in: nova/ocata
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
We don't have a clear reproducer of the issue so we don't really know
what's going on here, and haven't had any replies in a long time so I'm
going to mark this as invalid.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of
Because of https://review.opendev.org/#/c/605041/ I think we can take
the fix back to stable/rocky.
** Changed in: nova
Assignee: sean mooney (sean-k-mooney) => Artom Lifshitz (notartom)
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
I
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/queens
Importance: Undecided => Medium
** Changed in: n
https://opendev.org/openstack/nova/src/doc/source/admin/configuration/schedulers.rst
URL: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html
** Affects: nova
Importance: Low
Assignee: Matt Riedemann (mriedem)
Status: Confirmed
** Tags: doc
** Changed in:
>From https://review.opendev.org/#/c/664838/1/nova/pci/stats.py@a272 it
sounds like the "preferred" policy is what the user wanted.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Importance: Undecided => High
** Changed in: nova/stein
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Tags added: libvirt
*** This bug is a duplicate of bug 1718512 ***
https://bugs.launchpad.net/bugs/1718512
** This bug has been marked a duplicate of bug 1718512
migration fails if instance build failed on destination host
--
You received this bug notification because you are a member of Yahoo!
Engineering T
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova/stein
Importance: Undecided => Low
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/rocky
Status: New => In Progress
** Changed in: nova/rocky
Assignee: (unassigned)
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/rocky
Status: New => In Progress
** Changed in: nova/stein
Status: New => Fix Released
** Changed in: nova/rocky
I
** Changed in: nova/stein
Status: In Progress => Fix Released
--
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/1821696
Title:
Failed to start instances with encrypt
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => Fix Released
** Changed in: nova/stein
Importance: Undecided => Medium
** Changed in: nova/stein
Assignee: (unassigned) => Lee Yarwood (lyarwood)
--
You received this
*** This bug is a duplicate of bug 1804062 ***
https://bugs.launchpad.net/bugs/1804062
Public bug reported:
Seen here:
http://logs.openstack.org/61/660761/7/check/openstack-tox-
py27/b10a9a6/testr_results.html.gz
ft1.34:
nova.tests.unit.test_hacking.HackingTestCase.test_check_doubled_words
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => Confirmed
** Changed in: nova
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/rocky
Status: New => Fix Released
** Changed in: nova/rocky
Importance: Undecided => Medium
** Changed in: nova/rocky
Assignee: (unassigned) => Lee Yarwood (lyarwood)
--
You received this
OK so maybe this is just noise and if it's not causing any real issues
we could invalidate this bug.
** 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 Compute (nova).
Public bug reported:
During each scheduling request we build a HostState object per compute
node that is a candidate for scheduling:
https://github.com/openstack/nova/blob/9a7eee1592d84c732415da639c85ce4b262eefab/nova/scheduler/host_manager.py#L796
That eventually calls to _update_from_compute_n
This is low priority since most production deployments are probably not
running with split conductors and the cell conductor being isolated from
the API DB, it's mostly only an issue we hit in devstack, therefore I
probably won't backport this past Stein unless someone needs it.
** Changed in: nov
It's failing when trying to communicate with neutron so my guess would
be there is something wrong with the user/project setup for the neutron
user that nova is configured to use:
[neutron]
url = http://controller:9696
auth_url = http://controller:5000
auth_type = password
piroject_domain_name =
This isn't really a nova bug so I'm going to mark invalid.
** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1831424
** Changed in: nova
Importance: Low => Medium
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/rocky
Status: N
In this case the compute service is managing baremetal nodes using the
ironic driver, correct? In that case yes the ComputeFilter will reject
all nodes managed by that compute service host because it has been
disabled, just like it would in a 1:1 host:node (hypervisor) topology
when using the libvi
I think at this point we can mark the nova portion of this as won't fix
with these changes to manage allocation ratios:
https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html
#allocation-ratios
The workaround outside of that is to rely on that osc-placement patch
linked into c
OK it looks like this is your problem, OSA disables versioned
notifications by default:
https://github.com/openstack/openstack-ansible-
os_nova/blob/7d4b4ef3700d678c30435a90a54742a18d0f7941/defaults/main.yml#L26
https://github.com/openstack/openstack-ansible-
os_nova/blob/7d4b4ef3700d678c30435a90
I'm not sure why this is a nova bug - if the tenant has multiple
networks available to it, the request to create the server must specify
a network (or port) otherwise yes you get the 400 NetworkAmbiguous
error. This sounds like a Rally bug rather than a nova bug.
Note there is a related blueprint
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/queens
Status: New => In Progress
** Changed in: no
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
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
The patch was just on test code, which bandit shouldn't be scanning.
** Changed in: nova
Status: In Progress => Invalid
** Changed in: nova
Assignee: Spencer Yu (yushb) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which i
Regarding comment #2, someone said they still have the problem in Queens
(maybe using a different libvirt / qemu version if that matters?):
Maxence Sartiaux
Apr 9, 2018
Patch Set 6:
I tried in Queens, still have the error, libvirt try to open the swap
file
** Changed in: nova
Assignee: Kam
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nov
This isn't really a nova bug that I can tell, it sounds more like a test
execution bug in tempest.
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engi
> The API reference is generated from master branch only.
True they are published from master only, but...
> So stable branches do not have to be fixed.
If someone is building docs from the stable branch code for their
product, then the api-ref changes could be backported. This is also a
small e
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/rocky
Status: New => Triaged
** Changed in: nova/stein
Status: New => Triaged
** Changed in: nova/rocky
Importance
Public bug reported:
- [x] This doc is inaccurate in this way:
The server group policy field added in v2.64 is a string but the API
reference says the parameter is an object.
https://github.com/openstack/nova/blob/37ccd7ec3a0f0b8f636d8dd82e6e929f462f6586
/api-ref/source/parameters.yaml#L5368
ht
Sounds like this is solved with versioned notifications so is not a nova
bug.
** 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://bugs.launchpad.net/b
I don't understand what you're saying about this being a bug. The code
was removed in master, so why is that a bug? Do you have proprietary
code that depended on it? If so, you'll have to adjust your code on
master.
** Changed in: nova
Status: New => Invalid
--
You received this bug notif
This might explain what's happening during a cold migration.
Conductor creates a legacy filter_properties dict here:
https://github.com/openstack/nova/blob/stable/rocky/nova/conductor/tasks/migrate.py#L172
If the spec has an instance_group it will call here:
https://github.com/openstack/nova/bl
ENCES `instances` (`uuid`))') [SQL: 'DELETE FROM instances WHERE
instances.uuid = %(uuid_1)s'] [parameters: {'uuid_1': '4b8a12c4-e28a-
49cc-a681-236c1e8a174c'}]
** Affects: nova
Importance: Medium
Assignee: Matt Riedemann (mriedem)
Status: In Progress
Public bug reported:
Ever since we enabled the n-novnc service in the nova-multi-cell job on
May 20:
https://github.com/openstack/nova/commit/c5b83c3fbca83726f4a956009e1788d26bcedde0
#diff-7415f5ff7beee2cdf9ffe31e12e4c086
The
tempest.api.compute.servers.test_novnc.NoVNCConsoleTestJSON.test_novnc
Public bug reported:
We have a performance regression since Stein [1] when listing servers
with details concerning the host_status field. The code used to rely on
this method [2] to cache the host status information per host when
iterating over a list of instances but now it fetches it per host pe
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => Triaged
** Changed in: nova/rocky
Importance: Undecided => Medium
** Changed in: nova/stein
Importance: Undecided => Medium
--
You received this bug notification becaus
The inefficient query goes back to Icehouse when the
InstanceGroup.get_hosts() method was introduced:
https://review.opendev.org/#/c/77786/
So we can at least backport the #1 fix above to stable/ocata.
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova
would likely need to be a remotable method
because InstanceGroup.get_hosts() is calling in the late affinity check
ComputeManager._validate_instance_group_policy() method in the nova-
compute service (and because InstanceGroup.get_hosts() is remotable
itself).
** Affects: nova
Importance: Medium
Assignee:
** Also affects: nova/stein
Importance: Undecided
Status: New
** 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: no
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Importance: Undecided => Medium
** Changed in: nova/stein
Assignee: (unassigned) => Lee Yarwood (lyarwood)
--
You received this
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Assignee: (unassigned) => Silvan Kaiser (2-silvan)
--
You received this bug notification because you are a member of Yahoo!
Engineer
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Status: New => In Progress
** Changed in: nova/stein
Assignee: (unassigned) => Silvan Kaiser (2-silvan)
--
You received this bug notification because you are a member of Yahoo!
Engineer
** Also affects: nova/stein
Importance: Undecided
Status: New
** Changed in: nova/stein
Assignee: (unassigned) => Silvan Kaiser (2-silvan)
** Changed in: nova/stein
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineer
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
--
You received this b
Public bug reported:
While debugging a neutron failure from the nova logs, I'm tracing the
API request through the nova logs using the request ID generated from
the nova RequestContext created in the API.
Down in the nova-compute code it's deleting a port binding resource in
neutron, but because
Public bug reported:
I noticed today that when shutting down an instance, like for a snapshot
test, it's sometimes taking a full 60 seconds to wait for the graceful
shutdown before just destroying the guest:
http://logs.openstack.org/56/656656/12/check/nova-multi-
cell/6a403ba/compute1/logs/scree
Public bug reported:
During a cold migration the compute API resize() method checks the
instance.flavor:
https://github.com/openstack/nova/blob/53d42de9d970abc290064ab86df272b4d933abc9/nova/compute/api.py#L3587
But this results in a query to the DB:
May 16 19:46:21.368204 ubuntu-bionic-rax-dfw-
** Changed in: nova/pike
Status: Confirmed => Won't Fix
** Changed in: nova/queens
Status: In Progress => Won't Fix
** Changed in: nova/queens
Assignee: Matt Riedemann (mriedem) => (unassigned)
--
You received this bug notification because you ar
Public bug reported:
Seeing this which is low priority but clutters up the logs so we should
clean it up:
{7}
nova.tests.functional.test_servers.PortResourceRequestReSchedulingTest.test_boot_reschedule_fill_provider_mapping_raises
[6.791333s] ... ok
Captured stderr:
b'Traceb
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Chan
You need to upgrade the version of tox you're using, it was a regression
in some version of tox - this isn't a nova issue.
https://tox.readthedocs.io/en/latest/changelog.html
I can't remember off hand which version but I'm using 3.8.0 and don't
have this problem.
** Changed in: nova
Statu
The affected API is deprecated now, see the reasoning in bug
https://bugs.launchpad.net/nova/+bug/1525101 but we likely won't fix
this at this point.
** Changed in: nova
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: nova
Assignee: (unassigned) => Radoslav Gerganov (rgerganov)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs
** Changed in: nova
Importance: Undecided => High
** Also affects: nova/stein
Importance: Undecided
Status: New
** Also affects: nova/rocky
Importance: Undecided
Status: New
** Changed in: nova
Importance: High => Medium
** Changed in: nova/rocky
Status: New =>
201 - 300 of 3047 matches
Mail list logo
