December 2018 - 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 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

propose Ravi Nori as a frontend maintainer for ovirt-engine infra
by Greg Sheremeta 04 Feb '19

04 Feb '19

Hi all, I'd like to propose Ravi Nori as a frontend maintainer for ovirt-engine infra team. While the infra team typically hasn't had a frontend maintainer, Ravi has strong knowledge of all of the frontend infra pieces, including everything related to SSO, welcome page, and GWT in admin portal. Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

5 5

query on running OST
by Pooja Pandey 23 Jan '19

23 Jan '19

Hello Team, Could you please help me in answering a query about OST run.I am trying to run on a virtual machine and it is failing with an error that libvirtError: unsupported configuration: Domain requires KVM, but it is not available. Is it necessary to run this Ovirt System Test on a hypervisor only?Please reply on this so that I can proceed further.Thanks.... Regards, Pooja -- DISCLAIMER - *MSysTechnologies LLC* This email message, contents and its attachments may contain confidential, proprietary or legally privileged information and is intended solely for the use of the individual or entity to whom it is actually intended. If you have erroneously received this message, please permanently delete it immediately and notify the sender. If you are not the intended recipient of the email message,you are notified strictly not to disseminate,distribute or copy this e-mail.E-mail transmission cannot be guaranteed to be secure or error-free as Information could be intercepted, corrupted, lost, destroyed, incomplete or contain viruses and MSysTechnologies LLC accepts no liability for the contents and integrity of this mail or for any damage caused by the limitations of the e-mail transmission.

5 9

SSO with lightdm
by jeremiah52＠naver.com 15 Jan '19

15 Jan '19

I knows there are the GDM plugin and KDM plugin of ovirt-guest-agent that makes SSO in linux is possible. I want to make SSO with lightdm is possble. To add lightdm plugin to ovirt-guest-agent is enough? or something more is needed? I don't know how to develop SSO with lightdm.

3 2

Can we drop fc27 jobs / rpms from CI/tested repos?
by Eyal Edri 13 Jan '19

13 Jan '19

5 8

Please review "dump-chains-sqlite"
by Germano Veit Michel 06 Jan '19

06 Jan '19

Hi, With these 2 changes the ovirt-log-collector will collect storage domain metadata from all storage domains of the environment in a more efficient way. https://gerrit.ovirt.org/#/q/topic:dump-chains-sqlite I'll be away for the next 2 weeks, but reviews are welcome. If there is any problem with one of these patches, please don't merge any of them as they require each other. And if you have extra time, reviews are welcome on this series too =D https://gerrit.ovirt.org/#/q/topic:snapshot-tools Thanks, Germano

2 2

Failed to add host to oVirt
by Eyal Shenitzky 02 Jan '19

02 Jan '19

Hey, I am failing to add a host to oVirt due to the following error: 2018-12-23 11:15:29,482+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment customization': Cannot find a valid baseurl for repo: ovirt -master-centos-gluster5/7Server/x86_64 Does someone encounter this issue? -- Regards, Eyal Shenitzky

2 1

ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Nir Soffer 31 Dec '18

31 Dec '18

Started 2 days 11 hr ago Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-…

4 3

[VDSM] Tests fail because of network timeout
by Nir Soffer 26 Dec '18

26 Dec '18

First time I see this error. The issue seems to be network read timeout when creating virtual env in tox test. If you see this error in your builds, please report. storage-py27 create: /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py27 ERROR: invocation failed (exit code 1), logfile: /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py27/log/storage-py27-0.log ERROR: actionid: storage-py27 msg: getenv cmdargs: ['/usr/bin/python2', '-m', 'virtualenv', '--system-site-packages', '--python', '/usr/bin/python2.7', 'storage-py27'] New python executable in /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py27/bin/python2.7 Also creating executable in /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py27/bin/python Installing setuptools, pip, wheel... Complete output from command /home/jenkins/worksp...e-py27/bin/python2.7 - setuptools pip wheel: The directory '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. The directory '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. Looking in links: /usr/lib/python2.7/site-packages, /usr/lib/python2.7/site-packages/virtualenv_support Collecting setuptools Downloading https://files.pythonhosted.org/packages/37/06/754589caf971b0d2d48f151c2586f… (573kB) Exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/cli/base_command.py", line 143, in main status = self.run(options, args) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/commands/install.py", line 318, in run resolver.resolve(requirement_set) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/resolve.py", line 102, in resolve self._resolve_one(requirement_set, req) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/resolve.py", line 256, in _resolve_one abstract_dist = self._get_abstract_dist_for(req_to_install) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/resolve.py", line 209, in _get_abstract_dist_for self.require_hashes File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/operations/prepare.py", line 283, in prepare_linked_requirement progress_bar=self.progress_bar File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/download.py", line 836, in unpack_url progress_bar=progress_bar File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/download.py", line 673, in unpack_http_url progress_bar) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/download.py", line 897, in _download_http_url _download_url(resp, link, content_file, hashes, progress_bar) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/download.py", line 617, in _download_url hashes.check_against_chunks(downloaded_chunks) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/utils/hashes.py", line 48, in check_against_chunks for chunk in chunks: File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/download.py", line 585, in written_chunks for chunk in chunks: File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/utils/ui.py", line 159, in iter for x in it: File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_internal/download.py", line 574, in resp_read decode_content=False): File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_vendor/urllib3/response.py", line 465, in stream data = self.read(amt=amt, decode_content=decode_content) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_vendor/urllib3/response.py", line 430, in read raise IncompleteRead(self._fp_bytes_read, self.length_remaining) File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__ self.gen.throw(type, value, traceback) File "/usr/lib/python2.7/site-packages/virtualenv_support/pip-18.1-py2.py3-none-any.whl/pip/_vendor/urllib3/response.py", line 345, in _error_catcher raise ReadTimeoutError(self._pool, None, 'Read timed out.') ReadTimeoutError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Read timed out. ---------------------------------------- ...Installing setuptools, pip, wheel...done. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtualenv.py", line 2462, in <module> main() File "/usr/lib/python2.7/site-packages/virtualenv.py", line 762, in main symlink=options.symlink, File "/usr/lib/python2.7/site-packages/virtualenv.py", line 1015, in create_environment install_wheel(to_install, py_executable, search_dirs, download=download) File "/usr/lib/python2.7/site-packages/virtualenv.py", line 968, in install_wheel call_subprocess(cmd, show_stdout=False, extra_env=env, stdin=SCRIPT) File "/usr/lib/python2.7/site-packages/virtualenv.py", line 854, in call_subprocess raise OSError("Command {} failed with error code {}".format(cmd_desc, proc.returncode)) OSError: Command /home/jenkins/worksp...e-py27/bin/python2.7 - setuptools pip wheel failed with error code 2 Running virtualenv with interpreter /usr/bin/python2.7 ERROR: Error creating virtualenv. Note that some special characters (e.g. ':' and unicode symbols) in paths are not supported by virtualenv. Error details: InvocationError('/usr/bin/python2 -m virtualenv --system-site-packages --python /usr/bin/python2.7 storage-py27 (see /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/.tox/storage-py27/log/storage-py27-0.log)', 1) Build: https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st…

1 0

Tests failed because global_setup.sh failed
by Nir Soffer 26 Dec '18

26 Dec '18

Not sure why global setup failed: + [[ ! -O /home/jenkins/.ssh ]] + [[ ! -G /home/jenkins/.ssh ]] + verify_set_permissions 700 /home/jenkins/.ssh + local target_permissions=700 + local path_to_set=/home/jenkins/.ssh ++ stat -c %a /home/jenkins/.ssh + local access=700 + [[ 700 != \7\0\0 ]] + return 0 + [[ -f /home/jenkins/.ssh/known_hosts ]] + verify_set_ownership /home/jenkins/.ssh/known_hosts + local path_to_set=/home/jenkins/.ssh/known_hosts ++ id -un + local owner=jenkins ++ id -gn + local group=jenkins + [[ ! -O /home/jenkins/.ssh/known_hosts ]] + [[ ! -G /home/jenkins/.ssh/known_hosts ]] + verify_set_permissions 644 /home/jenkins/.ssh/known_hosts + local target_permissions=644 + local path_to_set=/home/jenkins/.ssh/known_hosts ++ stat -c %a /home/jenkins/.ssh/known_hosts + local access=644 + [[ 644 != \6\4\4 ]] + return 0 + return 0 + true + log ERROR Aborting. Build: https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st…

4 4

Proposing Nir as ovirt-site storage mainainer
by Nir Soffer 25 Dec '18

25 Dec '18

Nir has done significant work on vdsm and ovirt-imageio, and working recently on incremental backup feature page: https://ovirt.org/develop/release-management/features/storage/incremental-b… For some reason he does not have merge right in ovirt-site project. I think it is time to fix this issue. If we can trust his code we can trust his documentation. Thoughts? Nir

9 12

Re: [VDSM] Tests fail with "missing workspace /home/jenkins/workspace/vdsm_standard-check-patch/vdsm on vm0038.workers-phx.ovirt.org"
by Nir Soffer 22 Dec '18

22 Dec '18

On Fri, Dec 21, 2018 at 1:47 AM Nir Soffer <nsoffer(a)redhat.com> wrote: > Third time today: > > Error: > sh: /home/jenkins/workspace/vdsm_standard-check-patch/vdsm@tmp > /durable-15072b7e/jenkins-result.txt.tmp: > No such file or directory > mv: cannot stat > '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm@tmp > /durable-15072b7e/jenkins-result.txt.tmp': > No such file or directory > missing workspace > /home/jenkins/workspace/vdsm_standard-check-patch/vdsm on > vm0013.workers-phx.ovirt.org > > Build: > > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… Adding devel - if you see this error please report here. On Thu, Dec 20, 2018 at 10:01 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > Two incidents on a different slaves today: > > > > Error: > > sh: /home/jenkins/workspace/vdsm_standard-check-patch/vdsm@tmp > /durable-d993b7a2/jenkins-result.txt.tmp: > > No such file or directory > > mv: cannot stat > > '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm@tmp > /durable-d993b7a2/jenkins-result.txt.tmp': > > No such file or directory > > missing workspace > > /home/jenkins/workspace/vdsm_standard-check-patch/vdsm on > > vm0088.workers-phx.ovirt.org > > > > Build: > > > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… > > > > > > Error: > > sh: /home/jenkins/workspace/vdsm_standard-check-patch/vdsm@tmp > /durable-edec94a0/jenkins-result.txt.tmp: > > No such file or directory > > mv: cannot stat > > '/home/jenkins/workspace/vdsm_standard-check-patch/vdsm@tmp > /durable-edec94a0/jenkins-result.txt.tmp': > > No such file or directory > > missing workspace > > /home/jenkins/workspace/vdsm_standard-check-patch/vdsm on > > vm0013.workers-phx.ovirt.org > > > > Build: > > > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… > > > > On Wed, Dec 19, 2018 at 4:36 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > > > I have seen this before, very strange failure. > > > > > > The job run normally and then abort when we start to run the tests. > The error > > > does not come from our tests. > > > > > > Error: > > > ../tests/run_tests_local.sh API_test.py alignmentscan_test.py > > > api_response_test.py bridge_test.py caps_test.py client_test.py > > > clientif_test.py cmdutils_test.py config_test.py cpu_profile_test.py > > > cpuinfo_test.py domcaps_test.py encoding_test.py exception_test.py > > > executor_test.py eventfd_test.py fallocate_test.py filecontrol_test.py > > > fuser_test.py glob_test.py gluster_cli_test.py > > > gluster_exception_test.py glusterTestData.py > > > gluster_thinstorage_test.py hooks_test.py hostdev_test.py > > > hoststats_test.py hugepages_test.py hwinfo_test.py jobs_test.py > > > jsonRpcClient_test.py jsonrpc_test.py loopback_test.py mkimage_test.py > > > modprobe.py moduleloader_test.py monkeypatch_test.py mom_test.py > > > mompolicy_test.py osinfo_test.py osutils_test.py passwords_test.py > > > permutation_test.py protocoldetector_test.py response_test.py > > > rngsources_test.py schedule_test.py schemavalidation_test.py > > > sigutils_test.py sparsify_test.py stompadapter_test.py > > > stompasyncclient_test.py stompasyncdispatcher_test.py stomp_test.py > > > sysprep_test.py taskset_test.py testlib_test.py tool_confmeta_test.py > > > tool_test.py throttledlog_test.py unicode_test.py utils_test.py > > > validate_test.py vdsmapi_test.py vdsmdumpchains_test.py verify.py > > > vmapi_test.py vmfakelib_test.py vmTestsData.py zombiereaper_test.py > > > network/*_test.py devices/parsing/complex_vm_test.py > > > common/cache_test.py common/cmdutils_test.py common/concurrent_test.py > > > common/contextlib_test.py common/fileutils_test.py > > > common/function_test.py common/hostutils_test.py > > > common/libvirtconnection_test.py common/logutils_test.py > > > common/network_test.py common/osutils_test.py common/proc_test.py > > > common/properties_test.py common/pthread_test.py common/time_test.py > > > common/validate_test.py > > > > > > missing workspace > > > /home/jenkins/workspace/vdsm_standard-check-patch/vdsm on > > > vm0038.workers-phx.ovirt.org > > > > > > > > > Build: > > > > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… >

1 2

[VDSM] all test passed, build failed with "tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it"
by Nir Soffer 21 Dec '18

21 Dec '18

We have this failure that pops randomly: 1. All tests pass *00:13:13.284* ___________________________________ summary ____________________________________*00:13:13.285* tests: commands succeeded*00:13:13.286* storage-py27: commands succeeded*00:13:13.286* storage-py36: commands succeeded*00:13:13.286* lib-py27: commands succeeded*00:13:13.287* lib-py36: commands succeeded*00:13:13.288* network-py27: commands succeeded*00:13:13.290* network-py36: commands succeeded*00:13:13.291* virt-py27: commands succeeded*00:13:13.292* virt-py36: commands succeeded*00:13:13.293* congratulations :) 2. But we fail to collect logs at the end *00:14:35.992* ##########################################################*00:14:35.995* ## Wed Nov 28 17:39:50 UTC 2018 Finished env: fc28:fedora-28-x86_64*00:14:35.996* ## took 764 seconds*00:14:35.997* ## rc = 1*00:14:35.997* ##########################################################*00:14:36.009* ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv*00:14:36.010* ##! Last 20 log entries: /tmp/mock_logs.Lcop4ZOq/script/stdout_stderr.log*00:14:36.011* ##!*00:14:36.012* journal/b087148aba6d49b9bbef488e52a48752/system.journal*00:14:36.013* tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it*00:14:36.014* journal/b087148aba6d49b9bbef488e52a48752/user-1000.journal*00:14:36.015* lastlog*00:14:36.015* libvirt/*00:14:36.015* libvirt/lxc/*00:14:36.015* libvirt/libxl/*00:14:36.016* libvirt/qemu/*00:14:36.016* libvirt/qemu/LiveOS-f920001d-be4e-47ea-ac26-72480fd5be87.log*00:14:36.017* libvirt/uml/*00:14:36.017* ovirt-guest-agent/*00:14:36.017* ovirt-guest-agent/ovirt-guest-agent.log*00:14:36.017* README*00:14:36.018* samba/*00:14:36.018* samba/old/*00:14:36.018* sssd/*00:14:36.018* tallylog*00:14:36.018* wtmp*00:14:36.018* Took 678 seconds*00:14:36.018* ===================================*00:14:36.019* ##!*00:14:36.019* ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^*00:14:36.019* ##!######################################################## This looks like an issue with vdsm check-patch.sh: function collect_logs { res=$? [ "$res" -ne 0 ] && echo "*** err: $res" cd /var/log tar -cvzf "$EXPORT_DIR/mock_varlogs.tar.gz" * cd /var/host_log tar -cvzf "$EXPORT_DIR/host_varlogs.tar.gz" * } trap collect_logs EXIT Seems that tar fail to collect log if the log is modified while copied, which makes sense. We can ignore errors in tar, since log collection should not fail the build, but I think a better solution is to avoid collecting any logs since vdsm writes its own logs during tests - all the info must be in vdsm log. Here is the list of collected logs: *00:13:47.280* + tar -cvzf /home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/exported-artifacts/mock_varlogs.tar.gz btmp dnf.librepo.log dnf.log dnf.rpm.log faillog glusterfs hawkey.log journal lastlog libvirt openvswitch README tallylog vdsm_tests.log wtmp yum.log*00:13:47.285* btmp*00:13:47.285* dnf.librepo.log*00:13:47.299* dnf.log*00:13:47.309* dnf.rpm.log*00:13:47.310* faillog*00:13:47.311* glusterfs/*00:13:47.312* hawkey.log*00:13:47.313* journal/*00:13:47.313* lastlog*00:13:47.315* libvirt/*00:13:47.315* libvirt/qemu/*00:13:47.316* openvswitch/*00:13:47.317* openvswitch/ovs-vswitchd.log*00:13:47.318* openvswitch/ovsdb-server.log*00:13:47.319* README*00:13:47.320* tallylog*00:13:47.321* vdsm_tests.log*00:13:47.342* wtmp*00:13:47.343* yum.log*00:13:47.349* + cd /var/host_log*00:13:47.350* + tar -cvzf /home/jenkins/workspace/vdsm_master_check-patch-fc28-x86_64/vdsm/exported-artifacts/host_varlogs.tar.gz anaconda audit boot.log btmp chrony cloud-init.log cloud-init-output.log cron dnf.librepo.log dnf.log dnf.rpm.log firewalld glusterfs hawkey.log journal lastlog libvirt ovirt-guest-agent README samba sssd tallylog wtmp*00:13:47.356* anaconda/*00:13:47.356* anaconda/ifcfg.log*00:13:47.357* anaconda/ks-script-l5qnynnj.log*00:13:47.358* anaconda/storage.log*00:13:47.359* anaconda/program.log*00:13:47.395* anaconda/ks-script-b5_08tmo.log*00:13:47.396* anaconda/ks-script-6uks8bp3.log*00:13:47.397* anaconda/hawkey.log*00:13:47.398* anaconda/syslog*00:13:47.406* anaconda/journal.log*00:13:47.449* anaconda/dnf.librepo.log*00:13:47.458* anaconda/packaging.log*00:13:47.465* anaconda/dbus.log*00:13:47.466* anaconda/anaconda.log*00:13:47.467* anaconda/ks-script-slrcz39_.log*00:13:47.503* audit/*00:13:47.504* audit/audit.log.3*00:13:47.657* audit/audit.log.2*00:13:47.814* audit/audit.log.1*00:13:47.981* audit/audit.log*00:13:48.008* audit/audit.log.4*00:13:48.155* boot.log*00:13:48.156* btmp*00:13:48.157* chrony/*00:13:48.159* cloud-init.log*00:13:48.159* cloud-init-output.log*00:13:48.161* cron*00:13:48.162* dnf.librepo.log*00:13:49.930* dnf.log*00:13:51.335* dnf.rpm.log*00:13:51.421* firewalld*00:13:51.423* glusterfs/*00:13:51.424* hawkey.log*00:13:51.704* journal/*00:13:51.708* journal/b087148aba6d49b9bbef488e52a48752/*00:13:51.709* journal/b087148aba6d49b9bbef488e52a48752/system.journal*00:13:55.817* tar: journal/b087148aba6d49b9bbef488e52a48752/system.journal: file changed as we read it*00:13:55.819* journal/b087148aba6d49b9bbef488e52a48752/user-1000.journal*00:13:55.915* lastlog*00:13:55.923* libvirt/*00:13:55.924* libvirt/lxc/*00:13:55.926* libvirt/libxl/*00:13:55.927* libvirt/qemu/*00:13:55.928* libvirt/qemu/LiveOS-f920001d-be4e-47ea-ac26-72480fd5be87.log*00:13:55.929* libvirt/uml/*00:13:55.930* ovirt-guest-agent/*00:13:55.930* ovirt-guest-agent/ovirt-guest-agent.log*00:13:55.932* README*00:13:55.933* samba/*00:13:55.933* samba/old/*00:13:55.935* sssd/*00:13:55.935* tallylog*00:13:55.935* wtmp Most if not all are lot relevant to vdsm tests, and should not be collected. This was added in: commit 9c9c17297433e5a5a49aa19cde10b206e7db61e9 Author: Edward Haas <edwardh(a)redhat.com> Date: Tue Apr 17 10:53:11 2018 +0300 automation: Collect logs even when check-patch fails Change-Id: Idfe07ce6fc55473b1db1d7f16754f559cc5c345a Signed-off-by: Edward Haas <edwardh(a)redhat.com> Reviewed in: https://gerrit.ovirt.org/c/90370 Edward, can you explain why do we need to collect logs during check-patch, and why do we need to collect all the logs in the system? Nir

3 13

[Ovirt] [CQ weekly status] [21-12-2018]
by Dafna Ron 21 Dec '18

21 Dec '18

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.2*: GREEN (#3) Last job failure was on Dec 11th (i.e no failures reported in the last 10 days for 4.2) *CQ-Master:* RED (#1) Project: ALL Reason: we have an active regression: https://ovirt-jira.atlassian.net/browse/OVIRT-2634 Fix has been merged and waiting to pass CQ: https://gerrit.ovirt.org/#/c/96371/ Please note: Due to the shut down and holidays, the next report will be sent on Jan 11th Happy Holidays! Dafna ------------------------------------------------------------------------------------------------------------------- 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)

1 0

planned datacenter maintenance 21.12.2018 20:30 UTC
by Evgheni Dereveanchin 20 Dec '18

20 Dec '18

Hi everyone, The network switch stack used by the oVirt PHX datacenter needs a reboot which is scheduled for tomorrow. It is expected to be a fast task yet it may cut all networking including shared storage access for all of our hypervisors for a couple of minutes. For this reason I'll shut down non-critical services beforehand and pause CI to minimize I/O activity and protect against potential VM disk corruption. Maintenance window: 21.12.2018 20:30 UTC - 21:30 UTC Services that may be unreachable for short periods of time during this outage are: * Package repositories * Glance image repository * Jenkins CI Other services such as the website, gerrit and mailing lists are not affected and will be operating as usual. -- Regards, Evgheni Dereveanchin

1 0

Failure while trying to setup master
by Shani Leviim 20 Dec '18

20 Dec '18

Hi, I've fetched & rebased ovirt-engine master, but got into this error message while trying to run the setup: [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/home/sleviim/ovirt-engine/share/ovirt-engine/dbscripts/upgrade/04_03_0590_remove_maintenance_and_optional_reason_required.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed Can anyone assist, please? *Regards,* *Shani Leviim*

2 1

Adding multiple VM NICs or VM tags in a single request
by Mahesh Falmari 20 Dec '18

20 Dec '18

Hi Nir and RedHat Team, Would like to confirm if it is possible to create multiple VM tags or multiple VM NICs in a single POST request. Currently, I could see that a single request creates a single VM NIC or VM tag for a given virtual machine. We are using the following APIs but looks like it doesn’t allows us to add multiple VM NICs or VM tags in a single request. If it is possible, please let us know how the request body should look like in that case. POST /vms/{vm:id}/tags Request body: <tags> <name>tag1</name> </tags> POST /vms/{vm:id}/nics Request body: <nic> <name>network1</name> </nic> Thanks & Regards, Mahesh Falmari

3 4

[TEST NEEDED] Please test oVirt with Gluster 5
by Sandro Bonazzola 20 Dec '18

20 Dec '18

Hi Sahina, can your team please test oVirt with Gluster 5? Waiting for test results in order to merge https://gerrit.ovirt.org/#/c/95833/ Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

4 4

Nominate Dominik Holler to have a merge permissions on ovirt-site
by Michael Burman 20 Dec '18

20 Dec '18

Hi All, I would like to suggest the nomination of Dominik Holler to have and get a merge permissions on ovirt-site. Dominik is a professional member and developer in our ovirt community and organization. His contribution to ovirt is huge and i believe that he is an appropriate nomination to receive such permissions. Thank you) -- Michael Burman Senior Quality engineer - rhv network - redhat israel Red Hat <https://www.redhat.com> mburman(a)redhat.com M: 0545355725 IM: mburman <https://red.ht/sig>

3 2

Update to latest master failed with Failed to execute stage 'Setup validation': 'changed'
by Michael Burman 20 Dec '18

20 Dec '18

Hi I'm trying to update the latest master version 4.3.0-0.4.master.20181219115514.git1d803c4.el7 and on engine-setup i get: [ ERROR ] Failed to execute stage 'Setup validation': 'changed' 2018-12-20 08:44:50,803+0200 DEBUG otopi.context context._executeMethod:128 Stage validation METHOD otopi.plugins.ovirt_engine_common.base.core.uninstall.Plugin._validatio n_changed_files 2018-12-20 08:44:50,819+0200 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core/uninstall.py", line 247, in _validation_changed_files if info['changed'] KeyError: 'changed' 2018-12-20 08:44:50,821+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Setup validation': 'changed' Known issue? Thanks, -- Michael Burman Senior Quality engineer - rhv network - redhat israel Red Hat <https://www.redhat.com> mburman(a)redhat.com M: 0545355725 IM: mburman <https://red.ht/sig>

2 3

Fwd: oVirt infra weekly meeting notes 19.12.2018
by Eyal Edri 19 Dec '18

19 Dec '18

---------- Forwarded message --------- From: Evgheni Dereveanchin <ederevea(a)redhat.com> Date: Wed, Dec 19, 2018 at 3:39 PM Subject: oVirt infra weekly meeting notes 19.12.2018 To: infra <infra(a)ovirt.org> Hi everyone, Please find this week's infra updates below: PHX: - Jenkins - Core and plugins updated - JVM optimizations enabled - SSE gateway mem leak still not fixed - Dropping sessions from /monitoring helps with load - RAM upgraded on 4 bare metals, 6 to go - oVirt 4.2.7 upgrade started OSAS: - Network issues in community cage still being investigated AI: - Review hawkular in OpenShift - Review SSL facilities for OpenShift -- Regards, Evgheni Dereveanchin _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-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/infra@ovirt.org/message/ZNUMSNQKXNSP2… -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

planned Jenkins restart
by Evgheni Dereveanchin 18 Dec '18

18 Dec '18

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

1 1

[Ovirt] [CQ weekly status] [14-12-2018]
by Dafna Ron 16 Dec '18

16 Dec '18

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.2*: GREEN (#1) Last job failure was on Dec 11th. Project: ovirt-engine Reason: infra related failure *CQ-Master:* GREEN (#1) Last job failure was on Dec 13th Project: vdsm Reason: failed package build cause CQ to fail to run. the package build failure was infra related and a new package was successfully built and tested after this failure. Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- 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)

2 1

4.2 CI failure on qemu-io tests
by Milan Zamazal 14 Dec '18

14 Dec '18

Hi, I've seen a CI failure on qemu-io tests in ovirt-4.2 branch: http://jenkins.ovirt.org/job/vdsm_standard-check-patch/602/ It fails only in some testing parts, while in others it succeeds: http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-el7-x86_64/553/ Nir, could you please take a look whether we need to backport your fix from master and/or fix anything else (such as ensuring the right QEMU version is used)? Thanks, Milan

2 3