October 2019 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error: Adding new Host to ovirt-engine
by Ahmad Khiet 14 Aug '23

14 Aug '23

Hi, Can't add new host to ovirt engine, because the following error: 2019-06-12 12:23:09,664 p=4134 u=engine | TASK [ovirt-host-deploy-facts : Set facts] ************************************* 2019-06-12 12:23:09,684 p=4134 u=engine | ok: [10.35.1.17] => { "ansible_facts": { "ansible_python_interpreter": "/usr/bin/python2", "host_deploy_vdsm_version": "4.40.0" }, "changed": false } 2019-06-12 12:23:09,697 p=4134 u=engine | TASK [ovirt-provider-ovn-driver : Install ovs] ********************************* 2019-06-12 12:23:09,726 p=4134 u=engine | fatal: [10.35.1.17]: FAILED! => {} MSG: The conditional check 'cluster_switch == "ovs" or (ovn_central is defined and ovn_central | ipaddr and ovn_engine_cluster_version is version_compare('4.2', '>='))' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller The error appears to be in '/home/engine/apps/engine/share/ovirt-engine/playbooks/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - block: - name: Install ovs ^ here 2019-06-12 12:23:09,728 p=4134 u=engine | PLAY RECAP ********************************************************************* 2019-06-12 12:23:09,728 p=4134 u=engine | 10.35.1.17 : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 whats missing!? Thanks -- Ahmad Khiet Red Hat <https://www.redhat.com/> akhiet(a)redhat.com M: +972-54-6225629 <https://red.ht/sig>

7 10

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/jav… ). Can you confirm the defect? Best regards Patrick

6 11

Fetch LUN ID for iSCSI Creation
by scott.fitzgerald＠oracle.com 04 Dec '19

04 Dec '19

Hi, Using sysService.hostsService().hostService(host.id()).iscsiDiscover().iscsi(iscsiDetailsBuilder).send().discoveredTargets(); Where iscsiDetailsBuilder is IscsiDetailsBuilder iscsiDetailsBuilder = new IscsiDetailsBuilder().address(address).port(port); I can fetch an iSCSI details container list, which contains the list of iSCSI targets. However, all values, except the address, port, portal and target string are null. I need the iSCSI LUN ID for automation of iSCSI creation. How can this be done via the SDK? Thanks in advance.

2 2

Dropping local crypto settings throughout oVirt in favour of crypto policies
by Marcin Sobczyk 07 Nov '19

07 Nov '19

Hi, given that crypto policies appeared in RHEL8 I think it's a good time to discuss using them throughout oVirt. I prepared a document, that describes the current state of crypto settings in VDSM along with the benefits and potential issues that come with moving to crypto policies. If you have a moment, please go through the doc - any input and comments are welcome. https://docs.google.com/document/d/1K19jDOITEQenPDbbSft2ChgGrL_DgpcbQon_bWL… Regards, Marcin Sobczyk

2 2

[feedback needed] VirtIO Windows Drivers - new installer
by Steve Graham 04 Nov '19

04 Nov '19

Good morning - I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service. I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help. The system is 2012 R2 fully patched. Thank you for all your hard work! [image: 2019-10-30_11-12-00.png]

3 5

qemu-img process stuck
by Vojtech Juranek 01 Nov '19

01 Nov '19

Hi, I'm doing some manual storage tests on RHEL 8.1 host (kernel version 4.18.0-107.el8.x86_64) and run into following issue: when I try to move an image to block SD and RHEL 8.1 host is SPM, qemu-img gets stuck. There are errors regarding blk_cloned_rq_check_limits on RHEL host and also max_write_same_len on iscsi target (see bellow). iscsi target runs CentOS 7.6. Before running qemu-img command, everything works fine (e.g. cat a file from iscsi target), after running qemu-img, all IO on iscsi target is very slow. When I try to run qemu-img command manually, it's very slow (1GB image take several minutes), but finishes, when it's run from vdsm, it seems to be hung forever. In similar cases I found it could be fixed by adjusting various values in /sys/block/#DEVICE/queue/, but in this case, AFAICT all values are correct (same as on CentOS 7.7 host where everything work). Or it was identified as a bug in the kernel and was suggested to upgrade to newer kernel. Do you know any workaround, how to make it working? Or does it sound to you like a bug in kernel which should be reported? Thanks Vojta Example of qemu-img command: [root@localhost ~]#/usr/bin/qemu-img convert -p -t none -T none -f raw /rhev/data-center/mnt/blockSD/ceba76d5-9d5d-4b04-9226-dffc7e77d4be/images/9aafce3d-53a6-41d7-b0d5-0e1db8aa59fc/7b7c7800-4837-4c3f-967c-c942b9c54e1b -O raw -W /rhev/data-center/mnt/blockSD/a17d7695-50fc-412e-abc7-008ebb6cdf23/images/9aafce3d-53a6-41d7-b0d5-0e1db8aa59fc/7b7c7800-4837-4c3f-967c-c942b9c54e1b (100.00/100%) Errors on RHEL 8.1 host: [ 356.658973] print_req_error: critical target error, dev dm-8, sector 31203328 flags 9 [ 356.658982] print_req_error: critical target error, dev dm-8, sector 31268863 flags 9 [ 356.658984] print_req_error: critical target error, dev dm-8, sector 31334398 flags 9 [ 356.658986] print_req_error: critical target error, dev dm-8, sector 31399933 flags 9 [ 356.658987] print_req_error: critical target error, dev dm-8, sector 31465468 flags 9 [ 356.658989] print_req_error: critical target error, dev dm-8, sector 31531003 flags 9 [ 356.658999] print_req_error: critical target error, dev dm-8, sector 31596538 flags 9 [ 356.659001] print_req_error: critical target error, dev dm-8, sector 31662073 flags 9 [ 356.659008] blk_cloned_rq_check_limits: over max size limit. [ 356.659044] device-mapper: multipath: Failing path 8:80. [ 356.669966] print_req_error: critical target error, dev dm-8, sector 31727608 flags 9 [ 356.669987] print_req_error: critical target error, dev dm-8, sector 31793143 flags 9 [ 358.923614] device-mapper: multipath: Reinstating path 8:80. [ 358.933888] sd 6:0:0:4: alua: port group 00 state A non-preferred supports TOlUSNA [ 358.933980] blk_cloned_rq_check_limits: over max size limit. [ 358.934008] device-mapper: multipath: Failing path 8:80. [ 364.927647] device-mapper: multipath: Reinstating path 8:80. [ 364.956799] sd 6:0:0:4: alua: port group 00 state A non-preferred supports TOlUSNA [ 364.956890] blk_cloned_rq_check_limits: over max size limit. [...] [ 475.001255] blk_cloned_rq_check_limits: over max size limit. [ 475.001271] device-mapper: multipath: Failing path 8:80. [ 479.995729] device-mapper: multipath: Reinstating path 8:80. [ 480.006078] sd 6:0:0:4: alua: port group 00 state A non-preferred supports TOlUSNA [ 480.006114] blk_cloned_rq_check_limits: over max size limit. [ 480.006134] device-mapper: multipath: Failing path 8:80. [ 484.997257] device-mapper: multipath: Reinstating path 8:80. [ 485.006868] sd 6:0:0:4: alua: port group 00 state A non-preferred supports TOlUSNA [ 485.006908] blk_cloned_rq_check_limits: over max size limit. [ 485.006960] device-mapper: multipath: Failing path 8:80. [ 489.998641] device-mapper: multipath: Reinstating path 8:80. [ 490.010288] sd 6:0:0:4: alua: port group 00 state A non-preferred supports TOlUSNA [ 490.010430] blk_cloned_rq_check_limits: over max size limit. [ 490.010455] device-mapper: multipath: Failing path 8:80. [ 492.922671] INFO: task qemu-img:9509 blocked for more than 120 seconds. [ 492.922675] Tainted: G --------- -t - 4.18.0-107.el8.x86_64 #1 [ 492.922676] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 492.922677] qemu-img D 0 9509 7416 0x00000080 [ 492.922679] Call Trace: [ 492.922703] ? __schedule+0x253/0x830 [ 492.922704] schedule+0x28/0x70 [ 492.922705] schedule_timeout+0x26d/0x390 [ 492.922711] ? blk_flush_plug_list+0xd7/0x100 [ 492.922713] io_schedule_timeout+0x19/0x40 [ 492.922714] wait_for_completion_io+0x11f/0x190 [ 492.922717] ? wake_up_q+0x70/0x70 [ 492.922719] submit_bio_wait+0x5b/0x80 [ 492.922728] blkdev_issue_zeroout+0x142/0x220 [ 492.922737] blkdev_fallocate+0x11e/0x190 [ 492.922745] vfs_fallocate+0x13f/0x280 [ 492.922753] ksys_fallocate+0x3c/0x80 [ 492.922754] __x64_sys_fallocate+0x1a/0x20 [ 492.922756] do_syscall_64+0x5b/0x1b0 [ 492.922764] entry_SYSCALL_64_after_hwframe+0x65/0xca [ 492.922767] RIP: 0033:0x7f9e2f8f1e85 [ 492.922771] Code: Bad RIP value. [ 492.922771] RSP: 002b:00007f9e2d79ba20 EFLAGS: 00000293 ORIG_RAX: 000000000000011d [ 492.922772] RAX: ffffffffffffffda RBX: 000000000000000a RCX: 00007f9e2f8f1e85 [ 492.922773] RDX: 0000000000000000 RSI: 0000000000000003 RDI: 000000000000000a [ 492.922773] RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000001 [ 492.922774] R10: 0000000040000000 R11: 0000000000000293 R12: 0000000000000000 [ 492.922774] R13: 0000000040000000 R14: 000055b21fe81390 R15: 00007f9e2d79bbc0 Errors on iscsi target: [ 703.199374] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.200836] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.202089] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.203289] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.204479] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.205819] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.206878] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.208020] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.209084] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.210357] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.211439] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.212584] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.213756] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096 [ 703.214813] WRITE_SAME sectors: 65535 exceeds max_write_same_len: 4096

2 2

Creating bonds between Network Interface Cards with SDK
by Jamie Holohan 31 Oct '19

31 Oct '19

How can I bond one network interface to another using the SDK. I am try to perform the task in java but I'm unsure in what context I can find the utilities that will do this task. The task can be performed in the OVM UI after a host has been initialised. By navigating from the side bar Compute -> Hosts -> (Select Host) -> (Host tabs) Network Interfaces -> From here, click Setup Host Networks. In the pop up you can select a network interface and drag it to another to create a bond between them. How can I perform this step using the SDK. I am attempting to perform this in the context of a nicservice, found like this: systemService.hostsService().hostService(hostObject).nicservice(NICObject)).get().send().nic(); but I can't find any methods associated with the retrieved NIC or nicservice that seem relevant to my task.

2 1

Planned restart of production services
by Evgheni Dereveanchin 30 Oct '19

30 Oct '19

Hi everyone, I'll be restarting several production systems today to apply security updates. The following services may be unreachable for short periods of time: - resources.ovirt.org - software repositories - jenkins.ovirt.org - CI master No new builds will be started during this period. I will announce you once maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

vdsm has been tagged (v4.30.35)
by Petr Horacek 30 Oct '19

30 Oct '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.7.1)
by Tal Nisan 30 Oct '19

30 Oct '19

1 0

CentOS builds fail because cbs.centos.org/repos/virt7-kvm-common-testing/{x86_64/ppc64le} not found
by Nir Soffer 30 Oct '19

30 Oct '19

We have failing imageio builds, seems that the centos virt7-kvm-common-testing is broken. ppc64le: https://cbs.centos.org/repos/virt7-kvm-common-testing/ppc64le/os/repodata/r…: [Errno 14] HTTPS Error 404 - Not Found https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1611/artif… x86_64: https://cbs.centos.org/repos/virt7-kvm-common-testing/x86_64/os/repodata/re…: [Errno 14] HTTPS Error 404 - Not Found https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1611/artif… Patch: https://gerrit.ovirt.org/c/101788/ Sandro, can you check this? Nr

2 1

[vdsm] Standard patch check broken by Black formatter for network stuff
by Vojtech Juranek 29 Oct '19

29 Oct '19

Hi, standard patch check tests for vdsm are broken due to Black formatter check failure (see e.g. [1]): Oh no! 10:16:24 6 files would be reformatted, 164 files would be left unchanged. 10:16:24 ERROR: InvocationError for command /home/jenkins/workspace/ vdsm_standard-check-patch/vdsm/.tox/black/bin/black -l 79 -S --check ./lib/ vdsm/network/ ./tests/network (exited with code 1) Can someone take a look and fix it? I did a quick check and wasn't able to find any recent commit which should cause this failure:-( Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/13396

3 2

OST: Failing migrations on el8
by Milan Zamazal 29 Oct '19

29 Oct '19

Hi, I looked at the failing migrations in OST on el8, when running basic-suite-master with https://gerrit.ovirt.org/#/c/103888/31. The migration fails even before started, when Vdsm tries to talk to the remote Vdsm and can't reach it. Indeed, there seems to be a networking problem between the hosts: [root@lago-basic-suite-master-host-1 ~]# ping -c 1 lago-basic-suite-master-host-0 PING lago-basic-suite-master-host-0(lago-basic-suite-master-host-0.lago.local (fd8f:1391:3a82:201::c0a8:c902)) 56 data bytes From lago-basic-suite-master-host-1 (fd8f:1391:3a82:200::c0a8:c899): icmp_seq=1 Destination unreachable: Address unreachable Regards, Milan

5 5

Errors while building ovirt-engine master on fedora 29
by Kaustav Majumder 29 Oct '19

29 Oct '19

Hi, I am currently facing this error while building ovirt-engine master (commit da774d861d5a593666932f6e678f5383222ed8d5) on fedora 29. *[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project ovirt-checkstyle-extension: Fatal error compiling: invalid flag: --release -> [Help 1]* full build log here: https://pastebin.com/rJA5PHWu -- Thanks, Kaustav Majumder

3 6

Automatic snapshots
by Joost Evertse 29 Oct '19

29 Oct '19

Hello everyone, We run a large number of virtual desktops on RHEV and we use the snapshot mechanism occasionally. Would it be possible to create automatic snapshots when VM’s are started and when they are stopped? My gut feeling says this would be a bad idea, because taking snapshots does not guarantee anything, but I have the task of exploring the option. If needed, I would change source code to create something and contribute it. Currently I have taken a look at - the vdsm hook mechanism, but that seems to be aimed at the VM lifecycle, not operations like starting and stopping an instance. - the ovirt-agent hooks , but they also seem to be useful when migrating a VM The goal of the snapshot is to have a backup-backup, just handy when dealing with malfunctions inside a VM workstation, it does not have to be perfect. Maybe I can create scripts to enable functionality in a different (existing) place, but I am a bit reluctant to create unnecessary scripting because that creates admin overhead. Maybe from an architectural point of view automatic snapshots is just a plain wrong idea, not sure. What are your thoughts about this? With kind regards, Joost Evertse

1 0

IMPORTANT: OST is now gated.
by Ehud Yonasi 29 Oct '19

29 Oct '19

Hey everyone, OST project is now enabled for patch gating. What is the meaning of this? 1. The gating process will start when Code-Review +2, CI +1 and Verified +1 labels are turned on. 2. Every patch before merging will have to pass the following suites: - *oVirt-master* *oVirt-4.3* basic_suite basic_suite upgrade-from-release upgrade-from-release upgrade-from-prevrelease 3. Patches should no longer be manually merged in OST, they will be merged automatically when passing the gate. *NOTE: *Maintainers are still able to merge manually, but it is not recommended if the gate is not passing. *NOTE:* For additional information regarding the gating I've sent FAQ mail - 'Patch Gating summary + FAQ' Regards, Ehud.

4 4

Re: [ovirt-users] Host-passthrough CPU and migration
by Strahil 27 Oct '19

27 Oct '19

Ah... Never thought I can switch it to 'Auto'. Actually it makes sense - we can't be sure if all nodes in cluster are the same - like my case. Now all VMs are in Auto mode. Thanks for the clarification, Sharon. Best Regards, Strahil NikolovOn Oct 27, 2019 17:30, Sharon Gratch <sgratch(a)redhat.com> wrote: > > Hi, > > The "manual migration" option is only a default value. You can change the migration mode to "automatic" mode if you prefer. > > Details: > When you enable Host CPU Pass-Through for a VM then the migration default value is auto set to "manual migration" in UI because it's not sure if this VM should be automatically migrated as part of internal events (such as load balancing policies or host turning into maintenance mode), without letting the user controlling it. > > Sometimes there are few destination hosts to migrate to and we want to let the user controlling that since performance may decrease or migration may fail. > > But if you are sure that the cluster contains hosts with identical cpu model and identical number of sockets, threads and cores as the source host, and you don't mind that VM will be migrated whenever required, then you can definitely change the migration value to "Allow manual and automatic migration". > > Thanks, > Sharon > > On Sun, Oct 20, 2019 at 2:42 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Hello Community,Dev, >> >> does anyone know why only "Manual Migration" allows passing through the CPU from the Host to the VM ? >> >> In many environments, the Clusters are having the same CPU model in order to avoid any issues. Have you observed any issues with that ? >> >> Best Regards, >> Strahil Nikolov >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/sit

1 0

Host-passthrough CPU and migration
by Strahil Nikolov 27 Oct '19

27 Oct '19

Hello Community,Dev, does anyone know why only "Manual Migration" allows passing through the CPU from the Host to the VM ? In many environments, the Clusters are having the same CPU model in order to avoid any issues. Have you observed any issues with that ? Best Regards,Strahil Nikolov

2 1

[oVirt] [CQ weekly status] [26-10-2019]
by Dusan Fodor 26 Oct '19

26 Oct '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.3*: GREEN (#1) Last failure was on 25-10 for ovirt-host due to dependency issue. Patch ( 104248 <https://gerrit.ovirt.org/104248>) is pending to fix this. *CQ-Master:* YELLOW (#1 Last failure was on 25-10 caused by known, random add storage domain failure (test issue). Current running jobs for 4.3 [1] and master [2] can be found here: [1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YCNCKRK3G4EJX…

1 0

Fwd: [Test-Announce] Fedora 31 Final is GO
by Sandro Bonazzola 24 Oct '19

24 Oct '19

FYI ---------- Forwarded message --------- Da: Ben Cotton <bcotton(a)redhat.com> Date: gio 24 ott 2019 alle ore 17:43 Subject: [Test-Announce] Fedora 31 Final is GO To: <logistics(a)lists.fedoraproject.org>, < test-announce(a)lists.fedoraproject.org>, < devel-announce(a)lists.fedoraproject.org> The Fedora 31 Final RC1.9 compose [1] is GO and will be shipped live on Tuesday, 29 October 2019. For more information please check the Go/No-Go meeting minutes [2] or logs [3]. Thank you to everyone who has worked on this release and getting it out on time. [1] https://dl.fedoraproject.org/pub/alt/stage/31_RC-1.9/ [2] https://meetbot.fedoraproject.org/fedora-meeting/2019-10-24/f31-final-go_no… [3] https://meetbot.fedoraproject.org/fedora-meeting/2019-10-24/f31-final-go_no… -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorapro… _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

1 0

VDSM master not building for el8 on ppc64le
by Sandro Bonazzola 24 Oct '19

24 Oct '19

Hi, can you please check why vdsm is not being built for el8 on ppc64le? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 3

Ovirt System Tests: reposync fails during run_suite.sh
by raymond.francis＠oracle.com 24 Oct '19

24 Oct '19

I am currently setting up the Ovirt System Tests using the guide https://ovirt-system-tests.readthedocs.io/en/latest/general/running_tests/i… So we get to the run_suite.sh part. This calls a python script called put_host_image.py which tries to create a symlink to the current repo but hits an issue where the file (internal_repo/host_image) is said to not exist at the time. Output below python /Ray/ovirt-system-tests/common/scripts/put_host_image.py /Ray/ovirt-system-tests/deployment-basic-suite-4.3 /Ray/ovirt-system-tests/deployment-basic-suite-4.3/current/internal_repo/host_image Backing file path is /var/lib/lago/store/phx_repo:el7.6-base-5:v1 dest is /Ray/ovirt-system-tests/deployment-basic-suite-4.3/current/internal_repo/host_image Traceback (most recent call last): File "/Ray/ovirt-system-tests/common/scripts/put_host_image.py", line 66, in <module> main() File "/Ray/ovirt-system-tests/common/scripts/put_host_image.py", line 63, in main add_host_image_to_dest(prefix_path=sys.argv[1], dest=sys.argv[2]) File "/Ray/ovirt-system-tests/common/scripts/put_host_image.py", line 55, in add_host_image_to_dest symlink(backing_file_path, dest) OSError: [Errno 2] No such file or directory + on_exit + [[ 1 -ne 0 ]] + logger.error 'on_exit: Exiting with a non-zero status' + logger.log ERROR 'on_exit: Exiting with a non-zero status' + set +x 2019-10-16 14:50:14.980898261+0100 run_suite.sh::on_exit::ERROR:: on_exit: Exiting with a non-zero status + logger.info 'Dumping lago env status' + logger.log INFO 'Dumping lago env status' + set +x 2019-10-16 14:50:14.986356383+0100 run_suite.sh::on_exit::INFO:: Dumping lago env status + env_status + cd /Ray/ovirt-system-tests/deployment-basic-suite-4.3 + lago status [Prefix]: Base directory: /Ray/ovirt-system-tests/deployment-basic-suite-4.3/default [Networks]: [lago-basic-suite-4-3-net-bonding]: gateway: 192.168.203.1 management: False status: down [lago-basic-suite-4-3-net-management]: gateway: 192.168.205.1 management: True status: down [lago-basic-suite-4-3-net-storage]: gateway: 192.168.204.1 management: False status: down UUID: d6b67236f01b11e988fc002128a2f0d8 [VMs]: [lago-basic-suite-4-3-engine]: [NICs]: [eth0]: ip: 192.168.205.2 network: lago-basic-suite-4-3-net-management [eth1]: ip: 192.168.204.2 network: lago-basic-suite-4-3-net-storage distro: el7 [metadata]: deploy-scripts: $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_engine.sh ovirt-engine-password: 123 root password: 123456 status: down [lago-basic-suite-4-3-host-0]: [NICs]: [eth0]: ip: 192.168.205.4 network: lago-basic-suite-4-3-net-management [eth1]: ip: 192.168.204.4 network: lago-basic-suite-4-3-net-storage [eth2]: ip: 192.168.203.4 network: lago-basic-suite-4-3-net-bonding [eth3]: ip: 192.168.203.5 network: lago-basic-suite-4-3-net-bonding distro: el7 [metadata]: deploy-scripts: $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_host_el7.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_1st_host_el7.sh root password: 123456 status: down [lago-basic-suite-4-3-host-1]: [NICs]: [eth0]: ip: 192.168.205.3 network: lago-basic-suite-4-3-net-management [eth1]: ip: 192.168.204.3 network: lago-basic-suite-4-3-net-storage [eth2]: ip: 192.168.203.2 network: lago-basic-suite-4-3-net-bonding [eth3]: ip: 192.168.203.3 network: lago-basic-suite-4-3-net-bonding distro: el7 [metadata]: deploy-scripts: $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_add_local_repo_no_ext_access.sh $LAGO_PREFIX_PATH/scripts/_Ray_ovirt-system-tests_basic-suite-4.3_deploy-scripts_setup_host_el7.sh root password: 123456 status: down + cd - /Ray/ovirt-system-tests

2 5

workaround for the lack of native el8 slaves in the CI
by Marcin Sobczyk 23 Oct '19

23 Oct '19

Hi all, we're trying to move vdsm tests to el8. AFAIK we don't have native el8 slaves in the CI yet, so our el8 stages run on el7 with el8 mocked. There are some issues with scripts setting up the env for storage tests - they are refusing to work on older kernel versions. I have an idea for a workaround - until now we were using 'host-distro: same' in our 'stdci.yaml'. I can see that this option can also take a value of 'better/newer' [1], but that won't work for el8. Could we possibly implement something like [2] ? That would allow us to i.e. define an el8 mocked env with 'host-distro: fc30' enforcing native fc30 host. I assume this would be a temporary workaround only, until we have native el8 slaves. Regards, Marcin [1] https://github.com/oVirt/jenkins/blob/a796094bfd15f1a85b9f630aaeb25ce6e0dab… [2] https://gerrit.ovirt.org/#/c/104091/

6 7

Restart a Host
by scott.fitzgerald＠oracle.com 23 Oct '19

23 Oct '19

Hi, I am currently trying to restart a host, ie send it into reboot state, and then up, using the Restart button below SSH Management in the UI. How is this achieved? I don't see a restart option in any of the host endpoints. TIA

3 5