- Infra - oVirt List Archives

[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
by danken (oVirt JIRA) 05 Jun '18

05 Jun '18

danken created OVIRT-2136: ----------------------------- Summary: Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer Key: OVIRT-2136 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra Please add Milan to vdsm-maintainers list. ---------- Forwarded message ---------- From: Edward Haas <ehaas(a)redhat.com> Date: Mon, Jun 4, 2018 at 3:35 PM Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer To: "devel(a)ovirt.org" <devel(a)ovirt.org> Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas <edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg <danken(a)redhat.com> +1 Thanks, Edy. > On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote: > > Approved. > > On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski > <piotr.kliczewski(a)gmail.com> wrote: >> +1 >> >>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote: >>> >>> >>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> >>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com> >>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> Milan Zamazal has been working on the oVirt project for more than 2.5 >>>>> years. >>>>> Let me highlight some of his many contributions to the project: >>>>> >>>>> - Since January this year - 2018, he's been a maintainer for the stable >>>>> branches. >>>>> - He developed important features like memory hotunplug, which required >>>>> tight cooperation >>>>> and communication with the other layers of the stack (libvirt, qemu). >>>>> - He is a mentor in the Outreachy program, which lead to creation of the >>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer >>>>> - He contributed more than 290 patches to the Vdsm project in master >>>>> branch alone, excluding backports and contributions to Engine >>>>> - He contributed and is contributing testcases and fixes to the oVirt >>>>> System Test suite, a tool which was already pivotal in ensuring the >>>>> quality of the oVirt project. >>>>> >>>>> As reviewer, Milan is responsive and his comments are always >>>>> comprehensive and well focused, >>>>> with strong attitude towards getting things done and done right. >>>>> >>>>> Milan also demonstrated his ability to adapt to the needs of the project: >>>>> - he demonstrated careful and thoughtful patch management while >>>>> maintaining the stable branches >>>>> - he also demonstrated he's not shy to tackle large and needed changes >>>>> during the 4.1 and 4.2 cycles, >>>>> when we deeply reorganized the XML processing in the virt code. >>>>> >>>>> For those reasons, and many more, I think he will be a good addition to >>>>> the maintainers team, and I propose him as virt co-maintainer. >>>>> >>>>> Please share your thoughts >>>> >>>> >>>> +1 >>> >>> >>> FWIW, +1 >>> >>>> >>>> >>>> Nir >>>> >>>> >>>> _______________________________________________ >>>> Devel mailing list -- devel(a)ovirt.org >>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QELJ7YNZVW65H… >>>> >>> >>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YIMB6QHQ37DVL… >>> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YBK7IHQELSEFN… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Gal Ben Haim (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-1834: ------------------------------------- I don't see any valid solution from OST side. [~bkorren(a)redhat.com] [~dbelenky(a)redhat.com] any idea how we can solve it? I know that signal handling in Jenkins is a difficult task. Maybe let's change the job to wipe the workspace before running git? > 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#100087)

1 0

[CQ]: 91821, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

A system test invoked by the "ovirt-master" change queue including change 91821,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91888,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91888,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91821/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91888/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8048/

1 0

[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2076: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > name clash on vdsm module at host-deploy > ---------------------------------------- > > Key: OVIRT-2076 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2076 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > Add host is failing and was reported by gal for hc > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > (Relevant) error snippet from the host deploy log: > <error> > 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None) > 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported > 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf > _('Cannot resolve ovirt_hosted_engine_ha module') > RuntimeError: Cannot resolve ovirt_hosted_engine_ha module -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy
by Dafna Ron (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2076: ---------------------------------- Both passed on CQ and the vdsm build was fixed. > name clash on vdsm module at host-deploy > ---------------------------------------- > > Key: OVIRT-2076 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2076 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > Add host is failing and was reported by gal for hc > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > (Relevant) error snippet from the host deploy log: > <error> > 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None) > 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported > 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf > _('Cannot resolve ovirt_hosted_engine_ha module') > RuntimeError: Cannot resolve ovirt_hosted_engine_ha module -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2135) On failure we collect the logs from the VMs twice
by Gal Ben Haim (oVirt JIRA) 05 Jun '18

05 Jun '18

Gal Ben Haim created OVIRT-2135: ----------------------------------- Summary: On failure we collect the logs from the VMs twice Key: OVIRT-2135 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2135 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra The first collection is done by `LogCollector` nose plugin (this plugin is defined in ovirtlago.testlib) The second collection is done by `env_collect` in the `control.sh` script of the suite. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-master" system tests
by oVirt Jenkins 05 Jun '18

05 Jun '18

Change 82632,1 (py2exe-py2.7) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/82632/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8046/

1 0

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Jun '18

05 Jun '18

Change 82632,1 (py2exe-py2.7) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/82632/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2293/

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1550
by jenkins＠jenkins.phx.ovirt.org 05 Jun '18

05 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1550/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 5cb82835887b96781c1ec5514c0309078f60d3f2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5cb82835887b96781c1ec5514c0309078f60d3f2 Commit message: "cockpit-ovirt: Move to fc28 and exclude 4.2 on fc28" > git rev-list --no-walk 5cb82835887b96781c1ec5514c0309078f60d3f2 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins879410915074091692.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by sbonazzo (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2078: --------------------------------- Note that https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… says also: bq. "For CI systems that must verify private changes, a special permission can be granted (View Private Changes). In that case, care should be taken to prevent the CI system from exposing secret details." so we should research also for a jenkins plugin which allows to test such private change without exposing it. > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0