search for: sdk4

...requirements. After fixing the first issue I found that jansson-devel is also missing. Should'nt we add these packages to the build requirements? Next issues - trying to test upload to ovirt, I found that these packages should be installed: nbdkit nbdkit-plugin-python3 python3-ovirt-engine-sdk4 Should we document these requirements in the rhv-upload-plugin? Nir

...dnf copr enable nsoffer/ovirt-imageio-preview -# dnf install ovirt-imageio-client +# Install ovirt-release package: +# +# dnf install http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm +# +# Install required packages: +# +# dnf install ovirt-imageio-client python3-ovirt-engine-sdk4 +# +# Note: python3-ovirt-engine-sdk4 is not available yet for Fedora 31 and 32. # # To upload or download images, you need to start an image transfer. The # easiest way is using oVirt image_transfer.py example: @@ -33,7 +41,7 @@ # # To upload an image run: # -# qemu-img convert -n -f raw -...

...88af e8e0 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 So far, so normal. This works fine under 2.6.32-220.23.1.el6.x86_64 Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active raid5 sdj3[2] sdi2[1] sdk4[3] sdh1[0] 5860537344 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] However, I just patched to CentOS 6.3 and on reboot this array failed to be built. The 2.6.32-279 kernel complained that /dev/sdj was too similar to /dev/sdj3. But I reboot to -220.23.1 then it works. And, indeed,...

...# Install ovirt-imageio-client +# +# dnf copr enable nsoffer/ovirt-imageio-preview +# dnf install ovirt-imageio-client +# +# To upload or download images, you need to start an image transfer. The +# easiest way is using oVirt image_transfer.py example: +# +# /usr/share/doc/python3-ovirt-enigne-sdk4/eamples/image_transfer.py \ +# --engine-url https://my.engine \ +# --username admin@internal \ +# --password-file password \ +# --cafile my.engine.pem \ +# upload disk-uuid +# +# This will print the trasnfer URL for this image transfer. +# +# Run this example from the build...

...t-imageio-preview > +# dnf install ovirt-imageio-client Even after running these steps,... > +# > +# To upload or download images, you need to start an image transfer. The > +# easiest way is using oVirt image_transfer.py example: > +# > +# /usr/share/doc/python3-ovirt-enigne-sdk4/eamples/image_transfer.py \ ...I do not have a /usr/share/doc/python3-ovirt-* directory at all. Where am I supposed to get it from? Also, I suspect you want s/enigne/engine/; s/eamples/examples/ > +# --engine-url https://my.engine \ > +# --username admin@internal \ > +#...

On Thu, Jan 26, 2023 at 2:31 PM Richard W.M. Jones <rjones at redhat.com> wrote: > > Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1986386 > Reported-by: Junqin Zhou > --- > output/rhv-upload-precheck.py | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/output/rhv-upload-precheck.py b/output/rhv-upload-precheck.py > index

...gt; +# dnf copr enable nsoffer/ovirt-imageio-preview > +# dnf install ovirt-imageio-client > +# > +# To upload or download images, you need to start an image transfer. The > +# easiest way is using oVirt image_transfer.py example: > +# > +# /usr/share/doc/python3-ovirt-enigne-sdk4/eamples/image_transfer.py \ > +# --engine-url https://my.engine \ > +# --username admin@internal \ > +# --password-file password \ > +# --cafile my.engine.pem \ > +# upload disk-uuid > +# > +# This will print the trasnfer URL for this image transfer. &g...