- Infra - oVirt List Archives

[JIRA] (OVIRT-2545) Fwd: [ovirt-users] Backport KVM bug fix for nested KVM in ESXi and Hyper-V
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2545?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2545: -------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) Hi Duck, Can you check if this is still needed? > Fwd: [ovirt-users] Backport KVM bug fix for nested KVM in ESXi and Hyper-V > -------------------------------------------------------------------------- > > Key: OVIRT-2545 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2545 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Marc Dequènes (Duck) > > Opening a ticket because looks like the forwarded email doesn't show up on > list archives at > https://lists.ovirt.org/archives/list/users@ovirt.org/2018/10/ > Marc can you please check? > ---------- Forwarded message --------- > From: Gianluca Cecchi <gianluca.cecchi(a)gmail.com> > Date: mar 16 ott 2018 alle ore 12:57 > Subject: [ovirt-users] Backport KVM bug fix for nested KVM in ESXi and > Hyper-V > To: users <users(a)ovirt.org> > Hello, > I send a dedicated subject message on this topic. > Also, the reply to my other related message seems not visible inside list > archive page for some reason. > It seems this nasty problem in nested virt using pc-i440fx-rhel7.X.0 > machine type with X >= 3 impacts not only vSphere as main hypervisor for > nested KVM, but other hypervisors too (Hyper-V) and other machine types too > and could be due to a bug in KVM, so in the kernel, if I understood > correctly. > According to this link below > https://bugs.launchpad.net/qemu/+bug/1636217 > and its comment by Roman Kagan in June this year: > " > This is a KVM bug. It has been fixed in mainstream Linux in > commit d391f1207067268261add0485f0f34503539c5b0 > Author: Vitaly Kuznetsov <email address hidden> > Date: Thu Jan 25 16:37:07 2018 +0100 > x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when > running nested > I was investigating an issue with seabios >= 1.10 which stopped working > for nested KVM on Hyper-V. The problem appears to be in > handle_ept_violation() function: when we do fast mmio we need to skip > the instruction so we do kvm_skip_emulated_instruction(). This, however, > depends on VM_EXIT_INSTRUCTION_LEN field being set correctly in VMCS. > However, this is not the case. > Intel's manual doesn't mandate VM_EXIT_INSTRUCTION_LEN to be set when > EPT MISCONFIG occurs. While on real hardware it was observed to be set, > some hypervisors follow the spec and don't set it; we end up advancing > IP with some random value. > I checked with Microsoft and they confirmed they don't fill > VM_EXIT_INSTRUCTION_LEN on EPT MISCONFIG. > Fix the issue by doing instruction skip through emulator when running > nested. > Fixes: 68c3b4d1676d870f0453c31d5a52e7e65c7448ae > Suggested-by: Radim Krčmář <email address hidden> > Suggested-by: Paolo Bonzini <email address hidden> > Signed-off-by: Vitaly Kuznetsov <email address hidden> > Acked-by: Michael S. Tsirkin <email address hidden> > Signed-off-by: Radim Krčmář <email address hidden> > Although the commit mentions Hyper-V as L0 hypervisor, the same problem > pertains to ESXi. > The commit is included in v4.16. > " > Is it possible to backport the fix to the kernel provided by plain > RHEL/CentOS hosts and/or RHVH/ovirt-ng nodes? > Thanks, > Gianluca > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/message/V6PLM7USQ4WJX… > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> > <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2547) Fedora 28/rawhide job fail with: "Job for systemd-journald.service failed"
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2547?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2547: ----------------------------- Resolution: Done Status: Done (was: To Do) no reply from requestor, please reopen if needed. > Fedora 28/rawhide job fail with: "Job for systemd-journald.service failed" > -------------------------------------------------------------------------- > > Key: OVIRT-2547 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2547 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > These jobs failed without running any test and no logs were collected. > 1. 00:04:17.045 [check-patch.fc28.x86_64] Job for systemd-journald.service > failed. See "systemctl status systemd-journald.service" and "journalctl > -xe" for details. > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/617/consol… > 2. 00:01:40.814 [check-patch.fcraw.x86_64] Job for systemd-journald.service > failed because a fatal signal was delivered to the control process. See > "systemctl status systemd-journald.service" and "journalctl -xe" for > details. > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/618/consol… > 3. 00:07:15.919 [check-patch.fc28.x86_64] Job for systemd-journald.service > failed because a fatal signal was delivered to the control process. See > "systemctl status systemd-journald.service" and "journalctl -xe" for > details. > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/627/consol… > Can we flag this kind of failure as CI error instead of test failure? > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2556: ---------------------------------- Is this still happening? [~dbelenky(a)redhat.com] [~bkorren(a)redhat.com]? > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Roman Mohr > Assignee: infra > Priority: High > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-1840) jobs freeze due to unresponsive docker
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1840?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1840: ---------------------------------- Is it still happening? > jobs freeze due to unresponsive docker > -------------------------------------- > > Key: OVIRT-1840 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1840 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > Quite often do I see jobs stuck at various stages for hours that seem related to docker. > Example: > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc26-x86_6… > There's multiple docker commands stuck on the slave (will post in the next comment) so it seems to be deadlocked. Opening ticket to investigate which step exactly is causing this and possible ways of resolving. The job in question doesn't even use docker so shouldn't suffer if this happens. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-1832) Vdsm make install on fc27 fails with "package vdsm-... is disabled"
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1832?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1832: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > Vdsm make install on fc27 fails with "package vdsm-... is disabled" > ------------------------------------------------------------------- > > Key: OVIRT-1832 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1832 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Never seen this error, can anyone explain it? > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/578/console > *00:13:42.747* Problem 1: conflicting requests*00:13:42.747* - > nothing provides vdsm-hook-vmfex-dev = 4.20.11-12.git7f9589a1f.fc27 > needed by vdsm-4.20.11-12.git7f9589a1f.fc27.x86_64*00:13:42.747* > Problem 2: conflicting requests*00:13:42.747* - nothing provides > vdsm-python = 4.20.11-12.git7f9589a1f.fc27 needed by > vdsm-client-4.20.11-12.git7f9589a1f.fc27.noarch*00:13:42.747* Problem > 3: conflicting requests*00:13:42.747* - package > vdsm-gluster-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.748* Problem 4: conflicting requests*00:13:42.748* > - package vdsm-hook-allocate_net-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.748* Problem 5: conflicting > requests*00:13:42.748* - package > vdsm-hook-boot_hostdev-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.748* Problem 6: conflicting requests*00:13:42.748* > - package vdsm-hook-checkimages-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.748* Problem 7: conflicting > requests*00:13:42.748* - package > vdsm-hook-checkips-4.20.11-12.git7f9589a1f.fc27.x86_64 is > disabled*00:13:42.748* Problem 8: conflicting requests*00:13:42.748* > - package vdsm-hook-cpuflags-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.748* Problem 9: conflicting requests*00:13:42.748* > - package vdsm-hook-diskunmap-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.749* Problem 10: conflicting requests*00:13:42.749* > - package vdsm-hook-ethtool-options-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.749* Problem 11: conflicting > requests*00:13:42.749* - package > vdsm-hook-extnet-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.749* Problem 12: conflicting requests*00:13:42.749* > - package vdsm-hook-extra-ipv4-addrs-4.20.11-12.git7f9589a1f.fc27.x86_64 > is disabled*00:13:42.749* Problem 13: conflicting > requests*00:13:42.749* - package > vdsm-hook-fakesriov-4.20.11-12.git7f9589a1f.fc27.x86_64 is > disabled*00:13:42.749* Problem 14: conflicting requests*00:13:42.749* > - package vdsm-hook-fakevmstats-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.749* Problem 15: conflicting > requests*00:13:42.749* - package > vdsm-hook-faqemu-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.750* Problem 16: conflicting requests*00:13:42.750* > - package vdsm-hook-fcoe-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.750* Problem 17: conflicting requests*00:13:42.750* > - package vdsm-hook-fileinject-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.750* Problem 18: conflicting > requests*00:13:42.750* - package > vdsm-hook-floppy-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.750* Problem 19: conflicting requests*00:13:42.750* > - package vdsm-hook-httpsisoboot-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.750* Problem 20: conflicting > requests*00:13:42.750* - package > vdsm-hook-ipv6-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.750* Problem 21: conflicting requests*00:13:42.750* > - package vdsm-hook-isolatedprivatevlan-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.751* Problem 22: conflicting > requests*00:13:42.751* - package > vdsm-hook-localdisk-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.751* Problem 23: conflicting requests*00:13:42.751* > - package vdsm-hook-macbind-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.751* Problem 24: conflicting requests*00:13:42.751* > - package vdsm-hook-macspoof-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.751* Problem 25: conflicting requests*00:13:42.751* > - package vdsm-hook-nestedvt-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.751* Problem 26: conflicting requests*00:13:42.751* > - package vdsm-hook-noipspoof-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.751* Problem 27: conflicting requests*00:13:42.751* > - package vdsm-hook-numa-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.752* Problem 28: conflicting requests*00:13:42.752* > - package vdsm-hook-openstacknet-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.752* Problem 29: conflicting > requests*00:13:42.752* - package > vdsm-hook-pincpu-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.752* Problem 30: conflicting requests*00:13:42.752* > - package vdsm-hook-promisc-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.752* Problem 31: conflicting requests*00:13:42.752* > - package vdsm-hook-qemucmdline-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.752* Problem 32: conflicting > requests*00:13:42.752* - package > vdsm-hook-qos-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.752* Problem 33: conflicting requests*00:13:42.752* > - package vdsm-hook-scratchpad-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.753* Problem 34: conflicting > requests*00:13:42.753* - package > vdsm-hook-smbios-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.753* Problem 35: conflicting requests*00:13:42.753* > - package vdsm-hook-spiceoptions-4.20.11-12.git7f9589a1f.fc27.noarch > is disabled*00:13:42.753* Problem 36: conflicting > requests*00:13:42.753* - package > vdsm-hook-vfio-mdev-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.753* Problem 37: conflicting requests*00:13:42.753* > - package vdsm-hook-vhostmd-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.753* Problem 38: conflicting requests*00:13:42.753* > - package vdsm-hook-vmdisk-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.753* Problem 39: conflicting requests*00:13:42.754* > - package vdsm-hook-vmfex-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.754* Problem 40: conflicting requests*00:13:42.754* > - package vdsm-hook-vmfex-dev-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.754* Problem 41: conflicting requests*00:13:42.754* > - package vdsm-http-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.754* Problem 42: conflicting requests*00:13:42.754* > - package vdsm-jsonrpc-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.754* Problem 43: conflicting requests*00:13:42.754* > - package vdsm-network-4.20.11-12.git7f9589a1f.fc27.x86_64 is > disabled*00:13:42.754* Problem 44: conflicting requests*00:13:42.754* > - package vdsm-python-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.754* Problem 45: conflicting requests*00:13:42.755* > - package vdsm-tests-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled*00:13:42.755* Problem 46: conflicting requests*00:13:42.755* > - package vdsm-yajsonrpc-4.20.11-12.git7f9589a1f.fc27.noarch is > disabled -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-1874) Manual building UI
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1874?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1874: ----------------------------- Resolution: Incomplete Status: Done (was: To Do) not reply from the requestor, please reopen with more info if its still needed. > Manual building UI > ------------------ > > Key: OVIRT-1874 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1874 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Lev Veyde > Assignee: infra > Labels: builds, releases > > Hi, > We need the interface to be able to do manual builds from specific refs > (i.e. tag/hash) for the projects. > Thanks, > -- > Lev Veyde > Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1427: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) Yes, there can be occasions of dependency issues, but they are not common. We don't have plans currently to introduce a dependency management in CI, due to lack of resources and other priorities. If this will become possible in the future, we'll consider revisiting this. > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1834: ---------------------------------- [~gbenhaim@redhat.com][~grosenth@redhat.com] can this failure still happen or with the latest lago release its fixed? > Jenkins failure - perhaps bad permissions > ----------------------------------------- > > Key: OVIRT-1834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… > *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01* > hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at > org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01* > at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at > hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01* > at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01* > at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01* > at hudson.model.Run.execute(Run.java:1724)*10:53:01* at > hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at > hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01* > at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by: > hudson.plugins.git.GitException: Command "git clean -fdx" returned > status code 1:*10:53:01* stdout: Removing > basic-suite-master/LagoInitFile*10:53:01* Removing > basic-suite-master/extra_sources*10:53:01* Removing > basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing > basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01* > Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing > basic-suite-master/test_utils/constants.pyc*10:53:01* Removing > basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing > exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01* > Removing mock_script_sid.x4jv1R*10:53:01* Removing > mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning: > failed to remove .pki/*10:53:01* warning: failed to remove > deployment-basic-suite-master/default/uuid*10:53:01* warning: failed > to remove deployment-basic-suite-master/default/id_rsa > ... > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1873: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Vdsm fcraw builds fail because ovirt-imageio-common is not installed > -------------------------------------------------------------------- > > Key: OVIRT-1873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We require the package: > $ grep ovirt-imageio-common automation/check-patch.packages.fcraw > ovirt-imageio-common > Here are few failing builds, we have more: > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… > *00:03:25.311* =================================== FAILURES > ===================================*00:03:25.311* > _________________________ test_import[vdsm.kvm2ovirt] > __________________________*00:03:25.312* *00:03:25.312* name = > 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* > @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def > test_import(name):*00:03:25.313* try:*00:03:25.313* > > importlib.import_module(name)*00:03:25.313* *00:03:25.313* > check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* > /usr/lib64/python2.7/importlib/__init__.py:37: in > import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ *00:03:25.315* *00:03:25.315* from __future__ import > absolute_import*00:03:25.315* *00:03:25.315* import > argparse*00:03:25.315* from contextlib import > contextmanager*00:03:25.315* import itertools*00:03:25.315* > import sys*00:03:25.316* import threading*00:03:25.316* > *00:03:25.316* > from ovirt_imageio_common import > directio*00:03:25.316* E ImportError: No module named > ovirt_imageio_common*00:03:25.316* *00:03:25.316* > ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 > failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2023) mailing lists footer macros are broken
by Eyal Edri (oVirt JIRA) 15 Dec '18

15 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2023?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2023: ----------------------------- Resolution: Duplicate Status: Done (was: To Do) > mailing lists footer macros are broken > -------------------------------------- > > Key: OVIRT-2023 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2023 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > Attachments: signature.asc > > > mailing lists footer macros are broken. Examples: > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0