RHEVH ends up with network interface named breth0, not rhevm
I've been attempting to get a CLEAN install of rhevm and a rhevh host and have run into a problem that seems to contradict the nice little videos:
* Red Hat Enterprise Virtualization 3.1 - Installing RHEV Manager :: https://access.redhat.com/knowledge/videos/269993 [1]
* Red Hat Enterprise Virtualization 3.1 - Installing RHEV Hypervisor :: https://access.redhat.com/knowledge/videos/270043 [2]
* Red Hat Enterprise Virtualization 3.1 - Connecting to RHEV Manager via Web Admin Portal :: https://access.redhat.com/knowledge/videos/270093 [3]
* Red Hat Enterprise Virtualization 3.1 - Approving RHEV Hypervisors :: https://access.redhat.com/knowledge/videos/270113 [4]
I install rhevh just fine and in exactly the same way as in video 2.
When I get to logging into the rhevm host (video 3), my host does not appear. When I add it manually, it seems to work and then sets the node as non-operational. When I investigate further, I can see that something different - my rhevh interface is set to breth0, not rhevm,
the management interface. If I then 'fiddle' with the rhevm gui, I can then change the interface from breth0 to rhevm. and eventually it will go green..
My questions are:
- What prevented me from adding this cleanly? What do I check? dns works, rhevm and rhevh can resolve each other and ping each other.
- What logs do look at ? engine.log? ovirt.log?
- How do you CLEANLY recover from this? I am rather tired of running rhevm-cleanup/setup and reinstalling the host every time this happens
Rick
Responses
Hi Rick,
In order to follow the flow through properly, we need to take it back to the top, i.e. find nout why the host, after you followed the videos, did not appear in the RHEV-M admin UI. There might be several different causes, but they usually pretty much add up to misconfigured networking.
RHEV-H must be able to resolve the RHEV-M via DNS (both A and PTR records) and vice versa. Besides, RHEv-H, in order to register itself with RHEV-M must be able to reach it's http and https ports.
Also make sure their time/date are in sync (this can cause serious issues with SSL if not).
So, in order to properly investigate this, I suggest you start from scratch - remove the host, wipe the disks, install a fresh RHEV-H, and follow the video through, step by step.
At the end, you should see the host in RHEV-M's UI in the "avaiting approval" status.
The 'breth' issue is not really an issue, since the proper approve/register flow renames it ro rhevm automatically
RHEV-H is basically a locked down, installable live-cd image. Installation takes a few minutes and it is usually easier to just reinstall than troubleshoot (that's the point after all).
As for local storage, RHEV tries not to blow existing storage domains away, and if it finds a UUID-like directory under the location you pointed to, it will abort, so as not to wipe another storage domain.
It might be, that your initial SD creation failed, leaving an already created directory structure behind (worth investigating why, so it won't happen again), and so when you tried to create a local SD again, the process was aborted by the safety mechanism, which is quite normal.
I would suggest you really start off with RHEV on multiple hosts and centralised storage, otherwise, lots of the features RHEV provides will remain unavailable
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
