> On Tue, Aug 4, 2020 at 7:37 PM
> This is good, you should not use export domain at this point. We have better
> replacement (see my other mail).
>
I agree that one way should be enough, but it needs to work and ideally improve
on usability generation on generation.
>
> I think you already
On Tue, Aug 4, 2020 at 7:37 PM wrote:
>
> Nir, first of all, thanks a lot for the detailed description and the quick
> fix in 4.4!
>
> I guess I'll be able to paste that single line fix into the 4.3. variant
> myself, but I'd rather see that included in the next 4.3 release, too: How
> would
HI Gianluca,
I have had a look at the change and it's a single line of code added on the
hosted-engine. I'll verify that it's working 4.3 and will make a note of
checking it with engine upgrade, which for now seems the less troublesome
approach.
Hopefully it will get integrated/backported
Dear Nir,
I am sorry if that sounded too harsh. I do appreciate what you are doing!
The thing is, that my only chances at getting my employer to go with the
commercial variant depend a lot on the upstream project showing already
demonstratable usability in the research lab.
Just try to
Nir, first of all, thanks a lot for the detailed description and the quick fix
in 4.4!
I guess I'll be able to paste that single line fix into the 4.3. variant
myself, but I'd rather see that included in the next 4.3 release, too: How
would that work?
---
"OVA is not a backup solution":
From
On Sat, Aug 1, 2020 at 11:48 AM wrote:
> I confirm, I get "qemu-img: /dev/loop0: error while converting qcow2:
> Could not open device: Permission denied", too.
>
> You've nailed it and Nir has pasted your log into the bug report 1862115.
>
>
It seems that actually the problem happens only the
On Thu, Jul 30, 2020 at 5:10 PM wrote:
>
> Export/Import/Transfer via export domain worked just fine. Just moved my last
> surviving Univention domain controller from the single node HCI
> disaster-recovery farm to the three node HCI primary, where I can now try to
> make it primary and start
Keep in mind that oVirt relies on OS components like qemu and if they do
fail it is not oVirt's fault.
Also, OVA export/import is not the most popular approach for backup/restore
in Virtualization Environments, so this bug should not be a reason to 'drop it
like a hot potato' .
Unfortunately that means OVA export/import doesn't seem to be a QA test case
for oVirt releases... which would make me want to drop it like a hot potato, if
there was any alternative at this point.
I guess my biggest mistake was to assume that oVirt was like CentOS.
I confirm, I get "qemu-img: /dev/loop0: error while converting qcow2: Could not
open device: Permission denied", too.
You've nailed it and Nir has pasted your log into the bug report 1862115.
___
Users mailing list -- users@ovirt.org
To unsubscribe
On Sat, Aug 1, 2020 at 12:36 AM wrote:
> Wow, it seems a good find for a potential reason!
>
Yes, but did you check the files at the path I gave you?
>
> Did you get a chance to test the OVA export/import cycle?
>
>
Right now.
Environment with oVirt 4.3.10. I have a CentOS 8 VM with a 20Gb
Wow, it seems a good find for a potential reason!
I'd totally subscribe to the cause, if it only affected my Atom HCI clusters,
who have had timing issues so bad, even the initial 3 node HCI setup had to be
run on a 5 GHz Kaby Lake to succeed, because my J5005 Atoms evidently were too
slow.
On Thu, Jul 30, 2020 at 4:04 PM wrote:
> Here is the ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1862115
>
>
could it be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1813028
?
It seems only verified as a status.
Can you check /var/log/ovirt-engine/ova/ (on engine I presume) if
Export/Import/Transfer via export domain worked just fine. Just moved my last
surviving Univention domain controller from the single node HCI
disaster-recovery farm to the three node HCI primary, where I can now try to
make it primary and start building new backups...
Backups that do not work
Here is the ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1862115
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
Bongiorno Gianluca,
I am entering the data in bugzilla right now...
Logs: There is a problem, I have not found any log evidence of this export and
import, I don't even know which component is actually doing this.
For 'foreign' imports like VMware and other *.vmdk producing hypervisors, VDSM
On Thu, Jul 30, 2020 at 2:37 PM wrote:
> I've tested this now in three distinct farms with CentOS7.8 and the latest
> oVirt 4.3 release: OVA export files only contain an XML header and then
> lots of zeros where the disk images should be.
>
> Where an 'ls -l .ova' shows a file about the size of
17 matches
Mail list logo
