December 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by eyal edri (oVirt JIRA) 26 Dec '17

26 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1781: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) Doesn't seem related to space issue, please report if it reproduced so we can help debug it in real time. > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt CI > Reporter: danken > Assignee: infra > Priority: High > Labels: vdsm > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1042
by jenkins＠jenkins.phx.ovirt.org 25 Dec '17

25 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1042/displ…> Changes: [Dan Kenigsberg] add network suite to manaul job suite selector ------------------------------------------ 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 ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 Commit message: "add network suite to manaul job suite selector" > git rev-list fa64ebc3c785af5a99aeffd081ec0fb88df044c8 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins561916233656873438.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-1173) Please use git shallow clone as jobs default
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1173?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1173: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) We didn't see any issues with clone on Jenkins due to the current policy, and due to the caching we already have, this won't bring any significant performance improvement and might introduce new errors. > Please use git shallow clone as jobs default > -------------------------------------------- > > Key: OVIRT-1173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roy Golan > Assignee: infra > Priority: Low > Labels: standard-ci > > Most if not all the git clone of the jobs don't need history at all. > For ovirt-engine I see it downloading *11Mb* using --depth 1 vs. *157Mb* > for regular clone. > R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1788: ----------------------------- Status: In Progress (was: To Do) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

This is a multi-part message in MIME format... ------------=_1514218351-25028-112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1007: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) repoclosure job migrated to test in ost. > repo closure job should find also optional pkg > ---------------------------------------------- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: infra > Priority: Low > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514218351-25028-112 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1007:</h3> <pre>Resolution: Won't Fix Status: Done (was: To Do)</pre> <p>repoclosure job migrated to test in ost.</p> <blockquote><h3>repo closure job should find also optional pkg</h3> <pre> Key: OVIRT-1007 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri Assignee: infra Priority: Low</pre> <p><a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console">http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514218351-25028-112--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by eyal edri (oVirt JIRA) 25 Dec '17

25 Dec '17

This is a multi-part message in MIME format... ------------=_1514218057-30883-100 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1769: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) As mentioned, if we want to run such scenario, we need to create a new suite for that, with the relevant tests. Having said that, I'm not sure its worth the resources over testing other flows which are not covered yet. > run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility > ----------------------------------------------------------------------------------- > > Key: OVIRT-1769 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. > However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514218057-30883-100 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1769:</h3> <pre>Resolution: Won't Do Status: Done (was: To Do)</pre> <p>As mentioned, if we want to run such scenario, we need to create a new suite for that, with the relevant tests. Having said that, I'm not sure its worth the resources over testing other flows which are not covered yet.</p> <blockquote><h3>run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility</h3> <pre> Key: OVIRT-1769 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769 Project: oVirt - virtualization made easy Issue Type: New Feature Components: OST Reporter: danken Assignee: infra Priority: High</pre> <p>starting with basic-suite-4.2, we port test cases to sdk4. That's good, since that's the future of the project. However, as long as we promise backward compatibility for sdk3, we need to make sure it does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514218057-30883-100--

1 0

[CQ]: 85723, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85723,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 85668,2 (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 85668,2 (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/85723/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85668/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4520/

1 0

[CQ]: 85723, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85723,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 85668,2 (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 85668,2 (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/85723/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85668/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4518/

1 0

[CQ]: 85717, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85717,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 85668,2 (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 85668,2 (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/85717/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85668/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4517/

1 0

[CQ]: 85286, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Dec '17

25 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85286,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 85668,2 (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 85668,2 (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/85286/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85668/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4515/

1 0