<div dir="auto">hello Iain, it is not possible.<div dir="auto">I checked hostnames several times.</div><div dir="auto">No changes . </div><div dir="auto">I tried same procedure on 3 different ocata installations because we have 3 distinct openstack . Same results.</div><div dir="auto">Regards</div><div dir="auto">Ignazio</div></div><br><div class="gmail_quote"><div dir="ltr">Il Mar 16 Ott 2018 17:20 iain MacDonnell <<a href="mailto:iain.macdonnell@oracle.com">iain.macdonnell@oracle.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Is it possible that the hostnames of the nodes changed when you updated <br>
them? e.g. maybe they were using fully-qualified names before and <br>
changed to short-form, or vice versa ?<br>
<br>
~iain<br>
<br>
<br>
On 10/16/2018 07:22 AM, Ignazio Cassano wrote:<br>
> Hi Sylvain,<br>
> I mean launching "yum update" on compute nodes.<br>
> Now I am going to describe what happened.<br>
> We had an environment made up of 3 kvm nodes.<br>
> We added two new compute nodes.<br>
> Since the addition has been made after 3 or 4 months after the first <br>
> openstack installation, the 2 new compute nodes are updated to most <br>
> recent ocata packages.<br>
> So we launched a yum update also on the 3 old compute nodes.<br>
> After the above operations, the resource_providers table contains wrong <br>
> uuid for the 3 old nodes and they stooped to work.<br>
> Updating resource_providers uuid getting them from compute_nodes table, <br>
> the old 3 nodes return to work fine.<br>
> Regards<br>
> Ignazio<br>
> <br>
> Il giorno mar 16 ott 2018 alle ore 16:11 Sylvain Bauza <br>
> <<a href="mailto:sbauza@redhat.com" target="_blank" rel="noreferrer">sbauza@redhat.com</a> <mailto:<a href="mailto:sbauza@redhat.com" target="_blank" rel="noreferrer">sbauza@redhat.com</a>>> ha scritto:<br>
> <br>
> <br>
> <br>
> On Tue, Oct 16, 2018 at 3:28 PM Ignazio Cassano<br>
> <<a href="mailto:ignaziocassano@gmail.com" target="_blank" rel="noreferrer">ignaziocassano@gmail.com</a> <mailto:<a href="mailto:ignaziocassano@gmail.com" target="_blank" rel="noreferrer">ignaziocassano@gmail.com</a>>> wrote:<br>
> <br>
> Hi everybody,<br>
> when on my ocata installation based on centos7 I update (only<br>
> update not changing openstack version) some kvm compute nodes,<br>
> I diescovered uuid in resource_providers nova_api db table are<br>
> different from uuid in compute_nodes nova db table.<br>
> This causes several errors in nova-compute service, because it<br>
> not able to receive instances anymore.<br>
> Aligning uuid from compute_nodes solves this problem.<br>
> Could anyone tel me if it is a bug ?<br>
> <br>
> <br>
> What do you mean by "updating some compute nodes" ? In Nova, we<br>
> consider uniqueness of compute nodes by a tuple (host,<br>
> hypervisor_hostname) where host is your nova-compute service name<br>
> for this compute host, and hypervisor_hostname is in the case of<br>
> libvirt the 'hostname' reported by the libvirt API [1]<br>
> <br>
> If somehow one of the two values change, then the Nova Resource<br>
> Tracker will consider this new record as a separate compute node,<br>
> hereby creating a new compute_nodes table record, and then a new UUID.<br>
> Could you please check your compute_nodes table and see whether some<br>
> entries were recently created ?<br>
> <br>
> -Sylvain<br>
> <br>
> [1]<br>
> <a href="https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Connections-Host_Info.html" rel="noreferrer noreferrer" target="_blank">https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Connections-Host_Info.html</a><br>
> <<a href="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=" rel="noreferrer noreferrer" target="_blank">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=</a>><br>
> <br>
> Regards<br>
> Ignazio<br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank" rel="noreferrer">OpenStack-operators@lists.openstack.org</a><br>
> <mailto:<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank" rel="noreferrer">OpenStack-operators@lists.openstack.org</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
> <<a href="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=" rel="noreferrer noreferrer" target="_blank">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=</a>><br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank" rel="noreferrer">OpenStack-operators@lists.openstack.org</a><br>
> <a href="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=" rel="noreferrer noreferrer" target="_blank">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=</a><br>
> <br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank" rel="noreferrer">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote></div>