[ovirt-users] I broke my ovirt real good....

[Michael Mortensen (MCMR)]

Hi Stack,

Do you use FQDN? Did you perhaps hit this one https://www.ovirt.org/blog/2016/05/modify-ifcfg-files/ ? The discussion in this bug report may be of assistance in that case: https://bugzilla.redhat.com/show_bug.cgi?id=1252534

If you've stored the VM disks and templates and whatnot on a network share like NFS, you should be able to start all over and import your old (current) storage domains and start using your templates etc.


Best wishes
// Mike


-----Original Message-----
From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On Behalf Of ~Stack~
Sent: 13. april 2018 00:26
To: users <users at ovirt.org>
Subject: [ovirt-users] I broke my ovirt real good....

Greetings,

So I did a over-confident-admin-makes-rookie-mistake. I changed a bunch of things all back-to-back and thus don't actually know what broke. :-D

The only two real "big" changes were:
* Upgrade from 4.2.1 to 4.2.2
* change my ovirtmgmt network

The update I followed the upgrade procedures and I thought it all went pretty well. Because I am moving it from a testing into what I hope will be a more heavily used environment, I changed my ovirtmgmt network from
192.168.100.0/24 to 192.168.101.0/24 via the web-gui.

That was a touch tricker than just a change as I had to poke the management engine host to be reachable on both network for a while, then it just seemed OK.

What's happening is:
* I can no longer migrate a vm from one host to the other.
* If I try to do a "reinstall" it dies.
* There is some serious network lag between my hosts on a 10Gb network.
* I've got all kinds of python2.4 failures in my vdsm and mom logs.

Those are least the biggies.

So while I was planning on moving this to a more active use case, right now - it is all still my play ground. I would REALLY hate to lose the VM's but everything else can go and be rebuilt.

Given that I've somehow really broke this system pretty good, would it be more advisable to blow away and rebuild it ALL or can I simply delete the hypervisor hosts and rebuild them?

Thoughts?

Thanks!
~Stack~