January 2021 - 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

Purging inactive maintainers from vdsm-master-maintainers
by Nir Soffer 21 Jun '21

21 Jun '21

I want to remove inactive contributors from vdsm-master-maintainers. I suggest the simple rule of 2 years of inactivity for removing from this group, based on git log. See the list below for current status: https://gerrit.ovirt.org/#/admin/groups/106,members Thoughts? Nir

6 11

Merge rights changes in the oVirt Engine project
by Tal Nisan 09 Apr '21

09 Apr '21

Hi everyone, As you probably know we are now in a mode in which we develop our next zstream version on the master branch as opposed to how we worked before where the master version was dedicated for the next major version. This makes the rapid changes in master to be delivered to customers in a much higher cadence thus affecting stability. Due to that we think it's best that from now on merges in the master branch will be done only by stable branch maintainers after inspecting those closely. What you need to do in order to get your patch merged: - Have it pass Jenkins - Have it get code review +2 - Have it mark verified +1 - It's always encourage to have it tested by OST, for bigger changes it's a must Once you have all those covered, please add me as a reviewer and I'll examine it and merge if everything seems right, if I haven't done it in a timely manner feel free to ping me.

3 4

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

Switch CentOS to Oracle Linux
by ntoxicator＠gmail.com 02 Feb '21

02 Feb '21

Hello, Oracle Linux is offering CentOS users/dev/production servers to switch to Oracle Linux free of cost. They've produced a script to do this. Oracle also has their own Repo's for oVirt and use it for their own Oracle Linux Virtualization Manager [Re-branded oVirt]. I know Red Hat has announced moving away from RHV and focusing on OpenShift virtualization. They'll happen in 2022-forward. Are we already to assume oVirt will follow suite and migrate to OpenShift?? Questions: Since announcement of CentOS going EOL and move to CentOS Stream... [Not doing it]. - Will the oVirt team continue to develop past 4.4 release as well as support Oracle Linux? - Does Oracle really develop to their own ovirt repo and virtualization manager product - What about supporting OpenSuSE or SLES? - oVirt packages on RHEL? [RH announced they will allow RHEL installed on up to 16-hosts for FREE] I am considering to test moving CentOS 7 development work-loads to Oracle Linux and use their oVirt repo. Really like to know if oVirt developers plan to continue to build on what is there moving forward. Or will the project die? I use oVirt on production work-loads [same as others] with GREAT success. This is an absolute VMWare replacement.

3 3

CentOS Stream support
by Michal Skrivanek 01 Feb '21

01 Feb '21

Hi all, we would like to ask about interest in community about oVirt moving to CentOS Stream. There were some requests before but it’s hard to see how many people would really like to see that. With CentOS releases lagging behind RHEL for months it’s interesting to consider moving to CentOS Stream as it is much more up to date and allows us to fix bugs faster, with less workarounds and overhead for maintaining old code. E.g. our current integration tests do not really pass on CentOS 8.1 and we can’t really do much about that other than wait for more up to date packages. It would also bring us closer to make oVirt run smoothly on RHEL as that is also much closer to Stream than it is to outdated CentOS. So..would you like us to support CentOS Stream? We don’t really have capacity to run 3 different platforms, would you still want oVirt to support CentOS Stream if it means “less support” for regular CentOS? There are some concerns about Stream being a bit less stable, do you share those concerns? Thank you for your comments, michal

6 12

ovirt-engine_standard-check-patch failed to fetch remote repo 'origin'
by Eyal Shenitzky 31 Jan '21

31 Jan '21

Hi, The ovirt-engine_standard-check-patch job in jenkins failed due to the following issue - [2021-01-31T13:15:01.371Z] The recommended git tool is: NONE [2021-01-31T13:15:05.283Z] No credentials specified [2021-01-31T13:15:05.283Z] No credentials specified [2021-01-31T13:15:05.393Z] Fetching changes from 2 remote Git repositories [2021-01-31T13:15:05.420Z] Cleaning workspace [2021-01-31T13:15:05.517Z] ERROR: Error fetching remote repo 'origin' [2021-01-31T13:15:05.517Z] hudson.plugins.git.GitException: Failed to fetch from https://gerrit.ovirt.org/jenkins [2021-01-31T13:15:05.518Z] at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:1001) [2021-01-31T13:15:05.518Z] at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1242) [2021-01-31T13:15:05.518Z] at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302) [2021-01-31T13:15:05.518Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125) [2021-01-31T13:15:05.518Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) [2021-01-31T13:15:05.518Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) [2021-01-31T13:15:05.518Z] at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) [2021-01-31T13:15:05.518Z] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [2021-01-31T13:15:05.518Z] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [2021-01-31T13:15:05.518Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [2021-01-31T13:15:05.518Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [2021-01-31T13:15:05.518Z] at java.lang.Thread.run(Thread.java:748) [2021-01-31T13:15:05.518Z] Caused by: hudson.plugins.git.GitException: Command "git clean -fdx" returned status code 1: Taken from - https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/10151/ which run as part of https://gerrit.ovirt.org/#/c/ovirt-engine/+/113113/ Seen also in other patches that were pushed today. Can someone please have a look? Thanks, -- Regards, Eyal Shenitzky

1 0

planned Jenkins restart
by Evgheni Dereveanchin 29 Jan '21

29 Jan '21

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

Ansible callbacks
by Michal Mocnak 29 Jan '21

29 Jan '21

Hello, is there a way how to trigger custom ansible playbooks ? For example when VM is created i'd like to automatically trigger playbook to define exact MAC address. I guess this is not possible to integrate via VDSM hook as they are executed on the host basis. Maybe it's possible to write UI plugin but i didn't find as much in documentation. Thank you so much ! Cheers -m

2 2

VDSM Hook to modify passthrough devices
by Michal Mocnak 29 Jan '21

29 Jan '21

Hello, i've set up gpu passthrough with RTX2080 consumer grade card properly. But need to add rom file param into libvirt XML. I wrote vdsm hook which is quite easy but i've found a problem that even i put the hook into before_vm_start event those passthrough devices are not present at that time in the XML. I couldn't find anything on docs about when those devices are ready in the XML and which event i should use. Thank you so much !! Cheers -michal

1 0

who can tell me that you did development environment on centos 7.9 was successful？
by unsayablelove＠gmail.com 29 Jan '21

29 Jan '21

I followed the official tutorial to deploy the development environment on centos7.9 but when I execute “make install-dev PREFIX="$HOME/ovirt-engine"” ，the system report two message and I search similar situation on https://bugzilla.redhat.com/show_bug.cgi?id=1549166

3 4

OST fails with NPE in VmDeviceUtils.updateUsbSlots
by Vojtech Juranek 28 Jan '21

28 Jan '21

Hi, OST fails constantly in test_check_snapshot_with_memory [1] with NPE in VmDeviceUtils.updateUsbSlots [2]. Build with any additional changes (custom repo) is on [3]. Unfortunately, I wasn't able to find the root cause. Could someone please take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7720/consoleFull [2] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7720/artifact/expor… [3] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/7718/parameters/

3 4

changequeue-status_master_standard-poll-upstream-sources failing consistently for more than a month
by Sandro Bonazzola 28 Jan '21

28 Jan '21

Hi, https://jenkins.ovirt.org/job/changequeue-status_master_standard-poll-upstr… is consistently failing with the last recorded successful build on November 24th 2020. Who's the current maintainer of this job? According to gerrit, changequeue-status project was owned by +Dan Kenigsberg <danken(a)redhat.com> but he's not actively involved in oVirt project anymore. If nobody is picking this project up I think we should drop the test. 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. <https://mojo.redhat.com/docs/DOC-1199578>*

3 2

ovirt-engine has been tagged (ovirt-engine-4.4.5.3)
by Tal Nisan 27 Jan '21

27 Jan '21

1 0

[VDSM] Test pass, build fail during cleanup
by Nir Soffer 26 Jan '21

26 Jan '21

We seem to have an issue in the CI, starting this week. All tests pass, but creating coverage report fail: + generate_combined_coverage_report + pushd tests ~/tests ~ + pwd /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests + ls .coverage-gluster .coverage-lib .coverage-network .coverage-nose .coverage-storage .coverage-virt .coverage-gluster .coverage-lib .coverage-network .coverage-nose .coverage-storage .coverage-virt + python3 -m coverage combine .coverage-gluster .coverage-lib .coverage-network .coverage-nose .coverage-storage .coverage-virt No usable data files Coverage.py warning: Couldn't read data from '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/.coverage-gluster': UnicodeDecodeError: 'utf-8' codec can't decode byte 0x96 in position 106: invalid start byte Coverage.py warning: Couldn't read data from '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/.coverage-lib': UnicodeDecodeError: 'utf-8' codec can't decode byte 0x96 in position 106: invalid start byte Coverage.py warning: Couldn't read data from '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/.coverage-network': UnicodeDecodeError: 'utf-8' codec can't decode byte 0x96 in position 106: invalid start byte Coverage.py warning: Couldn't read data from '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/.coverage-nose': UnicodeDecodeError: 'utf-8' codec can't decode byte 0x96 in position 106: invalid start byte Coverage.py warning: Couldn't read data from '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/.coverage-storage': UnicodeDecodeError: 'utf-8' codec can't decode byte 0x96 in position 106: invalid start byte Coverage.py warning: Couldn't read data from '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/.coverage-virt': UnicodeDecodeError: 'utf-8' codec can't decode byte 0x96 in position 106: invalid start byte This looks like a bug in coverage, or maybe we use the wrong version of this tool? + teardown + res=1 + '[' 1 -ne 0 ']' + echo '*** err: 1' *** err: 1 Additionally, we have this very strange error: + teardown_storage + python3 tests/storage/userstorage.py teardown python3: can't open file 'tests/storage/userstorage.py': [Errno 2] No such file or directory This error is impossible, since tests/storage/userstorage.py is part of the source. Is it possible that some other code has deleted the source while a build was running? + echo 'WARNING: Ingoring error while tearing down user storage' WARNING: Ingoring error while tearing down user storage We were careful not to fail the build because this issue, but it failed because coverage report could not be created. There are multiple instance of this issue: - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/26107//artifact/che… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/26103//artifact/che… - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/26102//artifact/che… I think Eyal reported another instance, but I cannot find it now. 2 weeks ago we updated pytest and pytest-cov to latest version, but we did not see this issue in the CI when we tested the change: https://gerrit.ovirt.org/c/vdsm/+/112604 And CI was fine since then, so this may not be related, unless this is a regression in latest coverage or pytest-cov. Nir

2 2

OST fails, please review gerrit #113140
by Vojtech Juranek 25 Jan '21

25 Jan '21

Hi, OST fails AFAICT due to flake8 issue. Please review [1], it should fix the issue. Thanks Vojta [1] https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/113140/

1 0

Gerrit very slow again - reload takes many seconds
by Nir Soffer 24 Jan '21

24 Jan '21

This is not a new issue, we see this every few months. In the past I think this was solved by restarting gerrit. I compared our gerrit to other installations: https://go-review.googlesource.com/ https://review.opendev.org/ Both reloads in about 1 second. Our gerrit takes 10-15 seconds. Go gerrit is using: 3.3.1-812-g388176bbb4 Openstack is using: 3.2.6-28-g4a9ffec296-dirty We use: 2.16.23 Looking in https://www.gerritcodereview.com/ current version is 3.3.1. Looks like we are using an old version. Nir

1 0

OST on Stream
by Michal Skrivanek 22 Jan '21

22 Jan '21

There seems to be multiple issues really 1) First it fails on “unknown state” of ovirt-engine-notifier service. Seems the OST code is not handling service states well and just explodes 2) Either way, the problem is it's stopped. It should be running 3) if you start it manually it gets to the engine-config test and restarts engine. It explodes here again, apparently same reason as #1 4) host installation fails - didi’s https://gerrit.ovirt.org/#/c/ovirt-engine/+/113101/ is fixing it 5) verify_engine_notifier fails when we try to stop it. it’s not running due to #2 and it explodes anyway due to #1 rest seems to work fine except few more #1 issues, so that’s good… Marcin, can you please prioritize #1? Martin, any idea about notifier? Thanks, michal

2 3

Re: [ovirt-users] Re: [ANN] oVirt 4.4.4 is now generally available
by Benny Zlotnik 22 Jan '21

22 Jan '21

On Tue, Dec 22, 2020 at 6:33 PM Konstantin Shalygin <k0ste(a)k0ste.ru> wrote: > > Sandro, FYI we are not against cinderlib integration, more than we are upgrade 4.3 to 4.4 due movement to cinderlib. > > But (!) current Managed Storage Block realization support only krbd (kernel RBD) driver - it's also not a option, because kernel client is always lagging behind librbd, and every update\bugfix we should reboot whole host instead simple migration of all VMs and then migrate it back. Also with krbd host will be use kernel page cache, and will not be unmounted if VM will crash (qemu with librbd is one userland process). > There was rbd-nbd support at some point in cinderlib[1] which addresses your concerns, but it was removed because of some issues +Gorka, are there any plans to pick it up again? [1] https://github.com/Akrog/cinderlib/commit/a09a7e12fe685d747ed390a59cd42d0ac… > So for me current situation look like this: > > 1. We update deprecated OpenStack code? Why, Its for delete?.. Nevermind, just update this code... > > 2. Hmm... auth tests doesn't work, to pass test just disable any OpenStack project_id related things... and... Done... > > 3. I don't care how current cinder + qemu code works, just write new one for linux kernel, it's optimal to use userland apps, just add wrappers (no, it's not); > > 4. Current Cinder integration require zero configuration on oVirt hosts. It's lazy, why oVirt administrator do nothing? just write manual how-to install packages - oVirt administrators love anything except "reinstall" from engine (no, it's not); > > 5. We broke old code. New features is "Cinderlib is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production". > > 6. Oh, we broke old code. Let's deprecate them and close PRODUCTION issues (we didn't see anything). > > > And again, we are not hate new cinderlib integration. We just want that new technology don't break all PRODUCTION clustes. Almost two years ago I write on this issue https://bugzilla.redhat.com/show_bug.cgi?id=1539837#c6 about "before deprecate, let's help to migrate". For now I see that oVirt totally will disable QEMU RBD support and want to use kernel RBD module + python os-brick + userland mappers + shell wrappers. > > > Thanks, I hope I am writing this for a reason and it will help build bridges between the community and the developers. We have been with oVirt for almost 10 years and now it is a crossroads towards a different virtualization manager. > > k > > > So I see only regressions for now, hope we'll found some code owner who can catch this oVirt 4.4 only bugs. > I looked at the bugs and I see you've already identified the problem and have patches attached, if you can submit the patches and verify them perhaps we can merge the fixes

5 6

[ANN] oVirt 4.4.5 Second Release Candidate is now available for testing
by Sandro Bonazzola 22 Jan '21

22 Jan '21

oVirt 4.4.5 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Second Release Candidate for testing, as of January 21st, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- 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.*

1 0

"Exception: null" after "Check if post tasks file exists" (was: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1892 - Failure!)
by Yedidyah Bar David 21 Jan '21

21 Jan '21

Hi all, On Thu, Jan 21, 2021 at 4:56 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1892/ https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1892… : 2021-01-21 03:25:52,254+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Installing Host lago-he-basic-suite-master-host-0.lago.local. Check if post tasks file exists. 2021-01-21 03:25:52,258+01 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] Exception: null 2021-01-21 03:25:52,296+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Installing Host lago-he-basic-suite-master-host-0.lago.local. Gather the rpm package facts. 2021-01-21 03:25:52,312+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Installing Host lago-he-basic-suite-master-host-0.lago.local. Check if post tasks file exists. 2021-01-21 03:25:52,316+01 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] Host installation failed for host '736e10b6-0445-4a24-935d-87ba15cae4c4', 'lago-he-basic-suite-master-host-0.lago.local': null 2021-01-21 03:25:52,321+01 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] START, SetVdsStatusVDSCommand(HostName = lago-he-basic-suite-master-host-0.lago.local, SetVdsStatusVDSCommandParameters:{hostId='736e10b6-0445-4a24-935d-87ba15cae4c4', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 198cd7e7 2021-01-21 03:25:52,337+01 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] FINISH, SetVdsStatusVDSCommand, return: , log id: 198cd7e7 2021-01-21 03:25:52,363+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [6668b493] EVENT_ID: VDS_INSTALL_FAILED(505), Host lago-he-basic-suite-master-host-0.lago.local installation failed. Please refer to /var/log/ovirt-engine/engine.log and log logs under /var/log/ovirt-engine/host-deploy/ for further details.. https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1892… ends with: 2021-01-21 03:25:52 CET - TASK [Executing post tasks defined by user] ************************************ Any idea? Best regards, > Build Number: 1892 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #1892 > [Andrej Cernek] pylint: Fix searched directories > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. -- Didi

2 3

ovirt-engine has been tagged (ovirt-engine-4.4.5.2)
by Tal Nisan 20 Jan '21

20 Jan '21

1 0

bz 1915329: [Stream] Add host fails with: Destination /etc/pki/ovirt-engine/requests not writable
by Yedidyah Bar David 20 Jan '21

20 Jan '21

Hi all, Now filed $Subject [1]. Any clues are most welcome. Thanks. Best regards, [1] https://bugzilla.redhat.com/show_bug.cgi?id=1915329 -- Didi

3 11

ovirt-engine has been tagged (ovirt-engine-4.4.5.1)
by Tal Nisan 20 Jan '21

20 Jan '21

2 1