[Yahoo-eng-team] [Bug 1675518] [NEW] cells_scheduler_filter policies checked outside nova-api

Public bug reported: cells_scheduler_filter:DifferentCellFilter and cells_scheduler_filter:TargetCellFilter policies are checked in nova scheduler not in nova-api. This bug is similar to https://bugs.launchpad.net/nova/+bug/1675486. Policies should not be checked outside nova-api. ** Affects: n

[Yahoo-eng-team] [Bug 1674486] [NEW] sync_instances in os-cells undocumented

Public bug reported: sync_instances action in os-cells API is not documented in https://developer.openstack.org/api-ref/compute/. ** Affects: nova Importance: Undecided Assignee: Sujitha (sujitha-neti) Status: New ** Tags: api-ref ** Summary changed: - sync_instances

[Yahoo-eng-team] [Bug 1659391] Re: Server list API does not show existing servers

** 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/1659391 Title: Server list API does not show existing servers Status in

[Yahoo-eng-team] [Bug 1654736] Re: VM number summarize not match.

@pratik-bandarkar, I agree with you. Also openstack usage list shows resource usage per project based on start and end date range. Both the commands have different usages. The behavior observed is expected. Marking this as invalid. ** Changed in: nova Status: New => Invalid -- You receiv

[Yahoo-eng-team] [Bug 1658415] Re: The name of _get_vm_ref_from_uuid is not consistent with its implementation

** 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/1658415 Title: The name of _get_vm_ref_from_uuid is not consistent with

[Yahoo-eng-team] [Bug 1631430] [NEW] Only one entry created for nova-osapi_compute and nova-metadata services in multi-n-api environment

Public bug reported: Description === In nova.conf, osapi_compute_listen and metadata_listen are defaulted to 0.0.0.0. Due to this when multiple n-api nodes are setup in a multinode environment, only one entry is created for nova-osapi_compute and nova-metadata services in nova.services

[Yahoo-eng-team] [Bug 1416269] Re: boot vm failed with --block-device set as attach volume failed during boot

*** This bug is a duplicate of bug 1433609 *** https://bugs.launchpad.net/bugs/1433609 This was the kilo fix: https://review.openstack.org/#/c/174060/ for bug 1433609. I'm not able to reproduce this bug on stable/kilo. I'm going to duplicate this bug against bug 1433609 - if it's not the sam

[Yahoo-eng-team] [Bug 1544720] Re: In response template processing, some values are set to u'' instead of None

I couldn't reproduce the bug. I changed the value for OS-EXT-SRV-ATTR:kernel_id from null to "test_kernel" in both server-get-resp.json.tpl and server-get-resp.json. Test fails because value in template(test_kernel) and actual response('') is different. This is expected. Also value in Response is

[Yahoo-eng-team] [Bug 1544744] [NEW] Live migration with attached volume results in ERROR state and fails to rollback when cinder client exception is thrown

Public bug reported: During live migration with attached volume, instance is moved to ERROR state and stuck in task state Migrating when cinder client exception is thrown. Steps: 1. Create a nova instance 2. Attach a cinder volume 3. Raise cinderclient exception in initialize_connection(

[Yahoo-eng-team] [Bug 1235220] Re: Nova API returns unicode Location Header

** 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/1235220 Title: Nova API returns unicode Location Header Status in