Nova compute addition with --limit fails to map host to cell

Bug #1869371 reported by Mark Goddard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Medium
Mark Goddard
Train
Fix Released
Medium
Mark Goddard
Ussuri
Fix Released
Medium
Mark Goddard

Bug Description

Steps to reproduce
------------------

Deploy a small cloud. Add one host to the compute group in the inventory, and scale out:

$ kolla-ansible deploy --limit <new compute host>

Expected results
----------------

Command succeeds, and compute host becomes active.

Actual results
--------------

Command succeeds, but creating an instance fails with the following:

"Host 'compute0' is not mapped to any cell"

This happens because we only discover computes on the first host in the cell's nova conductor group. If that host is not in the specified limit, the discovery will not happen.

Mark Goddard (mgoddard)
Changed in kolla-ansible:
importance: Undecided → Medium
status: New → Triaged
milestone: none → 10.0.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

Fix proposed to branch: master
Review: https://review.opendev.org/715474

Changed in kolla-ansible:
assignee: nobody → Mark Goddard (mgoddard)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.opendev.org/715474
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=3af28d2151f9e3431e81e5d23e0e2a72cea2c034
Submitter: Zuul
Branch: master

commit 3af28d2151f9e3431e81e5d23e0e2a72cea2c034
Author: Mark Goddard <email address hidden>
Date: Fri Mar 27 13:27:15 2020 +0000

    Fix nova compute addition with limit

    Deploy a small cloud. Add one host to the compute group in the
    inventory, and scale out:

    $ kolla-ansible deploy --limit <new compute host>

    The command succeeds, but creating an instance fails with the following:

        Host 'compute0' is not mapped to any cell

    This happens because we only discover computes on the first host in the
    cell's nova conductor group. If that host is not in the specified limit,
    the discovery will not happen.

    This change fixes the issue by running compute discovery when any ironic
    or virtualised compute hosts are in the play batch, and delegating it to
    a conductor.

    Change-Id: Ie984806240d147add825ffa8446ae6ff55ca4814
    Closes-Bug: #1869371

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/720518

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/train)

Reviewed: https://review.opendev.org/720518
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=5ac8d6224ba4e9f721a5f1a45fea454318afe443
Submitter: Zuul
Branch: stable/train

commit 5ac8d6224ba4e9f721a5f1a45fea454318afe443
Author: Mark Goddard <email address hidden>
Date: Fri Mar 27 13:27:15 2020 +0000

    Fix nova compute addition with limit

    Deploy a small cloud. Add one host to the compute group in the
    inventory, and scale out:

    $ kolla-ansible deploy --limit <new compute host>

    The command succeeds, but creating an instance fails with the following:

        Host 'compute0' is not mapped to any cell

    This happens because we only discover computes on the first host in the
    cell's nova conductor group. If that host is not in the specified limit,
    the discovery will not happen.

    This change fixes the issue by running compute discovery when any ironic
    or virtualised compute hosts are in the play batch, and delegating it to
    a conductor.

    Change-Id: Ie984806240d147add825ffa8446ae6ff55ca4814
    Closes-Bug: #1869371
    (cherry picked from commit 3af28d2151f9e3431e81e5d23e0e2a72cea2c034)

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

Other bug subscribers

Remote bug watches

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