- Infra - oVirt List Archives

[JIRA] (OVIRT-1822) ovirt-system-tests/network-suite: grant +2 rights to edwardh
by danken (oVirt JIRA) 01 Jan '18

01 Jan '18

This is a multi-part message in MIME format... ------------=_1514833945-20587-175 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit danken created OVIRT-1822: ----------------------------- Summary: ovirt-system-tests/network-suite: grant +2 rights to edwardh Key: OVIRT-1822 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1822 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: danken Assignee: infra I expect that the new network suite in OST would see many new tests and other modifications. To make development faster, I suggest to grant +2 powers to [~ehaas(a)redhat.com] under the understand that he uses them only on patches affecting network-suite/{lib,features,tests}/**. After month of having +2 powers on Vdsm, I am certain that he would not abuse his powers outside his realm. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514833945-20587-175 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>danken created OVIRT-1822:</h3> <pre> Summary: ovirt-system-tests/network-suite: grant +2 rights to edwardh Key: OVIRT-1822 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1822 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: danken Assignee: infra</pre> <p>I expect that the new network suite in OST would see many new tests and other modifications. To make development faster, I suggest to grant +2 powers to [~ehaas(a)redhat.com] under the understand that he uses them only on patches affecting network-suite/{lib,features,tests}/**.</p> <p>After month of having +2 powers on Vdsm, I am certain that he would not abuse his powers outside his realm.</p> <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> ------------=_1514833945-20587-175--

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1062
by jenkins＠jenkins.phx.ovirt.org 01 Jan '18

01 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1062/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 39cb0786960e2a2b603efb26af900faafe9dde96 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 39cb0786960e2a2b603efb26af900faafe9dde96 Commit message: "ioprocess: Disable build-artifacts on fedora/ppc64le" > git rev-list 39cb0786960e2a2b603efb26af900faafe9dde96 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins9010413751028951079.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/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/gen' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1821) jenkins 'check-patch.sh' does not always generate differences.html in downstream repos
by Barak Korren (oVirt JIRA) 01 Jan '18

01 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1821?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1821: -------------------------------- Status: In Progress (was: To Do) > jenkins 'check-patch.sh' does not always generate differences.html in downstream repos > -------------------------------------------------------------------------------------- > > Key: OVIRT-1821 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1821 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The 'check-patch.sh' script in the 'jenkins' repo knows how to generate a 'differences.html' file when job YAML changes. > The 'jenkins' repo is designed to be used as an upstream source repo for other repos, and it is designed that 'check-patch.sh' will be usable on those DS repos. > When YAML changes from the 'jenkins' repo make it into the DS repos via a patch to the 'upstream-sources.yaml' file in the DS repo, and 'check-patch.sh' runs on that repo, 'differences.html' is not being generated, because the change to 'upstream-sources.yaml' does not look like a job YAML change. > We need to change 'check-patch.sh' so that when running in a DS repo, it knows how to look and diagnose changes coming from the upstream repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1821) jenkins 'check-patch.sh' does not always generate differences.html in downstream repos
by Barak Korren (oVirt JIRA) 01 Jan '18

01 Jan '18

This is a multi-part message in MIME format... ------------=_1514819059-25030-101 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1821: ----------------------------------- Summary: jenkins 'check-patch.sh' does not always generate differences.html in downstream repos Key: OVIRT-1821 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1821 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra The 'check-patch.sh' script in the 'jenkins' repo knows how to generate a 'differences.html' file when job YAML changes. The 'jenkins' repo is designed to be used as an upstream source repo for other repos, and it is designed that 'check-patch.sh' will be usable on those DS repos. When YAML changes from the 'jenkins' repo make it into the DS repos via a patch to the 'upstream-sources.yaml' file in the DS repo, and 'check-patch.sh' runs on that repo, 'differences.html' is not being generated, because the change to 'upstream-sources.yaml' does not look like a job YAML change. We need to change 'check-patch.sh' so that when running in a DS repo, it knows how to look and diagnose changes coming from the upstream repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514819059-25030-101 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1821:</h3> <pre> Summary: jenkins 'check-patch.sh' does not always generate differences.html in downstream repos Key: OVIRT-1821 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1821 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra</pre> <p>The ‘check-patch.sh’ script in the ‘jenkins’ repo knows how to generate a ‘differences.html’ file when job YAML changes.</p> <p>The ‘jenkins’ repo is designed to be used as an upstream source repo for other repos, and it is designed that ‘check-patch.sh’ will be usable on those DS repos.</p> <p>When YAML changes from the ‘jenkins’ repo make it into the DS repos via a patch to the ‘upstream-sources.yaml’ file in the DS repo, and ‘check-patch.sh’ runs on that repo, ‘differences.html’ is not being generated, because the change to ‘upstream-sources.yaml’ does not look like a job YAML change.</p> <p>We need to change ‘check-patch.sh’ so that when running in a DS repo, it knows how to look and diagnose changes coming from the upstream repo.</p> <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> ------------=_1514819059-25030-101--

1 0

[JIRA] (OVIRT-1821) jenkins 'check-patch.sh' does not always generate differences.html in downstream repos
by Barak Korren (oVirt JIRA) 01 Jan '18

01 Jan '18

This is a multi-part message in MIME format... ------------=_1514819059-25953-112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1821?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1821: -------------------------------- Epic Link: OVIRT-400 > jenkins 'check-patch.sh' does not always generate differences.html in downstream repos > -------------------------------------------------------------------------------------- > > Key: OVIRT-1821 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1821 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The 'check-patch.sh' script in the 'jenkins' repo knows how to generate a 'differences.html' file when job YAML changes. > The 'jenkins' repo is designed to be used as an upstream source repo for other repos, and it is designed that 'check-patch.sh' will be usable on those DS repos. > When YAML changes from the 'jenkins' repo make it into the DS repos via a patch to the 'upstream-sources.yaml' file in the DS repo, and 'check-patch.sh' runs on that repo, 'differences.html' is not being generated, because the change to 'upstream-sources.yaml' does not look like a job YAML change. > We need to change 'check-patch.sh' so that when running in a DS repo, it knows how to look and diagnose changes coming from the upstream repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514819059-25953-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-1821?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1821:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>jenkins ‘check-patch.sh’ does not always generate differences.html in downstream repos</h3> <pre> Key: OVIRT-1821 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1821 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra Labels: standard-ci</pre> <p>The ‘check-patch.sh’ script in the ‘jenkins’ repo knows how to generate a ‘differences.html’ file when job YAML changes. The ‘jenkins’ repo is designed to be used as an upstream source repo for other repos, and it is designed that ‘check-patch.sh’ will be usable on those DS repos. When YAML changes from the ‘jenkins’ repo make it into the DS repos via a patch to the ‘upstream-sources.yaml’ file in the DS repo, and ‘check-patch.sh’ runs on that repo, ‘differences.html’ is not being generated, because the change to ‘upstream-sources.yaml’ does not look like a job YAML change. We need to change ‘check-patch.sh’ so that when running in a DS repo, it knows how to look and diagnose changes coming from the upstream repo.</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> ------------=_1514819059-25953-112--

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 140 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Jan '18

01 Jan '18

------=_Part_45_148669655.1514345479076 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/140/ Build Number: 140 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #140 [Yaniv Kaul] Add additional tests for more objects [Nir Soffer] ioprocess: Exclude fc2* ppc64le tests ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_45_148669655.1514345479076--

1 5

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 153 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Jan '18

01 Jan '18

------=_Part_43_1331353204.1514344774074 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/153/ Build Number: 153 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #153 [Yaniv Kaul] Add additional tests for more objects [Nir Soffer] ioprocess: Exclude fc2* ppc64le tests ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_43_1331353204.1514344774074--

1 6

[CQ]: 85849,1 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 31 Dec '17

31 Dec '17

Change 85849,1 (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/85849/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4592/

1 0

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

31 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1059/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 39cb0786960e2a2b603efb26af900faafe9dde96 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 39cb0786960e2a2b603efb26af900faafe9dde96 Commit message: "ioprocess: Disable build-artifacts on fedora/ppc64le" > git rev-list 39cb0786960e2a2b603efb26af900faafe9dde96 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins6156372028349447718.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

CQ for 4.2 not really working right now
by Barak Korren 31 Dec '17

31 Dec '17

If you're on this list you've probably seen the failure emails from the 4.2 CQ. The reason it is failing is that OST is failing to install engine, because there is no engine package available to it. The 4.2 tested repo does not contain an engine package ATM. ther does not seem to be any other repo configured in reposync for 4.2 ATM that engine could be taken from. Wern't we supposed to have 4.1 as a fallback repo fore 4.2 OST until everything branches? As things stand right now, its is quite likely that a 4,2 tested repo will not get built because everything needs an engine package to pass OST and the engine package need a great deal of other things to work, not to mention vdsm -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 3