** Also affects: oslo-incubator
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/1450438
Title:
loopingcall: if a time drift
IMHO, we should be able to fail gracefully if some part of the sample
config generation fails. Barbican isn't needed by default so I don't
think we should move it into requirements. This whole thing is yet
another manifestation of having optional dependencies and how to
represent that.
**
*** This bug is a security vulnerability ***
Public security bug reported:
The ironic config option for the password and auth token are not marked
as secret so the values will get logged during startup in debug mode.
** Affects: nova
Importance: Medium
Assignee: Joe Gordon (jogo
*** This bug is a duplicate of bug 1451931 ***
https://bugs.launchpad.net/bugs/1451931
Public bug reported:
The ironic config option for the password and auth token are not marked
as secret so the values will get logged during startup in debug mode.
** Affects: nova
Importance:
*** This bug is a duplicate of bug 1451931 ***
https://bugs.launchpad.net/bugs/1451931
Public bug reported:
The ironic config option for the password and auth token are not marked
as secret so the values will get logged during startup in debug mode.
** Affects: nova
Importance:
._impl.MismatchError: '5.5.5.5-g9ec3421' !=
'2015.2.0-g9ec3421'
http://logs.openstack.org/27/169827/8/check/gate-nova-python27/2009c78/console.html
** Affects: nova
Importance: Critical
Assignee: Joe Gordon (jogo)
Status: In Progress
** Changed in: nova
Status: New
The expiration timer hasn't started for some reason.
** Changed in: neutron
Status: Incomplete = 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/1298355
Title:
Lock wait
Haven't seen this in a while, marking as invalid
** Changed in: neutron
Status: Incomplete = 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/1313800
Title:
lock wait
no, we are not seeing this.
** Changed in: neutron
Status: Incomplete = 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/1313794
Title:
lock_wait timeout caused by
released in 0.10
** Changed in: hacking
Status: Fix Committed = 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/1403270
Title:
import
** No longer affects: hacking
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1214176
Title:
Fix copyright headers to be compliant with Foundation policies
Status in OpenStack Telemetry
we are testing live migration now and dhcp is working after the
migration.
** 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).
Public bug reported:
tempest.scenario.test_shelve_instance.TestShelveInstance.test_shelve_instance
periodically failing on aiopcpu job with network errors
TRACE tempest.common.ssh error: [Errno 113] No route to host
http://logs.openstack.org/27/169827/1/check/check-tempest-dsvm-aiopcpu-
Public bug reported:
http://logs.openstack.org/18/169318/1/check/check-tempest-dsvm-aiopcpu-
full/0f015f3/logs/10.209.65.164-subnode/screen-n-cpu.txt.gz#_2015-03-31_14_41_02_677
2015-03-31 14:41:02.677 20527 WARNING nova.virt.libvirt.driver [-] [instance:
bc1bfb78-d8b0-4fad-9a6c-aa9e5c228f8c]
This has been fixed by some of the work to move nova-net to objects.
** Changed in: nova
Status: Triaged = Fix Released
** Changed in: nova
Assignee: (unassigned) = Dan Smith (danms)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Changed in: nova
Status: New = 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/1426543
Title:
Spike in DBDeadlock errors in update_floatingip_statuses since 2/27
*** This bug is a duplicate of bug 1118066 ***
https://bugs.launchpad.net/bugs/1118066
** This bug is no longer a duplicate of bug 1313935
tenant is required for quota-update but not for quota-show
** This bug has been marked a duplicate of bug 1118066
Nova should confirm quota requests
moved to Opinion based on the discussion on the abandoned patch
** Changed in: nova
Status: Triaged = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Instances in error state take up quota. This is for consistency since we
generally count error state instances against the quota and having some
count and others not count would be even more confusing.
** Changed in: nova
Status: Confirmed = Opinion
--
You received this bug notification
*** This bug is a duplicate of bug 1118066 ***
https://bugs.launchpad.net/bugs/1118066
** This bug is no longer a duplicate of bug 1313935
tenant is required for quota-update but not for quota-show
** This bug has been marked a duplicate of bug 1118066
Nova should confirm quota requests
*** This bug is a duplicate of bug 1118066 ***
https://bugs.launchpad.net/bugs/1118066
** This bug is no longer a duplicate of bug 1313935
tenant is required for quota-update but not for quota-show
** This bug has been marked a duplicate of bug 1118066
Nova should confirm quota requests
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: nova
Status: Confirmed = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This bug is fairly old and doesn't explain how to reproduce it. Marking
as invalid. If we find out how to reproduce this error lets just open a
new bug.
** Changed in: nova
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
Looks like this should be fixed in nova since the fix landed in oslo
** Changed in: nova
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Error state instances should be counted against the quotas, we don't
100% know the state of what happened so we default to safe. Also having
some error state count and some not count is even more confusing.
** Tags added: quotas
** Changed in: nova
Status: Confirmed = Opinion
--
You
This bug is invalid and is a case of a bad translation
http://paste.openstack.org/show/190502
# -*- coding: utf-8 -*-
print(good:)
print(utest %s % u'á')
print(good:)
print(test %s % 'á')
print(bad:)
print(utest %s % 'á')
** Changed in: nova
Status: Fix Committed = Invalid
--
You
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** Changed in: nova/icehouse
Status: New = In Progress
** Changed in: nova/icehouse
Importance: Undecided = Critical
** Changed in: nova
Status: In Progress = Invalid
** Changed in: nova
Importance:
auth_version is coming from keystonemiddleware not nova. So perhaps you
had an old version of keystonemiddleware installed.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
this bug doesn't make sense. Furthermore, this is actually a valid behavior
IMHO.
I don't see why a host can't be part of two AZs.
AZs are internally defined as a special metadata key/value in an aggregate
(availability_zone key in metadata).
The bug says Two host aggregates in same
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** 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).
I just ran this with 'tox -r -egenconfig ' and didn't have any issues.
** Also affects: nova/juno
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New = Incomplete
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because
This sounds like a small feature request, not an actual bug.
** Changed in: nova
Importance: Undecided = Wishlist
** 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
this may be a novaclient bug. Only seeing this failure with the new
novaclient
** Also affects: python-novaclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
** 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/bugs/1423695
Title:
gate-devstack-dsvm-cells fails attaching volume
Status
The use case is to remove the root volume of an instance while this
being powered off. A different volume will then be attached. This keeps
the whole configuration (especially MAC addresses of network ports)
while changing the software.
This isn't a use case we are trying to support, this goes
sounds like an oslo.messaging issue at this point
** Changed in: oslo.messaging
Status: Incomplete = New
** 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
** 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.
https://bugs.launchpad.net/bugs/1357055
Title:
Race to delete shared subnet in Tempest neutron full
current rootwrap:
#!/usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT:
'nova==2015.1.dev567','console_scripts','nova-rootwrap'
__requires__ = 'nova==2015.1.dev567'
import sys
from pkg_resources import load_entry_point
if __name__ == '__main__':
sys.exit(
** Also affects: keystone
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/1407592
Title:
Snapshots fail to upload larger
** 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).
https://bugs.launchpad.net/bugs/999508
Title:
DeviceIsBusy error when reattaching volume to an
*** This bug is a duplicate of bug 1292243 ***
https://bugs.launchpad.net/bugs/1292243
** This bug has been marked a duplicate of bug 1292243
deallocate_for_instance should delete all neutron ports on error
--
You received this bug notification because you are a member of Yahoo!
Having an instance disappear isn't enough to know the things were
cleaned up successfully. Instead we should sort out why the instance
disappeared, that shouldn't happen.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
** Changed in: nova
Status: Incomplete = Opinion
--
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/1022612
Title:
private instance IPs can only reach public IPs in
** 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).
https://bugs.launchpad.net/bugs/1154140
Title:
Add excutils.save_and_reraise_exception()
Status
** Changed in: nova
Assignee: lvdongbing (dbcocle) = (unassigned)
** Changed in: nova
Status: In Progress = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Changed in: nova
Status: In Progress = Opinion
--
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/1279941
Title:
Break out security group logic in
not a bug, a feature request.
** Changed in: nova
Status: In Progress = Invalid
** Changed in: nova
Assignee: warewang (wangguangcai) = (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** 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).
not seeing this cause nova breaking change in oslo.concurrency was
reverted
** 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).
Can you provide more context here, from the very little this bug says,
this sounds like something is reconfigured and not a real bug. If you
don't think this is a real bug please use ask.openstack.org.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification
It sounds like the deeper issue is how the memory stat going to 0 for
the instance, and if it went to ERROR state or not. This should never
happen. Marking this bug as invalid and we should instead open a
separate bug on how to prevent us from getting stuck in that state. If
memory goes to 0 the
** Also affects: python-novaclient
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.launchpad.net/bugs/1410949
Title:
You are setting osapi_compute_link_prefix incorrectly, why are you
setting this in the first place. Since this isn't a bug you should
use ask.openstack.org for support.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
looks like this is a novaclient issue., not a nova issue and there is a
separate novaclient bug, so closing this.
** 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
** Changed in: nova
Status: Incomplete = Opinion
--
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/1233058
Title:
remove usage of ssh when do instance resize and
Marking as invalid as this isn't reproducible on master.
** 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/bugs/1410032
Title:
This is an openstack infra bug not a nova bug. AFAIK infra is now using
storyboard for bugs: https://storyboard.openstack.org
** Changed in: nova
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Looks like a neutron error: http://logs.openstack.org/15/143315/3/check
/check-grenade-dsvm-
neutron/90ca1e9/logs/new/screen-n-api.txt.gz#_2014-12-22_10_19_30_242
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Incomplete
--
You
Unless this keeps happening I think this is related to some new versions
of dependencies and this should be resolved already.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
It sounds like there may be an issue in oslo.messaging with reconnecting
** Also affects: oslo.messaging
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
When testing out multi node devstack running tempest-full
tempest.scenario.test_shelve_instance.TestShelveInstance fails
http://logs.openstack.org/04/136504/14/experimental/check-tempest-dsvm-
aiopcpu/68b73b8/logs/testr_results.html.gz
The instance successfully goes to
Public bug reported:
As of https://review.openstack.org/#/c/140146/2 importing
nova.hacking.checks now requires eventlet
This becomes an issue if we want to run flake8 in a venv without
eventlet. We do this as part of the hacking integration test, it builds
a venv (via tox) with trunk hacking
** Changed in: nova
Status: New = Opinion
--
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/1403270
Title:
import nova.hacking.checks.factory now requires eventlet
Public bug reported:
As per bug https://bugs.launchpad.net/nova/+bug/1238910, we truncate
instance names longer then 63 characters.
When doing nova boot --min-count=5 bob, a -{UUD} is appended to the
name resulting in something like:
bob-48cf0539-3be3-43bd-b744-fd5ae2a51c1a
This name then gets
Is this still valid, this bugs is several years old.
** 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/897140
Title:
Is this still valid, hasn't been touched in years.
** Changed in: nova
Status: Confirmed = 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
** Changed in: nova
Status: Confirmed = Opinion
--
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/1167073
Title:
nova-network should increase nf_conntrack_max
$ euca-authorize -P tcp -p 0-65535 -s 0.0.0.0/0 default
euca-authorize: error (InvalidParameterValue): Invalid port range 0:65535.
Valid TCP ports should be between 1-65535
** Changed in: nova
Status: Triaged = Invalid
--
You received this bug notification because you are a member
not sure how this relates to nova anymore.
** 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/1027263
Title:
Nova
** Changed in: nova
Status: Triaged = Opinion
--
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/975212
Title:
Flavor self link not included in GET server response
** 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/1013594
Title:
Update server name with invalid server name is not
Not sure how this is a nova bug,
https://bugs.launchpad.net/nova/+bug/1401110 sounds like the bug. Now
sure how what a possible next step would be for this bug report.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Note this is the gate devstack setup.
This is neutron.conf http://logs.openstack.org/80/139880/3/check/check-
tempest-dsvm-neutron-full/1fee100/logs/etc/neutron/neutron.conf.txt.gz
so we are using the default logging_context_format_string which looks to
be:
%(asctime)s.%(msecs)03d %(process)d
Unclear if this a nova bug or a neutron bug, but its definitely a bug.
** Changed in: nova
Importance: Undecided = Medium
** Tags added: network
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
This sounds like it is a horizon bug, since you see the change in the
command line and not in horizon.
** Changed in: nova
Status: New = Invalid
** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
based on the log this may be an oslo messaging issue.
** Also affects: oslo.messaging
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).
Not enough information, and no response closing bug.
** 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).
https://bugs.launchpad.net/bugs/1340082
not seeing any hits for the query message:Current status: SHUTOFF.
Current task state: None. outside of the experimental queue so looks
like this isn't an issue anymore.
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of
we aren't seeing this test fail anymore closing the 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).
https://bugs.launchpad.net/bugs/1328276
Public bug reported:
http://logs.openstack.org/58/136158/9/check/check-tempest-dsvm-neutron-
full/abea49f/logs/screen-q-svc.txt.gz?level=TRACE
Is full of a lot of repetitive warnings, and it is unclear if something
may be going wrong or not.
** Affects: neutron
Importance: Undecided
Public bug reported:
neutron logs: [req-94a39f87-e470-4032-82af-9a6b429b60fa None]
while nova logs: [req-c0b4dfb9-8af3-40eb-b0dd-7b576cfd1d55
AggregatesAdminTestJSON-917687995 AggregatesAdminTestJSON-394398414]
Nova uses the format: #logging_context_format_string=%(asctime)s.%(msecs)03d
This doesn't sound like a nova bug per se, this may be a packaging
issue?
https://github.com/kanaka/websockify/issues/101
** 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
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** Changed in: nova/icehouse
Status: New = Confirmed
** Changed in: nova
Status: New = Incomplete
** Changed in: nova
Status: Incomplete = Invalid
--
You received this bug notification because you
Do you have more detail? How can we reproduce this bug?
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Incomplete
** Changed in: nova/icehouse
Status: New = Incomplete
--
You received this bug notification because you
It looks like this is a neutron or keystone failure of some sort. As
neutron is saying
Max retries exceeded with url: /v2.0/tokens (Caused by class
'socket.gaierror': [Errno -9] Address family for hostname not
supported) and tokens is from keystone. So I don't think this is a nova
bug. What is
https://review.openstack.org/#/c/95440/ merged
** Changed in: nova
Status: In Progress = Fix Committed
** Changed in: nova
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
this sounds like a user error and not a nova bug
** 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).
https://bugs.launchpad.net/bugs/1395236
Title:
** 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).
https://bugs.launchpad.net/bugs/985489
Title:
nova-compute stops processing compute.$HOSTNAME
** 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).
https://bugs.launchpad.net/bugs/1006878
Title:
euca-authorize adds wrong rules for group-to-group
no response, closing the bug.
** Changed in: nova
Status: Incomplete = Invalid
** Changed in: nova
Status: Invalid = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
no response in a while, assuming this isn't an issue anymore closing the
bug.
** 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).
** Changed in: nova
Status: Incomplete = Opinion
--
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/1165275
Title:
Periodic tasks should dynamically adjust the
** Changed in: nova
Status: Incomplete = 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/1254667
Title:
host state get error
Status in OpenStack
no feedback, closing
** 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).
https://bugs.launchpad.net/bugs/1262642
Title:
VMware VC driver fails to
** 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).
https://bugs.launchpad.net/bugs/1291637
Title:
memcache client race
Status in OpenStack Identity
sounds like this is neutron not nova.
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Even if this isn't a memory leak and not something easily fixable, the
behavior should at least be documented somewhere.
This may be relevent: http://effbot.org/pyfaq/why-doesnt-python-release-
the-memory-when-i-delete-a-large-object.htm
** Also affects: ceilometer
Importance: Undecided
nova is trying to execute a command and oslo.concurrency (processutils)
is trying to look for passwords to mask them in the log and raising a
Unicode error. Is there a log line before the stacktrace saying Mount
device on dir? my hunch is something about that is unicode
** Also affects:
Sounds like this is a bug upstream from nova. Closing as not sure what
we can do in nova for this.
** Changed in: nova
Status: New = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Also affects: nova/icehouse
Importance: Undecided
Status: New
** 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).
1 - 100 of 429 matches
Mail list logo
