Not able to boot from Volume / Volume snapshot when using isolated_images

Bug #1746483 reported by Crazik
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Matt Riedemann
Ocata
Fix Committed
Medium
Matt Riedemann
Pike
Fix Committed
Medium
Matt Riedemann
Queens
Fix Committed
Medium
Matt Riedemann

Bug Description

Description
===========

When using isolated_images, isolated_hosts and restrict_isolated_hosts_to_isolated_images=true
I'm not able to create running instance with volume/volume snapshot as a source.

Instance goes to ERROR state with reason:
Failed to compute_task_build_instances: Cannot load 'id' in the base class

Steps to reproduce
==================

1. Set below options in nova.conf:

isolated_images = <id_of_one_of_images>
isolated_hosts = <one_dedicated_compute>
restrict_isolated_hosts_to_isolated_images=true

and append filter 'IsolatedHostsFilter' to the `enabled_filters` setting.

2. Apply configs & restart nova services

Now tests:
1. Create empty volume
2. Set bootable flag
3. Launch as instance
4. Created instance is in ERROR state.

Second test:
1. Create instance from image
2. create instance snapshot
3. Go to volume snapshots
4. Create as instance
5. Created instance is in ERROR state.

Actual results
================
Not working

Expected results
==================
Working as usual

Environment
==============
Ocata @ ubuntu xenial, Ceph-backed storage

Packages & versions:
ii nova-api 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - API frontend
ii nova-common 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - common files
ii nova-conductor 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - conductor service
ii nova-consoleauth 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - Console Authenticator
ii nova-novncproxy 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - NoVNC proxy
ii nova-placement-api 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - placement API frontend
ii nova-scheduler 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute - virtual machine scheduler
ii python-nova 2:15.0.1-0ubuntu1~cloud0 all OpenStack Compute Python libraries
ii python-novaclient 2:7.1.0-0ubuntu1~cloud0 all client library for OpenStack Compute API - Python 2.7

Logs
===========

Traceback (most recent call last):#012#012 File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 155, in _process_incoming#012 res = self.dispatcher.dispatch(message)#012#012 File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 222, in dispatch#012 return self._do_dispatch(endpoint, method, ctxt, args)#012#012 File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 192, in _do_dispatch#012 result = func(ctxt, **new_args)#012#012 File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 218, in inner#012 return func(*args, **kwargs)#012#012 File "/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py", line 98, in select_destinations#012 dests = self.driver.select_destinations(ctxt, spec_obj)#012#012 File "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py", line 58, in select_destinations#012 selected_hosts = self._schedule(context, spec_obj)#012#012 File "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py", line 110, in _schedule#012 spec_obj, index=num)#012#012 File "/usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py", line 572, in get_filtered_hosts#012 hosts, spec_obj, index)#012#012 File "/usr/lib/python2.7/dist-packages/nova/filters.py", line 89, in get_filtered_objects#012 list_objs = list(objs)#012#012 File "/usr/lib/python2.7/dist-packages/nova/filters.py", line 44, in filter_all#012 if self._filter_one(obj, spec_obj):#012#012 File "/usr/lib/python2.7/dist-packages/nova/scheduler/filters/__init__.py", line 26, in _filter_one#012 return self.host_passes(obj, filter_properties)#012#012 File "/usr/lib/python2.7/dist-packages/nova/scheduler/filters/isolated_hosts_filter.py", line 60, in host_passes#012 image_ref = spec_obj.image.id if spec_obj.image else None#012#012 File "/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 67, in getter#012 self.obj_load_attr(name)#012#012 File "/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 603, in obj_load_attr#012 _("Cannot load '%s' in the base class") % attrname)#012#012NotImplementedError: Cannot load 'id' in the base class

Revision history for this message
Matt Riedemann (mriedem) wrote :

Hmm, it appears that the IsolatedHostsFilter doesn't take into account that when you boot from volume, there doesn't need to be an image provided to the server create request, and therefore the RequestSpec likely won't have an image, or at least an image with an id, since the root disk is going to have the volume which has the OS image in it.

 File "/usr/lib/python2.7/dist-packages/nova/scheduler/filters/isolated_hosts_filter.py", line 60, in host_passes#012 image_ref = spec_obj.image.id if spec_obj.image else None

Changed in nova:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Matt Riedemann (mriedem) wrote :

There are probably two ways to handle this:

1. Ignore the request in the IsolatedHostsFilter if the RequestSpec.image(.id) isn't set.

2. In the API code, if creating a server from a bootable volume, and no image id is provided, get the image id from the volume image metadata like this:

https://github.com/openstack/nova/blob/2ecb99939ec15057904d1b86c4478def29e193db/nova/compute/api.py#L2971

And then store that on the request spec. However, that might be confusing later if code assumes that an image id in the request spec means it wasn't a boot-from-volume request; although we do have utility code to tell if an instance is boot-from-volume, like here:

https://github.com/openstack/nova/blob/2ecb99939ec15057904d1b86c4478def29e193db/nova/compute/api.py#L2957

Option #2 is probably the more correct, albeit complicated, fix.

tags: added: scheduler
removed: nova
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/543257

Revision history for this message
Matt Riedemann (mriedem) wrote :

It looks like this was likely regressed in Mitaka with this change:

https://review.openstack.org/#/c/202678/

Because before that change, the logic could handle no image being supplied with the server create request:

        spec = filter_properties.get('request_spec', {})
        props = spec.get('instance_properties', {})
        image_ref = props.get('image_ref')
        image_isolated = image_ref in isolated_images

But then it was changed to this which breaks in this scenario:

        image_ref = spec_obj.image.id if spec_obj.image else None

I'm not sure what's in spec_obj.image though if it's not None or empty.

Revision history for this message
Matt Riedemann (mriedem) wrote :

In debugging a functional test that recreates the failure, I got this:

spec_obj.image: ImageMeta(checksum=<?>,container_format=<?>,created_at=<?>,direct_url=<?>,disk_format=<?>,id=<?>,min_disk=0,min_ram=0,name=<?>,owner=<?>,properties=ImageMetaProps,protected=<?>,size=1073741824,status='active',tags=<?>,updated_at=<?>,virtual_size=<?>,visibility=<?>)

It looks like the image_meta comes from this method in the compute API:

https://github.com/openstack/nova/blob/fa6c0f9cb14f1b4ce4d9b1dbacb1743173089986/nova/compute/api.py#L1028

https://github.com/openstack/nova/blob/fa6c0f9cb14f1b4ce4d9b1dbacb1743173089986/nova/utils.py#L1032

Which should be setting these values in the ImageMeta object:

https://github.com/openstack/nova/blob/fa6c0f9cb14f1b4ce4d9b1dbacb1743173089986/nova/utils.py#L88

# Image attributes which Cinder stores in volume image metadata
# as regular properties
VIM_IMAGE_ATTRIBUTES = (
    'image_id', 'image_name', 'size', 'checksum',
    'container_format', 'disk_format', 'min_ram', 'min_disk',
)

And it looks like we never actually set the image_id in the image_meta dict in there, so it doesn't get stored in the RequestSpec.image to be used by the filter.

Changed in nova:
assignee: nobody → Matt Riedemann (mriedem)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/543263

Changed in nova:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/543264

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (master)

Reviewed: https://review.openstack.org/543257
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4f9667b7a92ffef4329380e39c64cf314203b06e
Submitter: Zuul
Branch: master

commit 4f9667b7a92ffef4329380e39c64cf314203b06e
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:14:31 2018 -0500

    Add regression test for BFV+IsolatedHostsFilter failure

    Creating a volume-backed server while using the IsolatedHostsFilter
    results in a NoValidHost failure because the filter tries to load
    the RequestSpec.image.id but when you create a server from a volume,
    an image is not required directly in the server create request.

    Change-Id: Id21e0afa5cec401555bee679193c256e55be863b
    Related-Bug: #1746483

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/543263
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0a7427dc58eeb271646a962604106e0e84b870b6
Submitter: Zuul
Branch: master

commit 0a7427dc58eeb271646a962604106e0e84b870b6
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:58:02 2018 -0500

    Handle volume-backed instances in IsolatedHostsFilter

    The RequestSpec.image object for a volume-backed instance will
    not have the 'id' attribute set because the
    nova.utils.get_image_metadata_from_volume() method doesn't convert
    the volume['volume_image_metadata']['image_id'] into the ImageMeta.id
    field. It is unclear if there are intentional reasons for omitting
    this information, but the IsolatedHostsFilter has just never supported
    filtering for volume-backed instances based on a provided image id.

    The logic within the filter depends on the
    restrict_isolated_hosts_to_isolated_images config option, which
    defaults to True. When True, a volume-backed instance will not be
    put on an isolated host. When False, a volume-backed instance can
    go on any host, isolated or not.

    Again, it's unclear if we should actually be filtering volume-backed
    servers using the image_id from the volume_image_metadata or not,
    but it's not what we've historically done so this change simply
    fixes the regression bug.

    Change-Id: Ieb8abb1a3f04ce008f9617e051e4d720dbe6917a
    Closes-Bug: #1746483

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (master)

Reviewed: https://review.openstack.org/543264
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=60bbec15ed319ce703d49667b2649289639a86da
Submitter: Zuul
Branch: master

commit 60bbec15ed319ce703d49667b2649289639a86da
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 17:13:08 2018 -0500

    Fix docs for IsolatedHostsFilter

    The docs were using variable names from the filter code rather
    than the actual config options.

    Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
    Related-Bug: #1746483

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (stable/queens)

Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/543594

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/543595

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (stable/queens)

Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/543596

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (stable/pike)

Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/543602

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/543603

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (stable/pike)

Related fix proposed to branch: stable/pike
Review: https://review.openstack.org/543604

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (stable/ocata)

Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543634

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543635

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to nova (stable/ocata)

Related fix proposed to branch: stable/ocata
Review: https://review.openstack.org/543636

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (stable/queens)

Reviewed: https://review.openstack.org/543594
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ed959b94ee8a211a270d9d89a6021e76a16bf31f
Submitter: Zuul
Branch: stable/queens

commit ed959b94ee8a211a270d9d89a6021e76a16bf31f
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:14:31 2018 -0500

    Add regression test for BFV+IsolatedHostsFilter failure

    Creating a volume-backed server while using the IsolatedHostsFilter
    results in a NoValidHost failure because the filter tries to load
    the RequestSpec.image.id but when you create a server from a volume,
    an image is not required directly in the server create request.

    Change-Id: Id21e0afa5cec401555bee679193c256e55be863b
    Related-Bug: #1746483
    (cherry picked from commit 4f9667b7a92ffef4329380e39c64cf314203b06e)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/queens)

Reviewed: https://review.openstack.org/543595
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4c6443c0b5579853f4b87eb8302d24aca99dddab
Submitter: Zuul
Branch: stable/queens

commit 4c6443c0b5579853f4b87eb8302d24aca99dddab
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:58:02 2018 -0500

    Handle volume-backed instances in IsolatedHostsFilter

    The RequestSpec.image object for a volume-backed instance will
    not have the 'id' attribute set because the
    nova.utils.get_image_metadata_from_volume() method doesn't convert
    the volume['volume_image_metadata']['image_id'] into the ImageMeta.id
    field. It is unclear if there are intentional reasons for omitting
    this information, but the IsolatedHostsFilter has just never supported
    filtering for volume-backed instances based on a provided image id.

    The logic within the filter depends on the
    restrict_isolated_hosts_to_isolated_images config option, which
    defaults to True. When True, a volume-backed instance will not be
    put on an isolated host. When False, a volume-backed instance can
    go on any host, isolated or not.

    Again, it's unclear if we should actually be filtering volume-backed
    servers using the image_id from the volume_image_metadata or not,
    but it's not what we've historically done so this change simply
    fixes the regression bug.

    Change-Id: Ieb8abb1a3f04ce008f9617e051e4d720dbe6917a
    Closes-Bug: #1746483
    (cherry picked from commit 0a7427dc58eeb271646a962604106e0e84b870b6)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (stable/queens)

Reviewed: https://review.openstack.org/543596
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c1dfe464bbe2c1a5b0e306285a86c814ceff9e80
Submitter: Zuul
Branch: stable/queens

commit c1dfe464bbe2c1a5b0e306285a86c814ceff9e80
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 17:13:08 2018 -0500

    Fix docs for IsolatedHostsFilter

    The docs were using variable names from the filter code rather
    than the actual config options.

    Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
    Related-Bug: #1746483
    (cherry picked from commit 60bbec15ed319ce703d49667b2649289639a86da)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 17.0.0.0rc2

This issue was fixed in the openstack/nova 17.0.0.0rc2 release candidate.

Revision history for this message
wondra (wondra) wrote :

Hi!
Is it possible that this will also fix https://bugs.launchpad.net/nova/+bug/1655030 ?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (stable/pike)

Reviewed: https://review.openstack.org/543602
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3ff30f407c36264641ea8a1bfe8849d9e7a75f0e
Submitter: Zuul
Branch: stable/pike

commit 3ff30f407c36264641ea8a1bfe8849d9e7a75f0e
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:14:31 2018 -0500

    Add regression test for BFV+IsolatedHostsFilter failure

    Creating a volume-backed server while using the IsolatedHostsFilter
    results in a NoValidHost failure because the filter tries to load
    the RequestSpec.image.id but when you create a server from a volume,
    an image is not required directly in the server create request.

    NOTE(mriedem): The CinderFixture had to be used since the
    CinderFixtureNewAttachFlow fixture didn't exist until Queens.

    Change-Id: Id21e0afa5cec401555bee679193c256e55be863b
    Related-Bug: #1746483
    (cherry picked from commit 4f9667b7a92ffef4329380e39c64cf314203b06e)
    (cherry picked from commit ed959b94ee8a211a270d9d89a6021e76a16bf31f)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/pike)

Reviewed: https://review.openstack.org/543603
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fb723851707d6a764cb8154343087affc19e5db0
Submitter: Zuul
Branch: stable/pike

commit fb723851707d6a764cb8154343087affc19e5db0
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:58:02 2018 -0500

    Handle volume-backed instances in IsolatedHostsFilter

    The RequestSpec.image object for a volume-backed instance will
    not have the 'id' attribute set because the
    nova.utils.get_image_metadata_from_volume() method doesn't convert
    the volume['volume_image_metadata']['image_id'] into the ImageMeta.id
    field. It is unclear if there are intentional reasons for omitting
    this information, but the IsolatedHostsFilter has just never supported
    filtering for volume-backed instances based on a provided image id.

    The logic within the filter depends on the
    restrict_isolated_hosts_to_isolated_images config option, which
    defaults to True. When True, a volume-backed instance will not be
    put on an isolated host. When False, a volume-backed instance can
    go on any host, isolated or not.

    Again, it's unclear if we should actually be filtering volume-backed
    servers using the image_id from the volume_image_metadata or not,
    but it's not what we've historically done so this change simply
    fixes the regression bug.

    Change-Id: Ieb8abb1a3f04ce008f9617e051e4d720dbe6917a
    Closes-Bug: #1746483
    (cherry picked from commit 0a7427dc58eeb271646a962604106e0e84b870b6)
    (cherry picked from commit 4c6443c0b5579853f4b87eb8302d24aca99dddab)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (stable/pike)

Reviewed: https://review.openstack.org/543604
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f510e2e7f00f612ad636f4e7fcc188d64285a889
Submitter: Zuul
Branch: stable/pike

commit f510e2e7f00f612ad636f4e7fcc188d64285a889
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 17:13:08 2018 -0500

    Fix docs for IsolatedHostsFilter

    The docs were using variable names from the filter code rather
    than the actual config options.

    Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
    Related-Bug: #1746483
    (cherry picked from commit 60bbec15ed319ce703d49667b2649289639a86da)
    (cherry picked from commit c1dfe464bbe2c1a5b0e306285a86c814ceff9e80)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 16.1.1

This issue was fixed in the openstack/nova 16.1.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (stable/ocata)

Reviewed: https://review.openstack.org/543634
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3f3ccfff8e123fc35306b982cab46b55980739e5
Submitter: Zuul
Branch: stable/ocata

commit 3f3ccfff8e123fc35306b982cab46b55980739e5
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:14:31 2018 -0500

    Add regression test for BFV+IsolatedHostsFilter failure

    Creating a volume-backed server while using the IsolatedHostsFilter
    results in a NoValidHost failure because the filter tries to load
    the RequestSpec.image.id but when you create a server from a volume,
    an image is not required directly in the server create request.

    NOTE(mriedem): The CinderFixture had to be used since the
    CinderFixtureNewAttachFlow fixture didn't exist until Queens.

    NOTE(mriedem): The functional test needed to change slightly to
    disable the DiskFilter since we're using the PlacementFixture which
    takes care of DISK_GB filtering.

    Change-Id: Id21e0afa5cec401555bee679193c256e55be863b
    Related-Bug: #1746483
    (cherry picked from commit 4f9667b7a92ffef4329380e39c64cf314203b06e)
    (cherry picked from commit ed959b94ee8a211a270d9d89a6021e76a16bf31f)
    (cherry picked from commit 3ff30f407c36264641ea8a1bfe8849d9e7a75f0e)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/ocata)

Reviewed: https://review.openstack.org/543635
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=88c51bde8c47b14e2750c5eb48f9c37b3a1c2ef7
Submitter: Zuul
Branch: stable/ocata

commit 88c51bde8c47b14e2750c5eb48f9c37b3a1c2ef7
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 16:58:02 2018 -0500

    Handle volume-backed instances in IsolatedHostsFilter

    The RequestSpec.image object for a volume-backed instance will
    not have the 'id' attribute set because the
    nova.utils.get_image_metadata_from_volume() method doesn't convert
    the volume['volume_image_metadata']['image_id'] into the ImageMeta.id
    field. It is unclear if there are intentional reasons for omitting
    this information, but the IsolatedHostsFilter has just never supported
    filtering for volume-backed instances based on a provided image id.

    The logic within the filter depends on the
    restrict_isolated_hosts_to_isolated_images config option, which
    defaults to True. When True, a volume-backed instance will not be
    put on an isolated host. When False, a volume-backed instance can
    go on any host, isolated or not.

    Again, it's unclear if we should actually be filtering volume-backed
    servers using the image_id from the volume_image_metadata or not,
    but it's not what we've historically done so this change simply
    fixes the regression bug.

    Change-Id: Ieb8abb1a3f04ce008f9617e051e4d720dbe6917a
    Closes-Bug: #1746483
    (cherry picked from commit 0a7427dc58eeb271646a962604106e0e84b870b6)
    (cherry picked from commit 4c6443c0b5579853f4b87eb8302d24aca99dddab)
    (cherry picked from commit fb723851707d6a764cb8154343087affc19e5db0)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (stable/ocata)

Reviewed: https://review.openstack.org/543636
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8430cbbc972740a80a774278b4f645b193dbdfa9
Submitter: Zuul
Branch: stable/ocata

commit 8430cbbc972740a80a774278b4f645b193dbdfa9
Author: Matt Riedemann <email address hidden>
Date: Sun Feb 11 17:13:08 2018 -0500

    Fix docs for IsolatedHostsFilter

    The docs were using variable names from the filter code rather
    than the actual config options.

    Conflicts:
          doc/source/admin/configuration/schedulers.rst

    NOTE(mriedem): The schedulers configuration doc is not
    included in this backport since that doc didn't exist in
    nova until Pike via commit da224b3a0.

    Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
    Related-Bug: #1746483
    (cherry picked from commit 60bbec15ed319ce703d49667b2649289639a86da)
    (cherry picked from commit c1dfe464bbe2c1a5b0e306285a86c814ceff9e80)
    (cherry picked from commit f510e2e7f00f612ad636f4e7fcc188d64285a889)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 18.0.0.0b1

This issue was fixed in the openstack/nova 18.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 15.1.1

This issue was fixed in the openstack/nova 15.1.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.