date:20170919

Re: [ovirt-users] Change CD Issue

2017-09-19 Thread Anantha Raghava


Hi,

You pointed out right. It is a specif issue with our second host 
(Host-2). For all VMs running on First Host (Host-1), Change CD works 
fine. It throws error for all VMs running on Second Host (Host-2). It 
has no relation with Host being SPM.


Looks like some issue with our second host (Host-2) specifically.

We migrated one VM from Second Host to First Host and Change CD works 
properly.


But how do we check what the error is? How do we fix it?

--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.

On 20/09/17 7:52 AM, Anantha Raghava wrote:


Hi,

Please find the full details about setup.

Engine is on a different machine with 
"centos-release-7-4.1708.el7.centos.x86_64" OS and kernel is "Linux 
3.10.0-693.2.2.el7.x86_64".


There are two nodes and both are with "oVirt Node 4.1.4" OS and kernel 
is "Linux 3.10.0-514.26.2.el7.x86_64".


We just upgraded the Engine and not nodes. This problem surfaced.

One peculiar behaviour observed : On a host that is marked as "SPM", 
change CD works perfectly. But throws the error on the other. This was 
not a case in the past.


--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.

On 20/09/17 12:19 AM, Eduardo Mayoral wrote:


I upgraded the ovirt-engine to 4.1.6 yesterday. The compute nodes are 
plain CentOS 7.3 and are still in 4.1.4


Tried to reproduce your problem, Change CD works fine for me .

So this looks like something specific to your setup rather than a 
generic issue with 4.1.6


Can you provide some more information about your setup?

Eduardo Mayoral Jimeno (emayo...@arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
On 19/09/17 13:11, Anantha Raghava wrote:


Hi,

We just updated our engine to 4.1.6.2. However when we attempt to 
change the CD using the UI, it is throwing the error  - "Error while 
executing action Change CD : Drive Image file could not be found." 
The image iso file very exists in the ISO Domain and has permission 
vdsm:kvm. Yet, it fails to recognise the iso image file.


This was not the case with version 4.1.3.

Can you please guide us to fix this error?

--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users






___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Change CD Issue

2017-09-19 Thread Anantha Raghava


Hi,

Please find the full details about setup.

Engine is on a different machine with 
"centos-release-7-4.1708.el7.centos.x86_64" OS and kernel is "Linux 
3.10.0-693.2.2.el7.x86_64".


There are two nodes and both are with "oVirt Node 4.1.4" OS and kernel 
is "Linux 3.10.0-514.26.2.el7.x86_64".


We just upgraded the Engine and not nodes. This problem surfaced.

One peculiar behaviour observed : On a host that is marked as "SPM", 
change CD works perfectly. But throws the error on the other. This was 
not a case in the past.


--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.

On 20/09/17 12:19 AM, Eduardo Mayoral wrote:


I upgraded the ovirt-engine to 4.1.6 yesterday. The compute nodes are 
plain CentOS 7.3 and are still in 4.1.4


Tried to reproduce your problem, Change CD works fine for me .

So this looks like something specific to your setup rather than a 
generic issue with 4.1.6


Can you provide some more information about your setup?

Eduardo Mayoral Jimeno (emayo...@arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
On 19/09/17 13:11, Anantha Raghava wrote:


Hi,

We just updated our engine to 4.1.6.2. However when we attempt to 
change the CD using the UI, it is throwing the error  - "Error while 
executing action Change CD : Drive Image file could not be found." 
The image iso file very exists in the ISO Domain and has permission 
vdsm:kvm. Yet, it fails to recognise the iso image file.


This was not the case with version 4.1.3.

Can you please guide us to fix this error?

--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Engine migration and host import

2017-09-19 Thread Ben Bradley

Hi All

I've been running a single-host ovirt setup for several months, having
previously used a basic QEMU/KVM for a few years in lab environments.

I currently have the ovirt engine running at the bare-metal level, with
the box also acting as the single host. I am also running this with
local storage.

I now have an extra host I can use and would like to migrate to a hosted
engine. The following documentation appears to be perfect and pretty
clear about the steps involved:
https://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/
and
https://www.ovirt.org/documentation/self-hosted/chap-Migrating_from_Bare_Metal_to_an_EL-Based_Self-Hosted_Environment

However I'd like to try and get a bit more of an understanding of the
process that happens behind the scenes during the cut-over from one
engine to a new/hosted engine.

As an experiment I attempted the following:
- created a new VM within my current environment (bare-metal engine)
- creating an engine-backup
- stopped the bare-metal engine
- restored the backup into the new VM
- ran engine-setup within the new VM
The new engine started up ok and I was able to connect and login to the
web UI. However my host was "unresponsive" and I was unable to manage it
in any way from the VM. I shut the VM down and started the bare-metal
ovirt-engine again on the host and everything worked as before. I didn't
try very hard to make it work however.

The magic missing from the basic process I tried is the synchronising
and importing of the existing host, which is what the hosted-engine
utility does.

Can anyone describe that process in a bit more detail?
Is it possible to perform any part of that process manually?

I'm planning to expand my lab and dev environments so for me it's
important to discover the following...
- That I'm able to reverse the process back to bare-metal engine if I
ever need/want to
- That I can setup a new VM or host with nothing more than an
engine-backup but still be able to regain control of exiting hosts and
VMs within the cluster

My main concern after my basic attempt at a "restore/migration" above is
that I might not be able to re-import/sync an existing host after I have
restored engine from a backup.

I have been able to export VMs to storage, remove them from ovirt,
re-install engine and restore, then import VMs from the export domain.
That all worked fine. But it involved shutting down all VMs and removing
their definitions from the environment.

Are there any pre-requisites to being able to re-import an existing
running host (and VMs), such as placing ALL hosts into maintenance mode
and shutting down any VMs first?

40 matches

Mail list logo