nova-status upgrade check fails with extracted placement-api

[Eduardo Gonzalez]

Currently doing extraction of placement api out of nova. Fresh deployment work fine,
however while doing an nova-status upgrade check once is up and with instances runningt he Resource Providers check fails due:

There are no compute resource providers in the Placement service but there are 1 compute nodes in the deployment. This means no compute nodes are reporting into the Placement service and need to be upgraded and/or fixed. See https://docs.openstack.org/nova/latest/user/placement.html for more details.

In an IRC chat in #openstack-placement channel, I've been told is because upgrade check command looks in the wrong database, and so is failing.

Following logs:

        "+-------------------------------------------------------------------+",
        "| Upgrade Check Results |",
        "+-------------------------------------------------------------------+",
        "| Check: Cells v2 |",
        "| Result: Success |",
        "| Details: None |",
        "+-------------------------------------------------------------------+",
        "| Check: Placement API |",
        "| Result: Success |",
        "| Details: None |",
        "+-------------------------------------------------------------------+",
        "| Check: Resource Providers |",
        "| Result: Warning |",
        "| Details: There are no compute resource providers in the Placement |",
        "| service but there are 1 compute nodes in the deployment. |",
        "| This means no compute nodes are reporting into the |",
        "| Placement service and need to be upgraded and/or fixed. |",
        "| See |",
        "| https://docs.openstack.org/nova/latest/user/placement.html |",
        "| for more details. |",
        "+-------------------------------------------------------------------+",
        "| Check: Ironic Flavor Migration |",
        "| Result: Success |",
        "| Details: None |",
        "+-------------------------------------------------------------------+",
        "| Check: API Service Version |",
        "| Result: Success |",
        "| Details: None |",
        "+-------------------------------------------------------------------+",
        "| Check: Request Spec Migration |",
        "| Result: Success |",
        "| Details: None |",
        "+-------------------------------------------------------------------+",
        "| Check: Console Auths |",
        "| Result: Success |",
        "| Details: None |",
        "+-------------------------------------------------------------------+"

Please let me know if need further information.

Regards

[Chris Dent (cdent)]

I asked Eduardo to create this so we had something to track and didn't forget about it.

This is in kolla-ansible. Placement is up, running, has resource providers in its db, but nova-api db does not. So the system works, but the status check does not.

[Matt Riedemann (mriedem)]

Hmm, grenade doesn't fail on this, but that's presumably because the status check is hitting the nova_api database from the rocky side of grenade where the resource providers are in the nova_api DB.

I did bring this up in the mailing list recently:

http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000454.html

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/626421
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=7737acdc206e590e640bd427367e1b2361f4ebd5
Submitter: Zuul
Branch: master

commit 7737acdc206e590e640bd427367e1b2361f4ebd5
Author: Matt Riedemann <email address hidden>
Date: Wed Dec 19 20:31:36 2018 -0500

    Remove "Resource Providers" upgrade check

    With placement being extracted from nova, the
    "Resource Providers" nova-status upgrade check no
    longer works as intended since the placement data
    will no longer be in the nova_api database. As a
    result the check can fail on otherwise properly
    deployed setups with placement extracted.

    This check was originally intended to ease the upgrade
    to Ocata when placement was required for nova to work,
    as can be seen from the newton/ocata/pike references
    in the code.

    Note that one could argue the check itself as a concept
    is still useful for fresh installs to make sure everything
    is deployed correctly and nova-compute is properly
    reporting into placement, but for it to be maintained
    we would have to change it to no longer rely on the
    nova_api database and instead use the placement REST API,
    which while possible, might not be worth the effort or
    maintenance cost.

    For simplicity and expediency, the check is simply removed
    in this change.

    Related mailing list discussion can be found here [1].

    [1] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000454.html

    Change-Id: I630a518d449a64160c81410245a22ed3d985fb01
    Closes-Bug: #1808956

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.