- Devel - oVirt List Archives

ovirt-guest-agent_master_build-artifacts-fc28-x86_64 Fails to Build
by Anton Marchukov 31 Aug '18

31 Aug '18

Hello All. Looks like ovirt-guest-agent_master_build-artifacts-fc28-x86_64 nolonger works, as I see it fails to build with the following error: *10:53:41* 0009:fixme:module:find_dll_file skipping L"C:\\windows\\system32\\dbghelp.dll" because of wrong architecture*10:53:42* 004a:err:msiexec:custom_action_server Failed to create custom action server pipe: 2 than it fails to recognize that and the whole job fails on a time out: *16:41:14* Build timed out (after 360 minutes). Marking the build as failed. As a result, OST for guest-agent also fails. I tried to rerun the job and got the same problem. The failing job is at [1] and I also opened JIRA issue [2] to track it. [1] http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc28-… [2] https://ovirt-jira.atlassian.net/browse/OVIRT-2466 -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

3 2

s390x (mainframe) CI node is currently not available
by Barak Korren 30 Aug '18

30 Aug '18

Hi all, Unfortunately, the s390x build host we've been using had gone off-line a couple of days ago, and the ETA for having it back up is unknown. The implication of having the host down is that projects that build on s390x have their builds be stuck forever waiting for the s390x node to become available. Sine the s390x builds are missing, builds for other platforms, while being successful do not get passed to the change queue and as a result are not being released to the nightly repos. As a work around for the current situation, we need to disable the s390x builds. Here is a patch that does this for vdsm: https://gerrit.ovirt.org/c/93316/ For V2 projects the change should be done in the projects own repo, for example here is how we did it for the CI jobs of the 'jenkins' repo itself: https://gerrit.ovirt.org/c/93288/ -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 1

Failing Build On vdsm_master_check-patch
by Shani Leviim 29 Aug '18

29 Aug '18

Hello All, I got into the following failure during the CI build for a patch I did: 14:33:56 ====================================================================== 14:33:56 FAIL: test_sourceroute_add_remove_and_read (network.sourceroute_test.TestSourceRoute) 14:33:56 ---------------------------------------------------------------------- 14:33:56 Traceback (most recent call last): 14:33:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/tests/testValidation.py", line 193, in wrapper 14:33:56 return f(*args, **kwargs) 14:33:56 File "/home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/tests/network/sourceroute_test.py", line 80, in test_sourceroute_add_remove_and_read 14:33:56 self.assertEqual(2, len(routes), routes) 14:33:56 AssertionError: 2 != 0 My patch is [1] and its build is [2] [1] https://gerrit.ovirt.org/#/c/92416/ [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/747/ Can you please assist? Thanks! *Regards,* *Shani Leviim*

3 4

OST compatibility check failing on backup snapshot removal
by Milan Zamazal 29 Aug '18

29 Aug '18

Hi, when basic-suite-master OST is run with cluster level < 4.2, verify_backup_snapshot_removed test fails. Indeed, the snapshot removal fails, with error such as: [c784a2c3-a700-41f7-80bd-2d1e25a712c5] Failed to live merge. Top volume 15b82854-c9dd-44aa-83c9-aebe273ac6a4 is still in qemu chain [15b82854-c9dd-44aa-83c9-aebe273ac6a4, 3c21269c-e71b-4e96-977e-a9168bbba9bf] See e.g. https://jenkins.ovirt.org/job/ovirt-system-tests_compat-3.6-suite-master/52… Does anybody have an idea what might be wrong? Thanks, Milan

3 6

Re: Image Transfer mechanism queries/API support
by Ranjit DSouza 28 Aug '18

28 Aug '18

Hello oVirt Development team Not sure you got a chance to see this email, resending it. Thanks Ranjit From: Ranjit DSouza Sent: Monday, July 9, 2018 1:16 PM To: 'Nir Soffer' <nsoffer(a)redhat.com> Cc: devel <devel(a)ovirt.org>; DL-VTAS-ENG-NBU-EverestFalcons <DL-VTAS-ENG-NBU-EverestFalcons(a)veritas.com>; Navin Tah <Navin.Tah(a)veritas.com>; Sudhakar Paulzagade <Sudhakar.Paulzagade(a)veritas.com>; Pavan Chavva; Yaniv Lavi (Dary) <ylavi(a)redhat.com>; Nisan, Tal <tnisan(a)redhat.com>; Daniel Erez <derez(a)redhat.com> Subject: RE: [EXTERNAL] Re: [ovirt-devel] Image Transfer mechanism queries/API support Hi Nir Thanks for getting back! We have few follow up questions: 1. On the new ‘Allocated extents API’: Can you share the release timeline for 4.2.z? From the link below it seems like it will be available on 7/30/2018. https://www.ovirt.org/develop/release-management/releases/4.2.z/release-man… However, we thought we would double check on this. 2. If this will be available in 4.2.z, does It mean, we can assume it will be backported to 4.3 also? 3. When we downloaded the snapshot disk using Image Transfer API, the resulting format of the disk is “raw”. However, for upload, we must upload a qcow2 disk (to enable further snapshots). It means, we need to convert it first using qemu-img convert. Or is there a way we directly ask via API for a qcow2 instead? Portion of the response of “GET /storagedomains/{storagedomain:id}/disksnapshots” "format" : "raw", "shareable" : "false", "sparse" : "true", "status" : "ok", "snapshot" : { "id" : "4756036e-92aa-4ebb-ae4b-052a30cd5109" }, "actual_size" : "1345228800", "content_type" : "data", "propagate_errors" : "false", "provisioned_size" : "21474836480", "storage_type" : "image", "total_size" : "0", "wipe_after_delete" : "false", 4. When downloading a snapshot in chunks, Is there any recommended chunk size? For our study we used 512 KB. Checked the documentation too. 5. Regarding your ask on ‘Can you file RFE for this, explaining the use case and the current performance’. Since you do not recommend direct access to NFS storage, we will consider it only if we see significant performance degradation using http download. Also, if time permits, we may check if there is a significant performance benefit using Unix socket, over http download (via Rest API). But as it stands now, getting the allocated extents support (soon), will alleviate most of our performance concerns. Thanks Ranjit From: Nir Soffer [mailto:nsoffer@redhat.com] Sent: Tuesday, July 3, 2018 4:29 PM To: Ranjit DSouza <Ranjit.DSouza(a)veritas.com<mailto:Ranjit.DSouza@veritas.com>> Cc: devel <devel(a)ovirt.org<mailto:devel@ovirt.org>>; DL-VTAS-ENG-NBU-EverestFalcons <DL-VTAS-ENG-NBU-EverestFalcons(a)veritas.com<mailto:DL-VTAS-ENG-NBU-EverestFalcons@veritas.com>>; Navin Tah <Navin.Tah(a)veritas.com<mailto:Navin.Tah@veritas.com>>; Sudhakar Paulzagade <Sudhakar.Paulzagade(a)veritas.com<mailto:Sudhakar.Paulzagade@veritas.com>>; Pavan Chavva; Yaniv Lavi (Dary) <ylavi(a)redhat.com<mailto:ylavi@redhat.com>>; Nisan, Tal <tnisan(a)redhat.com<mailto:tnisan@redhat.com>>; Daniel Erez <derez(a)redhat.com<mailto:derez@redhat.com>> Subject: [EXTERNAL] Re: [ovirt-devel] Image Transfer mechanism queries/API support On Tue, Jul 3, 2018 at 11:32 AM Ranjit DSouza <Ranjit.DSouza(a)veritas.com<mailto:Ranjit.DSouza@veritas.com>> wrote: ... We had a conversation with Pavan Chavva for supporting RHV. He had suggested to contact you with queries related to oVirt APIs we plan to use. We have following queries: 1. While downloading a snapshot disk, can we identify allocated extents and download only those using oVirt API? We are able to download the disk using the Image Transfer API mechanism. However, this method downloads the entire disk including the non-allocated extents, which is a performance overhead. If this functionality does not exist at this point will it be available in near future? Hi Ranjit, There is no way to do this in current 4.2, but we plan to introduce in in 4.2.z. The API will be something like: GET /images/xxx-yyy/map ... [{ "start": 0, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 0}, { "start": 65536, "length": 983040, "depth": 0, "zero": true, "data": false, "offset": 65536}, { "start": 1048576, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 1048576}, { "start": 1114112, "length": 983040, "depth": 0, "zero": true, "data": false, "offset": 1114112}, ... { "start": 5465571328, "length": 22675456, "depth": 0, "zero": false, "data": true, "offset": 5465571328}, { "start": 5488246784, "length": 954138624, "depth": 0, "zero": true, "data": false, "offset": 5488246784}, { "start": 6442385408, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 6442385408}] This is basically what you get using qemu-img map. You can test play this with this using: virt-builder Fedora-27 -o /var/tmp/fedora-27.img qemu-img map -f raw --output json /var/tmp/fedora-27.img This is the first data segment: { "start": 0, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 0} This is a hole between the first data segment and the second: { "start": 65536, "length": 983040, "depth": 0, "zero": true, "data": false, "offset": 65536} This is the second data segment: { "start": 1048576, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 1048576} Based on this output, you will be able to get the allocated parts of the image using: Request: GET /image/xxx-yyy HTTP/1.1 Range: bytes=0-65535 Response: HTTP/1.1 206 Partial Content Content-Range: bytes 0-65535/6442450944 <data of first segment> Request: GET /image/xxx-yyy HTTP/1.1 Range: bytes=1048576-1114111 Response: HTTP/1.1 206 Partial Content Content-Range: bytes 1048576-1114111/6442450944 <data of second segment> And so on. If you create a sparse file on your backup media, and download and write the data segments at the correct offset, you will get the a sparse version of the image as on the server side. This will work for raw or qcow2 images on NFS >= 4.2, or for qcow2 images on block storage. For older NFS versions, or raw images on block storage, we can solve the issue by reading the entire image and detecting zeroes - which is quite expensive, so I'm not sure we will implement this, maybe it will be done later. We have experimental patch using special sparse format, that can support this use case, downloading entire image in one pass. This commit message explain the format: https://gerrit.ovirt.org/#/c/85413/12//COMMIT_MSG For more info on using random I/O APIs, see: http://ovirt.github.io/ovirt-imageio/random-io (available since 4.2.3) For example code uploading sparse images see: https://github.com/oVirt/ovirt-imageio/blob/master/examples/upload For best performance, you should run your application on a oVirt host, using unix socket to communicate with imageio. See: http://ovirt.github.io/ovirt-imageio/unix-socket (will be available in 4.2.5) All this will work only for the non-active layer in a qcow2 chain. We are working now on incremental backup which will allow the same for the active layer with a running vm. This is expected in 4.3, and we may have a tech preview at some point in 4.2.z. Incremantal backup will use the similar API, allowing detection of dirty parts of an image, so you can download only the data that was changed since the last backup. Please watch and comment on the feature page: https://ovirt.org/develop/release-management/features/storage/incremental-b… We are also considering exposing images using NBD. This will allow downloading and uploading images using qemu-img from any host. This work depends on TLS-PSK support in qemu-img and qemu-nbd. You can follow this work here: https://lists.nongnu.org/archive/html/qemu-devel/2018-06/threads.html#08491 2. Is there an alternate method to transfer a snapshot to and from RHV storage? Are there other methods such as NFS share where we can download snapshot image to and from RHV storage? We don't support direct access to storage by 3rd party. You should use imageio API. Can you file RFE for this, explaning the use case and the current performance issues you experience? Nir

4 4

vdsm has been tagged (v4.20.39)
by Milan Zamazal 28 Aug '18

28 Aug '18

Vdsm 4.20.39 for oVirt 4.2.6 rc3

1 0

new storage domain question
by Hetz Ben Hamo 27 Aug '18

27 Aug '18

Hi, I just found something very interesting. While installing latest ovirt, I've created the shared_storage on my nas1 share folder (NFS). So far, so good. However, when trying to create additional 2 new storage domains, I can only create 1 (which means the shared_storage is 1 and a new one is 2, I cannot create a 3rd storage domain, 4th etc..). When I try, it shows an error (I don't remember which error right now). Why is that? and why this strange (IMHO) shared_storage thing? in a corporate, if I want to set up a virtualized environment, the storage administrator asks me which one I want (NFS, or an iSCSI LUN), do I need one or more, and then I'm adding them as a datastore (in VMWare, for example) and on top of that I'm installing the management software (for example, vCenter). with oVirt method, it will confuse VMware admins. Thanks

2 5

ovirt-engine has been tagged (ovirt-engine-4.2.6.4)
by Tal Nisan 26 Aug '18

26 Aug '18

1 0

vdsm has been tagged (v4.20.38)
by Milan Zamazal 24 Aug '18

24 Aug '18

Vdsm 4.20.38 for oVirt 4.2.6 rc3

1 0

Fwd: [CentOS-announce] Release for CentOS Linux 7 (1804) on POWER9 (ppc64le)
by Sandro Bonazzola 22 Aug '18

22 Aug '18

FYI ---------- Forwarded message ---------- From: James O'Connor <jpoc(a)linux.vnet.ibm.com> Date: 2018-08-15 20:26 GMT+02:00 Subject: [CentOS-announce] Release for CentOS Linux 7 (1804) on POWER9 (ppc64le) To: centos-announce(a)centos.org I am pleased to announce the general availability of CentOS Linux 7 (1804) for POWER9 processors (ppc64le - powerpc 64-bit little endian). This release is derived from Red Hat Enterprise Linux 7.5 ALT. Note this release is 99% equivalent to the existing CentOS 7 Linux 7 (1804) for POWER8 processors (ppc64le - powerpc 64-bit little endian). The key difference being that kernel-4.14.0 is used for POWER9 enablement and kernel-3.10.0 is used for POWER8 enablement. You will find the CentOS 7 (1804) Power9 installation images here: http://mirror.centos.org/altarch/7.5.1804/isos/power9/ sha256sum power9: 753c5b55c9ff681c925ec7d7c5295890284f40ec981f4da35b1f36f1ecbad95a CentOS-7-Power9-Everything-1804.iso 58d9af172656db71947b5db2d0d1f577217bbc1a86eada7ca3ce7bfcf7d7d9b4 CentOS-7-Power9-NetInstall-1804.iso CentOS 7 (1804) Power9 repositories: http://mirror.centos.org/altarch/7.5.1804/os/power9/ http://mirror.centos.org/altarch/7.5.1804/updates/power9/ http://mirror.centos.org/altarch/7.5.1804/extras/power9/ A special thank you to Johnny Hughes and Pablo Greco for their assistance making this release possible. -James O’Connor _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

1 0