Hello Dipak,
i didn't used export domains, but directly data domain, which avoided
me the long time of copying and importing back before powering on.
Luca
On Tue, Feb 19, 2019 at 8:59 AM Dipak D. Chaudhari wrote:
>
>
> Thanks
>
> Migrated in same way.
>
> 1] Created new nfs export domain on
Hi all!
The following error occurs during installation oVirt Node 4.2.8:
EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during
installation of Host hostname_ovirt_node2: Yum Cannot queue package dmidecode:
Cannot retrieve metalink for repository: ovirt-4.2-epel/x86_64.
Good Day
I have been trying to upgrade a clients oVirt from 3.6 to 4.0 but have run
into an issue where I am unable to change the cluster and data center
compatibility version.
I get the following error in the GUI:
Ovirt: Some of the hosts still use legacy protocol which is not supported
by
After upgrading from 4.2 -> 4.3 I cannot start a vm anymore.
I try to start the vm with run once on a specific node (ovirt-node04)
and this is the output of /var/log/vdsm/vdsm.log
2019-02-19 12:08:33,626+0100 INFO (jsonrpc/6) [api.host] START
getAllVmStats() from=:::129.132.17.194,33924
I am not sure if the message reached the list so I will write it again.
On Wed, Feb 13, 2019 at 2:37 AM wrote:
> Thank you for your help!
>
> Please note:
>
> - eno1 is a 1Gb connection and was the one used when oVirt was installed.
> It is currently the only interface actually connected to
Hi Jonathan,
Did you try first to change the compatibility of all clusters and then
change the data center's compatibility?
This once seems related: https://bugzilla.redhat.com/show_bug.cgi?id=1375567
*Regards,*
*Shani Leviim*
On Tue, Feb 19, 2019 at 11:01 AM Jonathan Mathews
wrote:
> Good
On Tue, Feb 19, 2019 at 3:30 PM adam...@adagene.com.cn
wrote:
>
> Thank you. Your answer solved my problems.
> After I installed the big rpm and reboot. there are two repo files remains
> in /etc/yum.repos.d/
> ovirt-4.2-dependencies.repo
> ovirt-4.2.repo
> maybe I should remove the 2 files
Hi,
In order to delete all jobs (aka tasks on the UI), I'm using:
truncate table job cascade;
Which is also mentioned here:
https://github.com/oVirt/ovirt-engine/blob/master/packaging/setup/dbutils/taskcleaner.sh
Hope it helps
*Regards,*
*Shani Leviim*
On Mon, Feb 18, 2019 at 3:52 PM Mike
On Mon, Feb 18, 2019 at 9:41 PM Brian Wilson wrote:
>
> It looked to continue to add them if looking at something like output from
> "ip link".
>
> I was not however able to save the networks so the host always had "Unsaved
> Network Changes".
>
> I eventually needed to use the host and
Thank you Simone,
that worked.
On 19.02.19 12:40, Simone Tiraboschi wrote:
On Tue, Feb 19, 2019 at 12:18 PM Moritz Baumann
mailto:moritz.baum...@inf.ethz.ch>> wrote:
After upgrading from 4.2 -> 4.3 I cannot start a vm anymore.
I try to start the vm with run once on a specific
On Mon, Feb 18, 2019 at 9:19 AM Lucie Leistnerova wrote:
>
> 1. Ensure the correct repositories are enabled. You can check which
> repositories are currently enabled by running yum repolist.
>
> You can do it like this:
>
> # yum install
Hi,
Currently choosing VDO at volume setup forces creation of a thick LV due to
a RHEL bug, cf :
https://bugzilla.redhat.com/show_bug.cgi?id=1634551
https://bugzilla.redhat.com/show_bug.cgi?id=1600156
The latter was closed while pointing to the following workaround :
Il giorno mar 19 feb 2019 alle ore 09:23 ha scritto:
> Hi all!
>
> The following error occurs during installation oVirt Node 4.2.8:
>
> EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred
> during installation of Host hostname_ovirt_node2: Yum Cannot queue package
> dmidecode:
On Tue, Feb 19, 2019 at 12:18 PM Moritz Baumann
wrote:
> After upgrading from 4.2 -> 4.3 I cannot start a vm anymore.
>
> I try to start the vm with run once on a specific node (ovirt-node04)
> and this is the output of /var/log/vdsm/vdsm.log
>
> VolumeDoesNotExist: Volume does not exist:
>
So, If I have 3 HHD per server from 500GB each, how do you complile Size(GB)
and Logical Size(GB)? (Target: 1st HDD ovirt node, 2nd vmstore + engine, 3rd
data)
I think to do this configuration:
http://oi68.tinypic.com/33xwlj4.jpg
http://oi64.tinypic.com/2gt58gz.jpg
On the engine and vmstore
Thank you. Your answer solved my problems.
After I installed the big rpm and reboot. there are two repo files remains
in /etc/yum.repos.d/
ovirt-4.2-dependencies.repo
ovirt-4.2.repo
maybe I should remove the 2 files to avoid any conflicts?
yours Adam
From: Juhani Rautiainen
Hi,
Can you please share engine and UI logs?
Also, can you please attach a screenshot?
*Regards,*
*Shani Leviim*
On Tue, Feb 19, 2019 at 1:54 AM wrote:
> I just updated my ovirt to the latest, and now I can't upload images that
> I used to be able to. I can upload and see the nagio xi
Download ISO 4.2.8 node
Install.
I tried to add a host to oVirt,and receive this error.
He did not make any changes after install.
rpm -qa | grep dmidecode
python-dmidecode-3.12.2-3.el7.x86_64
dmidecode-3.1-2.el7.x86_64
___
Users mailing list --
Also, can you please share the output of 'ls -l' executed on the image
you're trying to upload?
*Regards,*
*Shani Leviim*
On Tue, Feb 19, 2019 at 3:52 PM Shani Leviim wrote:
> Hi,
> Can you please share engine and UI logs?
> Also, can you please attach a screenshot?
>
>
> *Regards,*
>
>
Hi Shani
Yes, I did try and change the cluster compatibility first, and that's when
I got the error: Ovirt: Some of the hosts still use legacy protocol which
is not supported by cluster 3.6 or higher. In order to change it a host
needs to be put to maintenance and edited in advanced options
Hi,
You could get all the source codes relevant to oVirt from Gerrit [1] and
Github [2].
[1]: https://gerrit.ovirt.org
[2]: https://github.com/oVirt
On Wed, Feb 20, 2019 at 3:02 PM wrote:
> Hi,The dear.
> May I ask where I can find the source code of ovirt project? I want to
> test the
Current version my oVirt 4.2.6.
Maybe I need to update it?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
Hi,The dear.
May I ask where I can find the source code of ovirt project? I want to test the
environment through compilation and installation. At present, most of the
methods are online installation, so I cannot modify some contents.
Thank you very much for your help. Thank you very much.
pki/ovirt-engine/private/ca.pem -new -x509 -days
> 3650 -sha256 -extensions v3_ca -out newca.cert.pem
> 3) Put the new CA cert in place
> mv ca.pem ca.pem.orig.20190219;mv newca.cert.pem ca.pem
> 4) Resign all the other certs
> names="engine apache websocket-pr
On Wed, Feb 20, 2019 at 1:01 AM wrote:
> qemu-img info:
> LM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk
> image: LoadMaster-VLM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk
> file format: raw
> virtual size: 16G (17179869696 bytes)
> disk size: 16G
>
This is raw image, so it may work, but
ls -l:
>
Hi, Juhani. I followed the steps below:
1. yum remove ovirt-release42
2. yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
3. yum update ovirt-node-ng-image-update
4. reboot
5. yum update
and the ovirt-4.2.repo comes back after I reboot the node host.
yours Adam
I tried adding a 400 gig disk to a VM. I could see the disk being built out on
the storage, mounted via nfs, but clearly something is stuck. A few hours later
and I see nothing finishing. Nothing seems to be logging to the engine.log and
I have restarted vdsmd on all the hosts and have
Apologies, did not see a previous post from Julie
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, did not see a previous post from Julie
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, did not see a previous post from Julie
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, did not see a previous post
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, just saw the answer on a previous post in this same thread
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
the same private key:
openssl req -key /etc/pki/ovirt-engine/private/ca.pem -new -x509 -days
3650 -sha256 -extensions v3_ca -out newca.cert.pem
3) Put the new CA cert in place
mv ca.pem ca.pem.orig.20190219;mv newca.cert.pem ca.pem
4) Resign all the other certs
names="e
I am having the same issue from CLI and trying to use existing gluster storage
(server1:/gluster_bricks/engine).
Error:
[ INFO ] TASK [Add glusterfs storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Failed
to fetch Gluster Volume List]". HTTP response code
On Tue, Feb 19, 2019 at 11:29 PM Michael Blanchard
wrote:
> I don't even get the that point. I try to upload to he Kemp Roadmaster
> vm in .disk format and it says not in proper format and errors out. No log
> entries anuwhere
>
What is "Kemp Roadmaster vm in .disk format"?
Can you run this
qemu-img info:
LM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk
image: LoadMaster-VLM-7.2.45.0.17004.RELEASE-Linux-KVM-XEN.disk
file format: raw
virtual size: 16G (17179869696 bytes)
disk size: 16G
ls -l:
-rwxrwxrwx 1 michael michael 17179869185 Jan 7 16:43
Hello all,
I have a few nodes with local storage, and I've considered exporting
them via NFS to migrate into shared storage, more than a few times.
I have thought of this post on the ovirt-users list many times:
https://lists.ovirt.org/pipermail/users/2017-December/085521.html
Is this
37 matches
Mail list logo
