Hi,
I’m not sure if my thread before is correctly received by everyone when posted
via the website...therefore again via email.
Sorry if now everyone received this twice...
---
We are running our ovirt 4.3 test infrastructure on 4 Centos hosts. Our
self-hosted engine further manages
Ok. The oVirt Node installation sets up partitions to use the entire
disk. (Documentation recommends using the default layout.) The Cockpit
HE deployment tries to use gluster, but on a different disk
(non-existent). Do you recommend that I not use the default
partitioning when installing
Mike,
Keep it simple. It has to be a bare, plain disk.
Do not format or put a file system on the disk or the gluster install will fail.
On Jun 25 2019, at 3:53 pm, Mike Davis wrote:
> I installed oVirt node for oVirt v4.3.4 on a single server (default
> partitioning). I know a single node is
I installed oVirt node for oVirt v4.3.4 on a single server (default
partitioning). I know a single node is not best practice, but fits our
current need.
Now, I am trying to deploy the hosted engine, but getting the error
"Device /dev/sdb not found" (full output below). /dev/sdb does not
I have at least one of those VMs with DISKTYPE=1 on my old oVirt farm. Am
pretty sure nobody ever touched metadata files outside of oVirt, but the
disks were not created by oVirt but rather produced by virt-v2v and then
imported into older version of oVirt.
That happened several years ago and I
On Tue, Jun 25, 2019 at 8:39 PM Dmitry Filonov
wrote:
> Sorry, don't have any logs from back then. That was some time ago and it
> was easy to fix so I didn't bother keeping logs.
> DISKTYPE and DESCRIPTION were the only two lines I had to fix to get disks
> imported nicely.
> If you like I can
Sorry, don't have any logs from back then. That was some time ago and it
was easy to fix so I didn't bother keeping logs.
DISKTYPE and DESCRIPTION were the only two lines I had to fix to get disks
imported nicely.
If you like I can probably re-create situation by creating a VM, then
unregistering
Il 25/06/2019 14:26, Stefano Danzi ha scritto:
I don't remember to ever seen a question about this during
engine-setup,
but it could be.
In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
[root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
Hi Strahil
Sorry for the late reply but google sent ovirt mails to spam. I have tried
and thought I get audio, it sounds like its played at an incorrect bitrate
(I recorded audio ant soundls like slow motion audio).
Is there any other way to present the usb device than throught console usb
Hi Benny,
What is the rpm package with ovirt-imageio? I checked oVirt 4.3
repositories, did not find rpm with that command.
Thanks
Jonkery
On 6/24/2019 9:48 AM, Benny Zlotnik wrote:
yes, you can use ovirt-imageio[1]
[1] -
On Tue, Jun 25, 2019 at 3:15 PM Dmitry Filonov
wrote:
> Hi Nir -
>
> in my case these VMs were migrated from VirtualBox to oVirt using some of
> the VMWare provided tool
> and then virt-v2v to convert images. Here's the example of the meta file -
>
> DOMAIN=92be9db3-eab4-47ed-9ee9-87b8616b7c8c
I don't remember to ever seen a question about this during engine-setup,
but it could be.
In /etc/pki/vdsm/certs/ I can see an old cert and ca with subjet:
[root@ovirt01 ~]# su - vdsm -s /bin/bash -c 'openssl x509 -in
/etc/pki/vdsm/certs/cacert.pem.20150205093608 -text'
Certificate:
Hi Nir -
in my case these VMs were migrated from VirtualBox to oVirt using some of
the VMWare provided tool
and then virt-v2v to convert images. Here's the example of the meta file -
DOMAIN=92be9db3-eab4-47ed-9ee9-87b8616b7c8c
VOLTYPE=LEAF
CTIME=1529005629
MTIME=1529005629
So, it's better to configure an ISO Domain, for now.
Thanks
José
De: "Gianluca Cecchi"
Para: supo...@logicworks.pt
Cc: "Strahil Nikolov" , "users"
Enviadas: Terça-feira, 25 De Junho de 2019 11:27:39
Assunto: Re: [ovirt-users] Re: iso files
On Tue, Jun 25, 2019 at 11:01 AM <
On Tue, Jun 25, 2019 at 11:01 AM wrote:
> The bug only refers version 4.2. The problem remains on version 4.3?
>
> José
>
>
> Yes, detected in 4.2 but still remains.
You can see now inside bugzilla:
Target Milestone: ovirt-4.3.6
[snip]
>
> Just remind this:
>
On Tue, Jun 25, 2019 at 9:40 AM wrote:
> That's interesting.
>
> Where can i find meta for block storage?
>
In block storage metadata is kept in the "metadata" logical volume.
To find metadata for particular volume, you need to to look at the logical
volume tags:
lvs -o tags vg-name/lv-name
On Mon, Jun 24, 2019 at 7:47 PM Dmitry Filonov
wrote:
>
> Take a look at the corresponding .meta file for the disks you can not
> import.
> I had the very same problem and it was caused by
> DISKTYPE=1 in .meta.
>
I want more info on this. We think that the only value ever used for
DISKTYPE is
On Tue, Jun 25, 2019 at 12:28 PM Stefano Danzi wrote:
>
>
>
> Il 25/06/2019 10:08, Yedidyah Bar David ha scritto:
> > On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi wrote:
> >>
> >>
> >> Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
> >>> On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi
Il 25/06/2019 10:08, Yedidyah Bar David ha scritto:
On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi wrote:
Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
I've found that this issue is related to:
Hi!
We have installed our test infrastructure on 4 Centos hosts. Our self-hosted
engine further manages serveral stand alone hosts as separate datacenters.
We'd like now to reinstall the whole thing in a best practice way with oVirt
node and a fresh hosted engine.
We have planned to:
- set
The bug only refers version 4.2. The problem remains on version 4.3?
José
De: "Gianluca Cecchi"
Para: "Strahil Nikolov"
Cc: "users" , supo...@logicworks.pt
Enviadas: Terça-feira, 25 De Junho de 2019 7:41:27
Assunto: Re: [ovirt-users] Re: iso files
On Mon, Jun 24, 2019 at 9:26 PM
http://norton-setup-usa.com
___
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:
On Tue, Jun 25, 2019 at 10:26 AM Stefano Danzi wrote:
>
>
>
> Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
> > On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
> >> I've found that this issue is related to:
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1648190
> > Are you
Il 25/06/2019 08:27, Yedidyah Bar David ha scritto:
On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
I've found that this issue is related to:
https://bugzilla.redhat.com/show_bug.cgi?id=1648190
Are you sure?
That bug is about an old cert, generated by an old version, likely
before we
Sorry for the delay.
vdsm logs are huge, i'll cut when i moved storage domains and attach the logs.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
On Mon, Jun 24, 2019 at 9:26 PM Strahil Nikolov
wrote:
> Iso domains are deprecated. You can upload an ISO to a data domain via UI
> (and maybe API).
>
> Best Regards,
> Strahil Nikolov
>
> В понеделник, 24 юни 2019 г., 16:33:57 ч. Гринуич+3, <
> supo...@logicworks.pt> написа:
>
>
> Hi,
>
> is
That's interesting.
Where can i find meta for block storage?
On NFS storage these files are located next to the disk image.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
Before detaching storages i've checked that all disks on these storages. After
detaching in the old datacenter there were left empty storage domains with only
disk of hosted-engine. Rechecked this today.
___
Users mailing list -- users@ovirt.org
To
On Mon, Jun 24, 2019 at 7:56 PM Stefano Danzi wrote:
>
> I've found that this issue is related to:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1648190
Are you sure?
That bug is about an old cert, generated by an old version, likely
before we fixed bug 1210486 (even though it's not mentioned
29 matches
Mail list logo
