Ok I have tried reinstalling the server from scratch with a different name and IP address and when trying to add it to cluster I get the following error:

Event details

ID: 505

Time: Jun 10, 2019, 10:00:00 AM

Message: Host myshost2.virt.iad3p installation failed. Host myhost2.mydomain.com reports unique id which already registered for myhost1.mydomain.com

I am at a loss here, I don't have a brand new server to do this and in need to re-use what I have.

From the oVirt engine log (/var/log/ovirt-engine/engine.log):

2019-06-10 10:57:59,950-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-37744) [9b88055] EVENT_ID: VDS_INSTALL_FAILED(505), Host myhost2.mydomain.com installation failed. Host myhost2.mydomain.com reports unique id which already registered for myhost1.mydomain.com

So in the /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20190610105759-myhost2.mydomain.com-9b88055.log of the ovirt engine I see that the host deploy is running  the following command to identify the system, if this is the case then it will never work :( because it identifies each host using the system uuid.

dmidecode -s system-uuid
b64d566e-055d-44d4-83a2-d3b83f25412e

Any suggestions?

Thanks

On Sat, Jun 8, 2019 at 11:23 AM Adrian Quintero <adrianquintero@gmail.com> wrote:

Leo,

I did try putting it under maintenance and checking to ignore gluster and it did not work.

Error while executing action: 

-Cannot remove host. Server having gluster volume.

Note: the server was already reinstalled so gluster will never see the volumes or bricks for this server.

I will rename the server to myhost2.mydomain.com and try to replace the bricks hopefully that might work, however it would be good to know that you can re-install from scratch an existing cluster server and put it back to the cluster.

Still doing research hopefully we can find a way.

thanks again

Adrian

On Fri, Jun 7, 2019 at 2:39 AM Leo David <leoalex@gmail.com> wrote:

You will need to remove the storage role from that server first ( not being part of gluster cluster ).

I cannot test this right now on production,  but maybe putting host although its already died under "mantainance" while checking to ignore guster warning will let you remove it.

Maybe I am wrong about the procedure,  can anybody input an advice helping with this situation ?

Cheers,

Leo

On Thu, Jun 6, 2019 at 9:45 PM Adrian Quintero <adrianquintero@gmail.com> wrote:

I tried removing the bad host but running into the following issue , any idea?