Actually, it's not affecting Keystone -- or at least, it's not related
to Keystone itself -- but rather is a problem in Swift's
requirements.txt that is being installed in the check-grenade-dsvm jobs
in any of the integrated release projects.
** Also affects: keystone
Importance: Undecided
Public bug reported:
The nova.servicegroup.API.leave() method is not used by anything. It
should be removed.
** Affects: nova
Importance: Low
Assignee: Jay Pipes (jaypipes)
Status: In Progress
** Tags: low-hanging-fruit servicegroup-api
--
You received this bug
e):
pass
def wait(self):
pass
The rest of the drivers just return None, so this is not necessary.
** Affects: nova
Importance: Low
Assignee: Jay Pipes (jaypipes)
Status: In Progress
** Tags: low-hanging-fruit servicegroup-api
--
You received this bug notificatio
Public bug reported:
The current UNIT tests for the Zookeeper servicegroup API driver are
never run in any of the gates, since it would require installation of a
number of Python libraries, one of which would require C headers
(zkpython).
When I tried to follow the instructions on the Zookeeper d
in its is_up() method, there's actually no way the
Zookeeper driver was working correctly, since if ServiceGroupUnavailable
was raised from is_up(), things would go haywire in many places.
** Affects: nova
Importance: Low
Assignee: Jay Pipes (jaypipes)
Status: In Pro
up the unit tests to get rid of
the stubbed out image service code, I uncovered this.
** Affects: nova
Importance: Undecided
Assignee: Jay Pipes (jaypipes)
Status: New
** Tags: low-hanging-fruit
** Changed in: nova
Assignee: (unassigned) => Jay Pipes (jaypipes)
--
You
** Changed in: nova
Status: In Progress => Invalid
** Changed in: openstack-manuals
Status: New => Confirmed
--
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/1
Related bugs are marked Invalid. Patch is abandoned, so marking this
Invalid. David, please reset the status to something else if you
disagree. Thanks!
-jay
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Enginee
** Changed in: nova
Status: In Progress => 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/1069917
Title:
Setting InnoDB for tables breaks mysqlcluster/n
Marking Invalid per discussion on abandoned patch.
** Changed in: nova
Status: In Progress => 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/1301689
Title:
Public bug reported:
Currently, the resource tracker lazily-creates the compute node record
in the database (via a call to the conductor's compute_node_create() API
call) during calls to update_available_resource():
```
@utils.synchronized(COMPUTE_RESOURCE_SEMAPHORE)
def update_available_
Public bug reported:
AFAICT, there's no good reason to have a foreign key relation between
compute_nodes and services. In fact, I see no reason why compute_nodes
needs to have a service_id column at all.
The service is the representation of the message bus between the nova-
conductor and the nova
Public bug reported:
Unit tests should not need to start services. Instead, they should
simply mock out the specific calls out of the unit of code that is being
tested.
nova.tests.network.test_manager.AllocateTestCase calls
self.start_service() for the conductor, network, and compute service,
and
Public bug reported:
jpipes@uberbox:~/repos/openstack/neutron$ git log --oneline | head -1
84aeb9a Merge "Imported Translations from Transifex"
Running tox -eALL resulted in:
i18n runtests: commands[0] | python ./tools/check_i18n.py ./neutron
./tools/i18n_cfg.py
Traceback (most recent call last
Public bug reported:
Noticed the following warning when running unit tests:
SAWarning: The IN-predicate on "cisco_n1kv_profile_bindings.profile_id" was
invoked with an empty sequence. This results in a contradiction, which
nonetheless can be expensive to evaluate. Consider alternative strategi
Public bug reported:
When restarting neutron-plugin-openvswitch-agent, the plugin goes
through a series of initialization calls, many of which call out to ovs-
vsctl to set up things like the integration bridge, tun bridge and all
the flows.
I've seen this __init__() process take upwards of 2 hou
in
import pyudev
ImportError: No module named pyudev
The solution is to add pyudev to requirements.txt.
** Affects: neutron
Importance: Undecided
Assignee: Jay Pipes (jaypipes)
Status: In Progress
** Summary changed:
- pyudev missing from requirements.txt, used in a unit te
Public bug reported:
If a new model does not contain an "extra" column of type JsonBlob, unit
tests fail.
The reason is because keystone.common.sql.core.DictBase's from_dict()
classmethod looks like this:
@classmethod
def from_dict(cls, d):
new_d = d.copy()
new_d['extra'
ignee: Jay Pipes (jaypipes)
Status: Confirmed
** Changed in: keystone
Assignee: (unassigned) => Jay Pipes (jaypipes)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/127245
r the base class or
# the set of metric names returned to ensure only a single CPU
# monitor is loaded at any one time.
We need a mechanism to load other types of compute monitors than CPU.
** Affects: nova
Importance: Low
Assignee: Jay Pipes (jaypipes)
Statu
Public bug reported:
In no way should a disabled service be considered "up". I checked the
code and indeed, there is no test for whether the service record from
the DB is disabled or not:
http://git.openstack.org/cgit/openstack/nova/tree/nova/servicegroup/drivers/db.py#n68
The DB driver's get_al
I agree that it is valid to have a disabled host be operationally up
(and vice versa). Marking as Invalid. Chris, I'll try to get to a review
of your proposal this week.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yah
Public bug reported:
Glance's v2 Images resource has a "visibility" attribute that can be
"private", "public", and "shared":
http://git.openstack.org/cgit/openstack/glance/tree/glance/api/v2/images.py?id=93b0d5fce3a41e4a3a549f98f78b6681cbc3ea95#n579
However, the schema definition for the visibil
to a serialized versioned object
** Affects: nova
Importance: Low
Assignee: Jay Pipes (jaypipes)
Status: Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.n
#x27;
'compute metrics.'),
]
Since stevedore's ExtensionManager loads extensions via standard Python
setuptools entry_points.
** Affects: nova
Importance: Wishlist
Assignee: Jay Pipes (jaypipes)
Status: Triaged
** Tags: low-hanging-frui
Public bug reported:
In nova.image.glance:
def get_remote_image_service(context, image_href):
"""Create an image_service and parse the id from the given image_href.
The image_href param can be an href of the form
'http://example.com:9292/v1/images/b8b2c6f7-7345-4e2f-afa2-eedaba9cbbe3
Public bug reported:
Here is the GlanceClientWrapper.call method from nova.image.glance:
try:
return getattr(client.images, method)(*args, **kwargs)
except retry_excs as e:
host = self.host
port = self.port
ex
Public bug reported:
For some reason, nova.volume.cinder.API derives from nova.db.base.Base,
which looks like this (in its entirety):
class Base(object):
"""DB driver is injected in the init method."""
def __init__(self, db_driver=None):
super(Base, self).__init__()
if no
Public bug reported:
This bug was spurred by a conversation resulting from questions arising
from https://review.openstack.org/#/c/80741/:
http://paste.openstack.org/show/73678/
There are a number of places in Nova where a submodule depends on an
external library, but that external library is no
tance: Undecided
Assignee: Jay Pipes (jaypipes)
Status: New
** Tags: glance low-hanging-fruit
** Changed in: nova
Assignee: (unassigned) => Jay Pipes (jaypipes)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to O
Public bug reported:
There do not seem to be actual unit tests for the
nova.virt.firewall.IptablesFirewallDriver class.
There are tests for the various subclassing drivers, but there doesn't
seem to be unit tests for the base class itself, including the important
prepare_instance_filter() method
Public bug reported:
Performance improvement is possible by caching the values from the
global CONF object that are repeatedly access, including
CONF.scheduler_default_filters and CONF.scheduler_default_filters (see
patch here:
https://review.openstack.org/#/c/85594/3/nova/scheduler/host_manager.p
Public bug reported:
An abbreviated version of the
nova.compute.resource_tracker.update_available_resources() call:
def update_available_resource(self, context):
resources = self.driver.get_available_resource(self.nodename)
...
self._report_hypervisor_resource_view(resources)
Public bug reported:
jaypipes@cranky:~/repos/openstack/nova$ ack-grep load_image_handlers
--ignore-dir tests
nova/virt/imagehandler/__init__.py
70:def load_image_handlers(driver):
jaypipes@cranky:~/repos/openstack/nova$ ack-grep handle_image --ignore-dir tests
nova/virt/imagehandler/__init__.py
Public bug reported:
from nova/objects/network_request.py:
class NetworkRequest(obj_base.NovaObject):
# Version 1.0: Initial version
# Version 1.1: Added pci_request_id
VERSION = '1.0'
VERSION should be 1.1, per the comment above it.
** Affects: nova
Importance: Medium
Public bug reported:
Here is our ResourceTracker._update_usage_from_migration() code:
def _update_usage_from_migrations(self, context, resources,
migrations):
self.tracked_migrations.clear()
filtered = {}
# do some defensive filtering against bad migrations records
This worked:
jaypipes: change the first line in your config
"keys=root,keystone,combined" to just "keys=keystone"
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
ht
Dolph's solution actually didn't work...
root@c5r3.iad1 01:03:49:~# exec su -s /bin/sh -c "exec keystone-all" keystone
Traceback (most recent call last):
File "/usr/bin/keystone-all", line 83, in
config.setup_logging(CONF)
File "/usr/lib/python2.7/dist-packages/keystone/config.py", line 4
What DID work was to keep the root logger in the keys then set
logger_root section's handler to devel which uses StreamHandler instead
of File...
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Thanks for the assistance, guys. Changing the internalURL to match the
publicURL did the trick.
** Changed in: horizon/folsom
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
Was due to having admin port in internalURL. Might I say that Keystone's
adminURL and internalURL is stupid and confusing...
** Changed in: horizon/folsom
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subs
Public bug reported:
Turns out that the fix for https://bugs.launchpad.net/nova/+bug/1666831
accidentally broke boot-from-volume setups that use NFS. In particular,
this line:
https://github.com/openstack/nova/blob/stable/ocata/nova/virt/libvirt/driver.py#L1149
if os.path.exists(inst_bas
This is by design. Non-sharing providers that have all the resources
needed in the request are used as-is and there is no attempt to create
permutations of *some* the non-sharing provider's resources with those
of a sharing provider.
If you had, though, a second resource provider that only had VCP
me/jaypipes/src/git.openstack.org/openstack/nova/nova/virt/images.py", line
87, in qemu_img_info'
b'raise exception.InvalidDiskInfo(reason=msg)'
b'nova.exception.InvalidDiskInfo: Disk info file is invalid: qemu-img
failed to execute on /fake/path : Unexpected er
Public bug reported:
Something I noticed while reviewing
https://review.openstack.org/#/c/546675/14/osc_placement/resources/resource_provider.py
is that the code that prevents parent providers from being deleted:
https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/objects/r
max_unit is intended, as @edleafe states, to limit requested amount of
resources to a sane amount. It is there to provide protection against
consuming an amount of resources that would represent an unrealistic
request when the allocation_ratio > 1.0.
For example, consider the default CPU allocatio
Public bug reported:
There are a few places in the resource_provider.py placement API handler
module that need to be updated to return custom error codes.
Custom error codes were added in the last few months or so. They allow
the caller to determine what exact issue occurred on the server to, for
W_PROJECT_ID,
"user_id": $NEW_USER_ID
}
```
The $NEW_PROJECT_ID and $NEW_USER_ID values are merely ignored.
** Affects: nova
Importance: Medium
Assignee: Jay Pipes (jaypipes)
Status: Triaged
** Tags: placement
--
You received this bug notification because you are
up the auto-created consumer record if a
failure occurs when creating allocations for a *new* consumer.
** Affects: nova
Importance: Medium
Assignee: Jay Pipes (jaypipes)
Status: Triaged
** Tags: placement
--
You received this bug notification because you are a member of
Public bug reported:
When an allocation is POST'd or PUT'd and the set of allocations for a
consumer is deleted (indicated with an empty dict for the allocations),
then the consumer should be automatically deleted.
** Affects: nova
Importance: Low
Status: Triaged
** Tags: api plac
We'll be deleting consumers that have no allocations, so this bug is no
longer relevant.
** Changed in: nova
Status: In Progress => Won't Fix
** Changed in: nova
Assignee: Jay Pipes (jaypipes) => (unassigned)
--
You received this bug notification because you are a
bjects and if so, don't call
_delete_allocations_for_consumer(). Instead, call
_delete_allocations_by_id() and do a DELETE FROM allocations WHERE id IN
(...).
** Affects: nova
Importance: High
Assignee: Jay Pipes (jaypipes)
Status: Triaged
** Tags: placement
--
You re
This should be closed out now that auto-created consumers are deleted
and consumers with no allocations are auto-deleted.
** Changed in: nova
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenS
Public bug reported:
I can no longer run tox -efast8 on my local workstation. I've rm -rf
.tox/fast8 and tried from scratch twice. Continue to get the same error:
```
Collecting zVMCloudConnector===1.2.1 (from -c
https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt
tests ran successfully. marking as Fix Released.
** Changed in: nova
Status: Incomplete => 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/1782851
Titl
Public bug reported:
This is a small feature request.
Currently (version 1.3 or before of the placement API), in order to
delete all inventory for a resource provider, one must call PUT
/resource_providers/{uuid}/inventories and pass in the following request
payload:
{
'generation': ,
'resou
Public bug reported:
When attempting to perform a GET /allocation_candidates request for only
resources that are shared, a KeyError is produced:
http://paste.openstack.org/show/615753/
The problem is that the _get_usages_by_provider_and_rc() method returns
a dict with only the sharing resource p
OK, so this is indeed invalid. We do a server-side retry on creating
allocations already:
https://github.com/openstack/nova/blob/8ca24bf1ff80f39b14726aca22b5cf52603ea5a0/nova/objects/resource_provider.py#L1757-L1759
which is called from AllocationList.create_all():
https://github.com/openstack/n
** 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/1681658
Title:
disk_allocation_ratio does not work with placement API
ers to the PUT /allocations call that
the conductor makes.
Therefore, we should add the generation field to the request payload of
PUT /allocations
** Affects: nova
Importance: Medium
Assignee: Jay Pipes (jaypipes)
Status: Triaged
** Tags: placement
--
You receive
Turns out we don't actually need this... the set_allocations() call
ensures that inventory capacity is never exceeded.
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
You need to set CONF.reserved_host_memory_mb to the amount of memory
used by "other VMs not tracked by Nova". In the case of XenServer, the
dom0 counts for a VM not tracked by Nova.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a
The fix for this was merged in Newton. Marking as Fix Released.
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1456073
Title
I've seen no evidence of this occurring within the last 30 days at
least. Setting to Invalid. Feel free to re-open if you see this
happening again in the future.
** Changed in: nova
Assignee: Eli Qiao (taget-9) => (unassigned)
** Changed in: nova
Status: Confirmed => Invalid
--
You
Going to set this to Fix Released since the patch is in both Newton and
Mitaka.
** Changed in: nova
Status: Confirmed => Fix Released
** Changed in: oslo.vmware
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering T
As someone on one of the reviews commented, you can do a `nova reboot
--hard` to reboot a VM that is in ERROR state after a failed nova-
compute restart.
Closing this as Invalid.
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 1512880 ***
https://bugs.launchpad.net/bugs/1512880
The original poster's version of Nova was 13.1.2, which is Mitaka.
Therefore all the --force stuff and microversions discussion is
irrelevant (since microversion 2.29 was added in Newton).
So, the bug here
Public bug reported:
When running unit tests with tox, os-vif logging pollutes the output of
the testr runner and on multi-core machines, nearly always corrupts the
output stream like so:
http://paste.openstack.org/show/562213/
os-vif logging setup should be examined to ensure it is being proces
Public bug reported:
I'm seeing one of these per testr process in the functional test output:
Captured stderr:
/home/jaypipes/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters t
Public bug reported:
Running the Nova functional tests locally, I consistently get around a
dozen or so of these in the output:
Captured stderr:
Traceback (most recent call last):
File
"/home/jaypipes/src/git.openstack.org/openstack/nova/.tox/functional/local/lib/pytho
Seems there's an issue logged on BitBucket:
https://bitbucket.org/ianb/pastedeploy/issues/20/loadwsgi-should-
account-for-entrypointload
I'd submit a pull request to fix this crap but BitBucket won't let me
sign in with my Google account properly...
-jay
** Changed in: nova
Status: Confi
Public bug reported:
The nova.compute.claims.Claim object is used to test whether a set of
requested resources can be satisfied by the compute node. In the
constructor of the Claim object, the Claim._claim_test() object is
called:
def __init__(self, context, instance, tracker, resources, ove
Public bug reported:
You see a bunch of the following in Nova's test runs:
Captured stderr:
/home/jaypipes/repos/nova/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py:254:
OsloDBDeprecationWarning: EngineFacade is deprecated; please use
oslo_d
Public bug reported:
Nova test logs are full of the following:
Captured stderr:
/home/jaypipes/repos/nova/.tox/py27/local/lib/python2.7/site-packages/oslo_versionedobjects/fields.py:325:
FutureWarning: fake-instance is an invalid UUID. Using UUIDFields with invalid
UUIDs i
Public bug reported:
Nova test runs output a bunch of warnings about
keystoneclient.adapter.Adapter:
Captured stderr:
/home/jaypipes/repos/nova/.tox/py27/local/lib/python2.7/site-packages/keystoneclient/adapter.py:57:
DeprecationWarning: keystoneclient.adapter.Adapter is de
75 matches
Mail list logo
