Hello, I am sure we are not using nova-compute with duplicate names. As I told previously we tried on 3 differents openstack installations and we faced the same issue. Procedure used We have an openstack with 3 compute nodes : podto1-kvm01, podto1-kvm02, podto1-kvm03 1) install a new compute node (podto1-kvm04) 2) On controller we discovered the new compute node: su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova 3) Evacuate podto1-kvm01 4) yum update on podto1-kvm01 and reboot it 5) Evacuate podto1-kvm02 6) yum update on podto1-kvm02 and reboot it 7) Evacuate podto1-kvm03 8) yum update podto1-kvm03 and reboot it
Regards Il giorno mer 17 ott 2018 alle ore 16:19 Jay Pipes <jaypi...@gmail.com> ha scritto: > On 10/17/2018 01:41 AM, Ignazio Cassano wrote: > > Hello Jay, when I add a New compute node I run nova-manage cell_v2 > > discover host . > > IS it possible this command update the old host uuid in resource table? > > No, not unless you already had a nova-compute installed on a host with > the exact same hostname... which, from looking at the output of your > SELECT from compute_nodes table, doesn't seem to be the case. > > In short, I think both Sylvain and I are stumped as to how your > placement resource_providers table ended up with these phantom records :( > > -jay >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
