Hi
I opened a BugZilla at
https://bugzilla.redhat.com/show_bug.cgi?id=1664777 but no steps
have been shared on how to resolve. Does anyone know how this can be fixed without
destroying the data center and building a new hosted engine?
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug@med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Wed, Jan 9, 2019 at 10:22 AM Douglas Duckworth
<dod2014@med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Hi
Should I open a Bugzilla to resolve this problem?
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug@med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Wed, Dec 19, 2018 at 1:13 PM Douglas Duckworth
<dod2014@med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Hello
I am trying to migrate my hosted-engine VM to another cluster in the same data center.
Hosts in both clusters have the same logical networks and storage. Yet migrating the VM
isn't an option.
To get the hosted-engine VM on the other cluster I started the VM on host in that other
cluster using "hosted-engine --vm-start."
However HostedEngine still associated with old cluster as shown attached. So I cannot
live migrate the VM. Does anyone know how to resolve? With other VMs one can shut them
down then using the "Edit" option. Though that will not work for
HostedEngine.
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug@med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690