[Openstack-operators] Nova hypervisor uuid

[Ignazio Cassano]

Hi  All,
Please anyone know where hypervisor uuid is retrived?
Sometime updating kmv nodes with yum update it changes and in nova database
2 uuids are assigned to the same node.
regards
Ignazio
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Nova hypervisor uuid

[Matt Riedemann]

On 11/27/2018 11:32 AM, Ignazio Cassano wrote:

Hi  All,
Please anyone know where hypervisor uuid is retrived?
Sometime updating kmv nodes with yum update it changes and in nova 
database 2 uuids are assigned to the same node.

regards
Ignazio




___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



To be clear, do you mean the computes_nodes.uuid column value in the 
cell database? Which is also used for the GET /os-hypervisors response 
'id' value if using microversion >= 2.53. If so, that is generated 
randomly* when the compute_nodes table record is created:


https://github.com/openstack/nova/blob/8545ba2af7476e0884b5e7fb90965bef92d605bc/nova/compute/resource_tracker.py#L588

https://github.com/openstack/nova/blob/8545ba2af7476e0884b5e7fb90965bef92d605bc/nova/objects/compute_node.py#L312

When you hit this problem, are you sure the hostname on the compute host 
is not changing? Because when nova-compute starts up, it should look for 
the existing compute node record by host name and node name, which for 
the libvirt driver should be the same. That lookup code is here:


https://github.com/openstack/nova/blob/8545ba2af7476e0884b5e7fb90965bef92d605bc/nova/compute/resource_tracker.py#L815

So the only way nova-compute should create a new compute_nodes table 
record for the same host is if the host/node name changes during the 
upgrade. Is the deleted value in the database the same (0) for both of 
those records?


* The exception to this is for the ironic driver which re-uses the 
ironic node uuid as of this change: https://review.openstack.org/#/c/571535/


--

Thanks,

Matt

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] IMPORTANT: We're combining the lists!

[Jeremy Stanley]

REMINDER: The openstack, openstack-dev, openstack-sigs and
openstack-operators mailing lists (to which this was sent) are being
replaced by a new openstack-disc...@lists.openstack.org mailing
list. The new list[0] has been open for posts from subscribers since
Monday November 19, and the old lists will be configured to no
longer accept posts starting on Monday December 3. In the interim,
posts to the old lists will also get copied to the new list so it's
safe to unsubscribe from them now and not miss any messages. See my
previous notice[1] for details.

As of the time of this announcement, we have 403 subscribers on
openstack-discuss with six days to go before the old lists are
closed down for good). I have updated the old list descriptions to
indicate the openstack-discuss list is preferred, and added a custom
"welcome message" with the same for anyone who subscribes to them
over the next week.

[0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
[1] 
http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators