Command nova-status upgrade check always return warning when checking resource providers

Bug #1789535 reported by Ha Manh Dong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

Bug Description

Description
===========
Version: master
Cluster model: 1 controller and 1 compute

I used nova api database for placement service.

When I run command: "nova-status upgrade check",
the output always warning in check resource providers.

Expected result
===============
+--------------------------------+
| Check: Resource Providers |
| Result: Success |
| Details: None |
+--------------------------------+

Actual result
=============
+-------------------------------------------------------------------+
| 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. |
+-------------------------------------------------------------------+

Logs & Configs
==============
I checked in nova-compute.log that compute node was reported to placement
service with log:
"INFO nova.compute.resource_tracker [req-52b91ba5-518c-476c-ad63-a2c83a1a43c3 - - - - -]
Compute node record created for compute1:compute1 with uuid ..."

The resource_providers table in nova_api database:

MariaDB [nova_api]> select * from resource_providers;
+---------------------+---------------------+----+--------------------------------------+----------+------------+----------+------------------+--------------------+
| created_at | updated_at | id | uuid | name | generation | can_host | root_provider_id | parent_provider_id |
+---------------------+---------------------+----+--------------------------------------+----------+------------+----------+------------------+--------------------+
| 2018-08-16 07:20:33 | 2018-08-27 03:12:37 | 1 | a5ac6e98-9935-456c-9de1-10f47adb81d6 | compute1 | 7 | NULL | 1 | NULL |
+---------------------+---------------------+----+--------------------------------------+----------+------------+----------+------------------+--------------------+

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

Is the check running before or after the nova-compute service is showing up in the "nova service-list" output? You might be racing depending on when you run the upgrade check.

Is the nova.conf being used to run the nova-status upgrade check CLI configured with the [api_database]/connection set? It must be if it's pulling compute nodes out of the cell database.

Which release is this tested against?

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

> Which release is this tested against?

Oh I guess you said master.

tags: added: nova-status upgrade
Revision history for this message
Ha Manh Dong (donghm) wrote :

Hi Matt,

> Is the check running before or after the nova-compute service is showing up in the "nova service-list" output?

I tested after the nova-compute service is showing up in the "nova service-list" output and I also tested after I had created vm successfully.

> Is the nova.conf being used to run the nova-status upgrade check CLI configured with the [api_database]/connection set

Yes, the connections was added in the nova.conf

[api_database]
connection = mysql+pymysql://nova_api:hn2yBVvBFGV396urk44UEPtvbOsfpebIT5JYLq6K@192.168.122.250:3306/nova_api

> Which release is this tested against?

I also tested this in Rocky stable and have same issue, in Queens stable is ok.

Thanks.

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.