- Infra - oVirt List Archives

[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

[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: --------------------------------- User story: A researcher find a vulnerability in one of the oVirt packages. A CVE is opened and an embargo date is acknowledged between researcher, oVirt package maintainer and downstream vendors. Between report and embargo date, oVirt package maintainer must be able to push a patch to gerrit as a private patch, getting it reviewed by a restricted number of people and get it ready for being merged immediately on embargo lift, when the vulnerability will be disclosed to public, in order to issue an immediate release right after the merge. > 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

[JIRA] (OVIRT-2074) missing dependency for python-isort
by sbonazzo (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2074?page=com.atlassian.jira.… ] sbonazzo reassigned OVIRT-2074: ------------------------------- Assignee: sbonazzo (was: infra) > missing dependency for python-isort > ----------------------------------- > > Key: OVIRT-2074 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2074 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: sbonazzo > Labels: cq-issue-traking, ost_failures > > need to change fc27 to fc28 to fix the failures. > Sandro submitted a change for some projects but some are still missing. > Sandro: > Fix is here: https://gerrit.ovirt.org/91769 ; needs an engine to be built on fedora to pass CI, I'm on it. > Going on failures, I will help him with the change for failed projects build-artifacts with the same issue. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91378, 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 91378,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/91378/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/8041/

1 0

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

04 Jun '18

A system test invoked by the "ovirt-master" change queue including change 91841,7 (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/91841/7 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/8037/

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 228 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Jun '18

04 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/228/ Build Number: 228 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #228 [Milan Zamazal] Use Cirros 0.4.0 for cluster versions < 4.1 [Yuval Turgeman] system-tests: added he-node-ng-master suite [Barak Korren] Fix mock_cleanup.sh trying to umount bad things [Barak Korren] Switch fabric-ovirt to STDCI v2 ----------------- Failed Tests: ----------------- No tests ran.

1 3

[CQ]: 91888,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Jun '18

04 Jun '18

Change 91888,3 (ovirt-engine) 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/91888/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 446 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Jun '18

04 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/446/ Build Number: 446 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #446 [Gal Ben Haim] 4.2: Backport tests from master [Barak Korren] Fix mock_cleanup.sh trying to umount bad things [Barak Korren] Switch fabric-ovirt to STDCI v2 ----------------- Failed Tests: ----------------- No tests ran.

1 3

[JIRA] (OVIRT-2134) Investigate why HC suites fail on slaves with *-IBRS CPU
by Gal Ben Haim (oVirt JIRA) 04 Jun '18

04 Jun '18

Gal Ben Haim created OVIRT-2134: ----------------------------------- Summary: Investigate why HC suites fail on slaves with *-IBRS CPU Key: OVIRT-2134 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2134 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra The HC suites work just fine on "ovirt-srv05.phx.ovirt.org". while failing on "ovirt-srv21.phx.ovirt.org" and "ovirt-srv18.phx.ovirt.org". One thing that I've noticed is the difference between the CPU types on those slaves: ovirt-srv05.phx.ovirt.org - IvyBridge ovirt-srv21.phx.ovirt.org and ovirt-srv18.phx.ovirt.org - Haswell-noTSX-IBRS Together with [1], I have a strong feeling that this is the issue. [1] - https://gerrit.ovirt.org/#/c/90542/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2133) Explain how to remove a stale OST env
by Gal Ben Haim (oVirt JIRA) 04 Jun '18

04 Jun '18

Gal Ben Haim created OVIRT-2133: ----------------------------------- Summary: Explain how to remove a stale OST env Key: OVIRT-2133 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2133 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra If the lago prefix was removed without calling `lago destroy`, stale networks and VMs can be still running on the host. If so, the following error might occur: {code:java} libvirtError: internal error: Network is already in use by interface SOME INTERFACE NAME {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1933) Could not resolve host: mirrorlist.centos.org; Unknown error
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1933?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1933: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Could not resolve host: mirrorlist.centos.org; Unknown error > ------------------------------------------------------------ > > Key: OVIRT-1933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1933 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > I remember we had that in the past. And it looks intermittent. > http://jenkins.ovirt.org/blue/organizations/jenkins/rgolangh_ovirt-flexdriv… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1933) Could not resolve host: mirrorlist.centos.org; Unknown error
by Roy Golan (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1933?page=com.atlassian.jira.… ] Roy Golan commented on OVIRT-1933: ---------------------------------- I can confirm this is working well with my latest github pipeline. You can close this, it was most likely intermittent connectivity problem. > Could not resolve host: mirrorlist.centos.org; Unknown error > ------------------------------------------------------------ > > Key: OVIRT-1933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1933 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > I remember we had that in the past. And it looks intermittent. > http://jenkins.ovirt.org/blue/organizations/jenkins/rgolangh_ovirt-flexdriv… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

Check patch jobs for Fedora 28 are failing
by Tal Nisan 04 Jun '18

04 Jun '18

Example: http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc28-x86_64/67… Exception snippet: *12:12:36* Traceback (most recent call last):*12:12:36* File "/usr/bin/isort", line 6, in <module>*12:12:36* from pkg_resources import load_entry_point*12:12:36* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3095, in <module>*12:12:36* @_call_aside*12:12:36* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3079, in _call_aside*12:12:36* f(*args, **kwargs)*12:12:36* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3108, in _initialize_master_working_set*12:12:36* working_set = WorkingSet._build_master()*12:12:36* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 570, in _build_master*12:12:36* ws.require(__requires__)*12:12:36* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 888, in require*12:12:36* needed = self.resolve(parse_requirements(requirements))*12:12:36* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 774, in resolve*12:12:36* raise DistributionNotFound(req, requirers)*12:12:36* pkg_resources.DistributionNotFound: The 'futures' distribution was not found and is required by isort*12:12:36* + echo ERROR: The following check failed:*12:12:36* ERROR: The following check failed:*12:12:36* + echo isort --check build/helptag.py build/helptag_checker.py build/helptag-oneline-check.py packaging/bin/engine-host-update.py packaging/bin/engine-migrate-he.py

4 6

[JIRA] (OVIRT-1933) Could not resolve host: mirrorlist.centos.org; Unknown error
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1933?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1933: ---------------------------------- [~rgolan(a)redhat.com] ping? > Could not resolve host: mirrorlist.centos.org; Unknown error > ------------------------------------------------------------ > > Key: OVIRT-1933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1933 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > I remember we had that in the past. And it looks intermittent. > http://jenkins.ovirt.org/blue/organizations/jenkins/rgolangh_ovirt-flexdriv… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1909) GetBadges is not working anymore
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1909?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1909: ---------------------------------- [~ederevea] we dropped the Jenkins integration right? so I guess we can close this ticket > GetBadges is not working anymore > -------------------------------- > > Key: OVIRT-1909 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1909 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Not sure what happened 3 months ago but GetBadges is not receiving data > anymore. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1886: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) It was decided to drop fcraw support from CI due to its instability. > Add fcraw support for s390x and ppc64le > --------------------------------------- > > Key: OVIRT-1886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors, mock_runner > Reporter: sbonazzo > Assignee: infra > > Hi, > pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for > s390x ad ppc64le but looks like it won't be enough, opening a ticket as > suggested by Barak. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1873: ---------------------------------- I think it was agreed to drop fcraw support from CI due to its instability, any need for this ticket or we can close it? > 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#100086)

1 0

[JIRA] (OVIRT-1850) rename he-basic to he-basic-noansible
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1850?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1850: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) As stated, if the maintainer wish to rename the suites, he can send a patch to OST for renaming. > rename he-basic to he-basic-noansible > ------------------------------------- > > Key: OVIRT-1850 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1850 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > Hosted-engine setup recently moved to using the ansible flow by default [2]. > I pushed [1] to make he-basic use the old flow, so that we keep testing it. > Please merge [1], and rename 'he-basic' in the manual OST job to > 'he-basic-noansible'. Thanks. > [1] https://gerrit.ovirt.org/86398 > [2] https://gerrit.ovirt.org/83900 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1834: ---------------------------------- [~gbenhaim(a)redhat.com] is there a different card for tracking the proposed long-term solution? > 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#100086)

1 0

[JIRA] (OVIRT-2132) can't connect to monitoring.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2132?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2132: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > can't connect to monitoring.ovirt.org > ------------------------------------- > > Key: OVIRT-2132 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2132 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Hi, > today I can't connect to monitoring.ovirt.org. Can you please check its > status and bring back it online? > Thanks, > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2131: ---------------------------------- Maybe its time to close again the external repos, i.e - revert https://gerrit.ovirt.org/#/c/91150/. but needs to wait for https://gerrit.ovirt.org/#/c/91647/ first. > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2132) can't connect to monitoring.ovirt.org
by sbonazzo (oVirt JIRA) 04 Jun '18

04 Jun '18

sbonazzo created OVIRT-2132: ------------------------------- Summary: can't connect to monitoring.ovirt.org Key: OVIRT-2132 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2132 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, today I can't connect to monitoring.ovirt.org. Can you please check its status and bring back it online? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2131: ----------------------------- Summary: Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 (was: Cannot find a valid baseurl for repo: base/7/x86_64) > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by Gal Ben Haim (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2108: ------------------------------------- As stated, it will require building lago for ppc64. It's difficult to evaluate the amount of time that is needed for this task, but for sure it's not something immediate. > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: sbonazzo > Assignee: infra > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2131) Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

Dafna Ron created OVIRT-2131: -------------------------------- Summary: Cannot find a valid baseurl for repo: base/7/x86_64 Key: OVIRT-2131 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra test failed. looking into it '11:12:55 [basic-suit] 11:12:55 [basic-suit] - STDERR 11:12:55 [basic-suit] + HUGEPAGES=3 11:12:55 [basic-suit] + yum update -y iptables 11:12:55 [basic-suit] 11:12:55 [basic-suit] 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: 11:12:55 [basic-suit] 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. 11:12:55 [basic-suit] 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer 11:12:55 [basic-suit] distribution release than is supported by the repository (and the 11:12:55 [basic-suit] packages for the previous distribution release still work). 11:12:55 [basic-suit] 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... 11:12:55 [basic-suit] 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: 11:12:55 [basic-suit] 11:12:55 [basic-suit] yum-config-manager --disable <repoid> 11:12:55 [basic-suit] or 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> 11:12:55 [basic-suit] 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice 11:12:55 [basic-suit] compromise: 11:12:55 [basic-suit] 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true 11:12:55 [basic-suit] 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 11:12:55 [basic-suit] 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) 11:12:55 [basic-suit] Error while running thread 11:12:55 [basic-suit] Traceback (most recent call last): 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 11:12:55 [basic-suit] queue.put({'return': func()}) 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host 11:12:55 [basic-suit] host.name(), 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 11:12:55 [basic-suit] Error while running thread 11:12:55 [basic-suit] Traceback (most recent call last): 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 11:12:55 [basic-suit] queue.put({'return': func()}) 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host 11:12:55 [basic-suit] host.name(), 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 11:12:57 [upgrade-from-release-suit] Finish: creating root cache 11:12:57 [upgrade-from-release-suit] Finish: chroot init 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: 11:12:57 [upgrade-from-release-suit] Finish: run 11:12:57 [upgrade-from-release-suit] Init took 208 seconds 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1466) Switch to deploying JJB via PIP
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1466?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1466: ----------------------------------- Assignee: Barak Korren (was: infra) > Switch to deploying JJB via PIP > ------------------------------- > > Key: OVIRT-1466 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1466 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > Labels: jjb, standard-ci > > Since the JJB deployment job runs directly on the Jenkins master, we've been creating and using an RPM package for JJB. This made it hard to switch JJB versions. > Once we implement OVIRT-1465, we gain sufficient isolation via mock to allow ourselves to install JJB via pip. > We can set things up so that pip installs a specific JJB version, that way we can gate JJB version updates and have then checked by check-patch. We can even expand the upstream polling system to track JJB versions for us and create update patches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2077) Clicking Reply doesn't display Documentation in the dialog window
by Evgheni Dereveanchin (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2077?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2077: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Clicking Reply doesn't display Documentation in the dialog window > ----------------------------------------------------------------- > > Key: OVIRT-2077 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2077 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Emma Heftman > Assignee: Evgheni Dereveanchin > Attachments: image.png, image.png, image.png > > > My name appears correctly as the committer and uploader but as the Assignee > it appears without an icon...which is strange. > When i hit Reply to do +1 for Documentation, there is no Documentation > option in the dialog. > Also,there is an icon next to Uploader saying it was uploaded without a > certificate. > It also says uploader emmahef > while committer is Emma Heftman > I recently changed my Full Name from emmahef to Emma Heftman. But when i > log out and log in, the Full Name in Profile goes back to emmahef, while > the Full Name that appears in the Contact Information window is Emma > Heftman. > In my .ssh config file it says: > host gerrit.ovirt.org > HostName gerrit.ovirt.org > Port 29418 > User emmahef > The change I'm assigned to is: https://gerrit.ovirt.org/#/c/91103/ > -- > Thanks a lot, > Emma > *Emma Heftman* > Technical Writer, Red Hat Israel > [image: Inline image 1] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1626
by jenkins＠jenkins.phx.ovirt.org 04 Jun '18

04 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Sandro Bonazzola] guest agent: move to fc28 [Martin Perina] ovirt-engine: Drop FC28 build from 4.2 [arachmani] ovirt-engine-api-explorer: move from fc27 to fc 28 ------------------------------------------ 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-centos-updates-el7-x86_64/…> > 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 72898b0f612cfb12bc7b860c4eeb90d0efcb49b7 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 72898b0f612cfb12bc7b860c4eeb90d0efcb49b7 Commit message: "ovirt-engine-api-explorer: move from fc27 to fc 28" > git rev-list --no-walk 6bd80c8c7d578e02cc43e27ad05ef41fe6796c91 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4626862510290130928.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fc25/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2108: ---------------------------------- [~gbenhaim(a)redhat.com] I remember this wasn't possible due to missing pkgs on power, but I don't remember any details. Is it possible given the time and resources? > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: sbonazzo > Assignee: infra > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

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

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2078: ---------------------------------- [~sbonazzo(a)redhat.com] and [~mskrivanek] were the original requestors for this user story, they might help add more info. > 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#100086)

1 0

[JIRA] (OVIRT-2130) Support for private changes in Gerrit
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2130?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2130: ----------------------------- Resolution: Duplicate Status: Done (was: To Do) https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Support for private changes in Gerrit > ------------------------------------- > > Key: OVIRT-2130 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2130 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > can you please upgrade gerrit to latest version so we can leverage support > for private changes when working on security related patches? > Thanks, > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2130) Support for private changes in Gerrit
by sbonazzo (oVirt JIRA) 04 Jun '18

04 Jun '18

sbonazzo created OVIRT-2130: ------------------------------- Summary: Support for private changes in Gerrit Key: OVIRT-2130 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2130 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, can you please upgrade gerrit to latest version so we can leverage support for private changes when working on security related patches? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] eyal edri moved OST-35 to OVIRT-2108: ------------------------------------- Project: oVirt - virtualization made easy (was: oVirt system tests) Workflow: Task Management Workflow (was: Software Simplified Workflow for Project OST) Key: OVIRT-2108 (was: OST-35) > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: sbonazzo > Assignee: infra > Labels: ost_ticket_tmp > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2095) Re: he-basic-ansible_suite_master: failed to set MSR 0xd90 to 0x0
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2095?page=com.atlassian.jira.… ] eyal edri moved OST-106 to OVIRT-2095: -------------------------------------- Project: oVirt - virtualization made easy (was: oVirt system tests) Workflow: Task Management Workflow (was: Software Simplified Workflow for Project OST) Key: OVIRT-2095 (was: OST-106) > Re: he-basic-ansible_suite_master: failed to set MSR 0xd90 to 0x0 > ----------------------------------------------------------------- > > Key: OVIRT-2095 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2095 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: Gal Ben Haim > Labels: ost_ticket_tmp > > Opening a ticket on it, Gal will look into it, it might take some time to > investigate. > On Mon, Mar 26, 2018 at 1:24 PM, Yedidyah Bar David <didi(a)redhat.com> wrote: > > Hi all, > > > > Trying to run ovirt-system-tests using mock_runner.sh on my laptop > > (i7-6820HQ T460p, RHEL 7.4, kernel 3.10.0-693.17.1.el7.x86_64, > > qemu-kvm-rhev-2.9.0-16.el7_4.13.x86_64). > > > > hosted-engine deploy starts, and fails while running virt-install to > > create the engine vm (which will be a nested-kvm vm). > > > > qemu log on the nested-kvm host0 says: > > > > 2018-03-26T08:02:16.727212Z qemu-kvm: error: failed to set MSR 0xd90 to 0x0 > > qemu-kvm: /builddir/build/BUILD/qemu-2.9.0/target/i386/kvm.c:1843: > > kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. > > > > Searched and found this: > > > > https://bugs.launchpad.net/qemu/+bug/1665389 > > > > which seems very similar, although from a year ago and about a fedora > > 24 kernel+qemu. The conclusion there is: > > > > <quote> > > Yes, I mean '-cpu host' in the bare metal. There is no workaround; it > > worked by chance and it triggered other hard to find bugs. > > </quote> > > > > So, what should I/we do? Is there a workaround? How does this work > > elsewhere? > > > > Thanks, > > -- > > Didi > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > MANAGER > RHV 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) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2092: ------------------------------------- You linked to [91900|https://gerrit.ovirt.org/#/c/91900/] in this ticket, but the patch you actually re added according to the link you provided here is [91886|https://gerrit.ovirt.org/#/c/91886] You can see that change had gone into testing here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… And that test finished successfully: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2282/ The success was reported here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… Which is why the queue became empty. Non of this indicated any issue with standard enqueue. If you re-add a change by re-running the "add" build on the main CQ job - standard-enqueue is not even a part of the process. > standard-enqueue 4.2 not running > -------------------------------- > > Key: OVIRT-2092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > but the tested is showing that it only ran once (yesterday): > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > and "next test" job is showing empty queue: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2092: ------------------------------------- WRT [build 14051|https://jenkins.ovirt.org/view/Change queue jobs/job/standard-enqueue/14051] - its perfect;y fine. The 'jenkins' project does not build any RPMs so there is nothing to submit to any queues. > standard-enqueue 4.2 not running > -------------------------------- > > Key: OVIRT-2092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > but the tested is showing that it only ran once (yesterday): > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > and "next test" job is showing empty queue: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2093?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2093: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Add OST 4.2 -> 4.2 upgrade suit > ------------------------------- > > Key: OVIRT-2093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: High > > OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

Barak Korren created OVIRT-2093: ----------------------------------- Summary: Add OST 4.2 -> 4.2 upgrade suit Key: OVIRT-2093 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Barak Korren Assignee: infra Priority: High OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2093?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2093: -------------------------------- Epic Link: OVIRT-2091 > Add OST 4.2 -> 4.2 upgrade suit > ------------------------------- > > Key: OVIRT-2093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Barak Korren > Assignee: infra > Priority: High > > OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

Dafna Ron created OVIRT-2092: -------------------------------- Summary: standard-enqueue 4.2 not running Key: OVIRT-2092 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… but the tested is showing that it only ran once (yesterday): http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… and "next test" job is showing empty queue: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91899,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Jun '18

04 Jun '18

Change 91899,3 (ovirt-engine) 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/91899/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8029/

1 0

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

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2078: ------------------------------------- What is the use case? Can we put this in terms of a user story? > 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#100086)

1 0