Ask Your Question
0

"nova-manage cell_v2 discover_hosts" finds non-existing nodes. [closed]

asked 2019-03-10 22:58:44 -0500

amkgi gravatar image

I updated OpenStack from Newton to Ocata and I have some problems with nova-placement. Nova finds non-existing nodes. I tried to remove these hosts from the cell su -s /bin/sh -c "nova-manage cell_v2 delete_host --cell_uuid 5eccb670-bccc-4816-bd13-806da5649d66 --host osk013(osk014)" nova, but this has no effect. They will appear again when I do a "nova-manage cell_v2 discover_hosts"

su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
Found 2 cell mappings.
Skipping cell0 since it does not contain hosts.
Getting compute nodes from cell 'cell1': 5eccb670-bccc-4816-bd13-806da5649d66
Found 20 computes in cell: 5eccb670-bccc-4816-bd13-806da5649d66
Checking host mapping for compute host 'osc006': 14c7f1e4-e74c-42c0-8cd0-3980950ea816
Checking host mapping for compute host 'osk013': e6464929-fe24-44e0-86f6-1c3d10fe7ad9 (!)
Creating host mapping for compute host 'osk013': e6464929-fe24-44e0-86f6-1c3d10fe7ad9 (!)
Checking host mapping for compute host 'osc007': 6d080284-b541-4b93-8681-4afb64b4bf2f
Checking host mapping for compute host 'osk014': 464d24c4-1baf-4d8f-a7e9-da9dbad571dc (!)
Creating host mapping for compute host 'osk014': 464d24c4-1baf-4d8f-a7e9-da9dbad571dc (!)
Checking host mapping for compute host 'osc009': 678d0dd0-9d26-43c0-b444-f5d00dacb464
Checking host mapping for compute host 'osc010': 9aef642b-7051-4b64-a711-8338906b44ce
Checking host mapping for compute host 'osc011': 073823ca-949c-46ce-aa3d-55e51007d4f4
Checking host mapping for compute host 'osc008': 9e622863-4f29-4549-8fda-788de188e705
Checking host mapping for compute host 'osc012': b2531dd4-370a-40bd-91ce-d8ca05b763f3
Checking host mapping for compute host 'osc013': 0416d93c-84e2-4d32-9f10-9b923aa2d9bb
Checking host mapping for compute host 'osc014': 4d1b2b8f-4d7a-421e-a117-fa2bd4067b63
Checking host mapping for compute host 'osc015': 1a6d2657-8ccc-4a26-be7d-1632cdd49a64
Checking host mapping for compute host 'osc016': 0e7b8492-1e5f-4e8c-aab9-92294bcf36a9
Checking host mapping for compute host 'osc017': f6fe97e6-3e1c-403c-9096-4a26f97e4844
Checking host mapping for compute host 'osc018': 55a726d6-1e9e-4229-aa0c-88bcedf1f688
Checking host mapping for compute host 'osc019': b30d9f30-cc1b-4048-b1aa-dedc1798a3c0
Checking host mapping for compute host 'osc020': 9c73f396-f811-492f-8b5a-c653d2762cb2
Checking host mapping for compute host 'osc023': bacc2922-dc2f-48e8-ab5d-33135204c047
Checking host mapping for compute host 'osc021': 2d1ccc0d-98f8-42b9-9703-8cc3e11ab50f
Checking host mapping for compute host 'osc022': cac78822-5278-4276-831b-7fd9e0e655eb

openstack compute service list
+-----+------------------+-----------+----------+---------+-------+----------------------------+
|  ID | Binary           | Host      | Zone     | Status  | State | Updated At                 |
+-----+------------------+-----------+----------+---------+-------+----------------------------+
| 104 | nova-compute     | osc006 | nova     | enabled | up    | 2019-03-11T03:42:23.000000 |
| 107 | nova-compute     | osc007 | nova     | enabled | up    | 2019-03-11T03:42:19.000000 |
| 113 | nova-compute     | osc009 | nova     | enabled | up    | 2019-03-11T03:42:22.000000 |
| 117 | nova-compute     | osc010 | nova     | enabled | up    | 2019-03-11T03:42:24.000000 |
| 120 | nova-compute     | osc011 | nova     | enabled | up    | 2019-03-11T03:42:22.000000 |
| 152 | nova-compute     | osc008 | nova     | enabled | up    | 2019-03-11T03:42:29.000000 |
| 153 | nova-consoleauth | osx001 | internal | enabled | up    | 2019-03-11T03:42:24.000000 |
| 154 | nova-conductor   | osx001 | internal | enabled | up    | 2019-03-11T03:42:27.000000 |
| 155 | nova-scheduler   | osx001 | internal | enabled | up    | 2019-03-11T03:42:27.000000 |
| 156 | nova-scheduler   | osx002 | internal | enabled | up    | 2019-03-11T03:42:26.000000 |
| 157 | nova-conductor   | osx002 | internal | enabled | up    | 2019-03-11T03:42:27.000000 |
| 158 | nova-consoleauth | osx002 | internal | enabled | up    | 2019-03-11T03:42:29.000000 |
| 159 | nova-scheduler   | osx003 | internal | enabled | up    | 2019-03-11T03:42:27.000000 |
| 160 | nova-consoleauth | osx003 | internal | enabled | up    | 2019-03-11T03:42:20.000000 |
| 161 | nova-conductor   | osx003 | internal | enabled | up    | 2019-03-11T03:42:27.000000 |
| 184 | nova-compute     | osc012 | nova     | enabled | up    | 2019-03-11T03:42:19.000000 |
| 190 | nova-compute     | osc013 | nova     | enabled | up    | 2019-03-11T03:42:21.000000 |
| 196 | nova-compute     | osc014 | nova     | enabled | up    | 2019-03-11T03:42:25.000000 |
| 199 | nova-compute     | osc015 | nova     | enabled | up    | 2019-03-11T03:42:24.000000 |
| 202 | nova-compute     | osc016 | nova     | enabled | up    | 2019-03-11T03:42:20.000000 |
| 208 | nova-compute     | osc017 | nova     | enabled | up    | 2019-03-11T03:42:23.000000 |
| 214 | nova-compute     | osc018 | nova     | enabled | up    | 2019-03-11T03:42:20.000000 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by amkgi
close date 2019-03-11 00:26:41.842702

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-03-11 00:26:32 -0500

amkgi gravatar image

I did su -s /bin/sh -c "nova-manage db archive_deleted_rows --until-complete --verbose" nova and after I didn't see more 45 nodes, I saw only 20 nodes. Next I connected to nova db and manually remove osk013/osk014 in table 'compute_nodes'. Now, I see "There are 14 compute resource providers and 18 compute nodes in the deployment". That is correct. 4 nodes I don't add "[placement]" in nova config yet.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2019-03-10 22:58:44 -0500

Seen: 12 times

Last updated: Mar 10