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 31 Oct '19

31 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