Open Stack

Is it possible that the hostnames of the nodes changed when you updated 
them? e.g. maybe they were using fully-qualified names before and 
changed to short-form, or vice versa ?

     ~iain


On 10/16/2018 07:22 AM, Ignazio Cassano wrote:
> Hi Sylvain,
> I mean launching "yum update" on compute nodes.
> Now I am going to describe what happened.
> We had an environment made up of 3 kvm nodes.
> We added two new compute nodes.
> Since the addition has been made after 3 or 4 months after the first 
> openstack installation, the 2 new compute nodes are updated to most 
> recent ocata packages.
> So we launched a yum update also on the 3 old compute nodes.
> After the above operations, the resource_providers table contains wrong 
> uuid for the 3 old nodes and they stooped to work.
> Updating resource_providers uuid getting them from compute_nodes table, 
> the old 3 nodes return to work fine.
> Regards
> Ignazio
> 
> Il giorno mar 16 ott 2018 alle ore 16:11 Sylvain Bauza 
> <sbauza at redhat.com <mailto:sbauza at redhat.com>> ha scritto:
> 
> 
> 
>     On Tue, Oct 16, 2018 at 3:28 PM Ignazio Cassano
>     <ignaziocassano at gmail.com <mailto:ignaziocassano at gmail.com>> wrote:
> 
>         Hi everybody,
>         when on my ocata installation based on centos7 I update (only
>         update not  changing openstack version) some kvm compute nodes,
>         I diescovered uuid in resource_providers nova_api db table are
>         different from uuid in compute_nodes nova db table.
>         This causes several errors in nova-compute service, because it
>         not able to receive instances anymore.
>         Aligning uuid from compute_nodes solves this problem.
>         Could anyone tel me if it is a bug ?
> 
> 
>     What do you mean by "updating some compute nodes" ? In Nova, we
>     consider uniqueness of compute nodes by a tuple (host,
>     hypervisor_hostname) where host is your nova-compute service name
>     for this compute host, and hypervisor_hostname is in the case of
>     libvirt the 'hostname' reported by the libvirt API [1]
> 
>     If somehow one of the two values change, then the Nova Resource
>     Tracker will consider this new record as a separate compute node,
>     hereby creating a new compute_nodes table record, and then a new UUID.
>     Could you please check your compute_nodes table and see whether some
>     entries were recently created ?
> 
>     -Sylvain
> 
>     [1]
>     https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Connections-Host_Info.html
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__libvirt.org_docs_libvirt-2Dappdev-2Dguide-2Dpython_en-2DUS_html_libvirt-5Fapplication-5Fdevelopment-5Fguide-5Fusing-5Fpython-2DConnections-2DHost-5FInfo.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs&m=_TK1Um7U6rr6DWfsEbv4Rlnc21v6RU0YDRepaIogZrI&s=-qYx_DDcBW_aiXp2tLBcR4pN0VZ9ZNclcx5LfIVor_E&e=>
> 
>         Regards
>         Ignazio
>         _______________________________________________
>         OpenStack-operators mailing list
>         OpenStack-operators at lists.openstack.org
>         <mailto:OpenStack-operators at lists.openstack.org>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>         <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs&m=_TK1Um7U6rr6DWfsEbv4Rlnc21v6RU0YDRepaIogZrI&s=COsaMeTCgWBDl9EQVZB_AGikvKqCIaWcA5RY7IcLYgw&e=>
> 
> 
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs&m=_TK1Um7U6rr6DWfsEbv4Rlnc21v6RU0YDRepaIogZrI&s=COsaMeTCgWBDl9EQVZB_AGikvKqCIaWcA5RY7IcLYgw&e=
>