Re: [ovirt-users] Clean up Hosted Engine entry in oVirt console

Didi: Thanks for taking the time. Let me try to provide more details. I added my comments below your questions. Many Thanks, Eric -----Original Message----- From: Yedidyah Bar David [mailto:didi@redhat.com] Sent: Wednesday, April 15, 2015 4:00 PM To: Eric Wong Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Clean up Hosted Engine entry in oVirt console ----- Original Message ----- Please give more details, it's not completely clear what you did. Let's define: oldenginemachine - the machine where you ran the engine before migration attempt Our oVirt environment is configured as followed: - 2 racks. Each rack has 10 blades with SAN storage. - the 2 racks cannot access the SAN storage of the other rack. So the X side blades can only reach X side SAN. D side blades can only see D side SAN. - Application VMs are running on both side of the rack. So in case one side of the rack completely failed, we still have the other side providing the application services. - Our oVirt management environment is also configured the same way. X side & D side has their only ovirt-engine. "ovirt-engine" is running on CentOS VMs. Ovirt-engine on each side can see the blades and VMs on both sides. hostedenginehost - the host where you tried to run hosted-engine --deploy We tried to deploy hosted-engine on one of the blades on D side. We used this doc as our guide. http://www.ovirt.org/Migrate_to_Hosted_Engine newenginemachine - the vm created by 'hosted-engine --deploy' where you were supposed to setup an engine (by migrating data from oldenginemachine) On that D side blade, we got to the end of Part One of that document in which the newenginemachine seem to be created but I can never connect to it with vnc or remote-viewer (no firewall blocking). The hosted-engine is configured to use iSCSI storage instead of NFS. Was hostedenginehost registered in oldenginemachine before? Or is it a new host? I think the installation process automatically registered the hostedenginehost in the oldenginemachine during the Part One of the setup process. It was not there before. Was the engine there down while you tried migrating? The "engine" you talked about here. Is that the new or old one? The new hostedenginehost cannot be started. The oldenginemachine still runs. When I tried to started the HostedEngine (hostedenginehost) from the ovirt console, it tells me cannot be done because it is not managed by this ovirt host. Is there a chance that it was up, and 'hosted-engine --deploy' connected to it and tried doing stuff there? Where? I ran that on the blade where I initially ran the hosted-engine --deploy You mean, in oldenginemachine? That is correct. From the GUI provided by the oldenginemachine, I can see the entry HostedEngine. Indeed. Indeed. Not sure exactly how, but first let's be sure what the problem is. Best, -- Didi