April 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Daniel Belenky (oVirt JIRA) 10 Apr '18

10 Apr '18

This is a multi-part message in MIME format... ------------=_1523365020-24055-182 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Daniel Belenky edited comment on OVIRT-886 at 4/10/18 12:56 PM: ---------------------------------------------------------------- Thinking about this, we've solved a similar issue in https://gerrit.ovirt.org/c/89948 A simple solution could be something like what going through the packages in .packages and verify that they are installed. Should be something like: {code:java} for package in "${packages[@]}"; do rpm -q --whatprovides $package || fail; done {code} After this line, we can run the user's script. The bug is actually in yum. If you try to install multiple packages and some doesn't exist in the repo, it doesn't fail. was (Author: dbelenky(a)redhat.com) Thinking about this, we've solved a similar issue in [https://gerrit.ovirt.org/c/89948/|here] A simple solution could be something like what going through the packages in .packages and verify that they are installed. Should be something like: {code:java} for package in "${packages[@]}"; do rpm -q --whatprovides $pkg_name || fail; done {code} After this line, we can run the user's script. The bug is actually in yum. If you try to install multiple packages and some doesn't exist in the repo, it doesn't fail. > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1523365020-24055-182 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ]</pre> <h3>Daniel Belenky edited comment on OVIRT-886 at 4/10/18 12:56 PM:</h3> <p>Thinking about this, we've solved a similar issue in <a href="https://gerrit.ovirt.org/c/89948">https://gerrit.ovirt.org/c/89948</a> A simple solution could be something like what going through the packages in .packages and verify that they are installed. Should be something like: {code:java} for package in “${packages[@]}”; do rpm -q --whatprovides $package || fail; done {code} After this line, we can run the user's script.</p> <p>The bug is actually in yum. If you try to install multiple packages and some doesn't exist in the repo, it doesn't fail.</p> <p>was (Author: dbelenky(a)redhat.com) Thinking about this, we've solved a similar issue in [<a href="https://gerrit.ovirt.org/c/89948/">https://gerrit.ovirt.org/c/89948/</a>|here]. A simple solution could be something like what going through the packages in .packages and verify that they are installed. Should be something like: {code:java} for package in “${packages[@]}”; do rpm -q --whatprovides $pkg_name || fail; done {code} After this line, we can run the user's script.</p> <p>The bug is actually in yum. If you try to install multiple packages and some doesn't exist in the repo, it doesn't fail.</p> <blockquote><h3>Yum install does not throw error on missing package</h3> <pre> Key: OVIRT-886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Gil Shinar Assignee: infra Labels: mock_runner.sh, standard-ci</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1523365020-24055-182--

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Daniel Belenky (oVirt JIRA) 10 Apr '18

10 Apr '18

This is a multi-part message in MIME format... ------------=_1523364980-19608-136 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Daniel Belenky commented on OVIRT-886: -------------------------------------- Thinking about this, we've solved a similar issue in [https://gerrit.ovirt.org/c/89948/|here] A simple solution could be something like what going through the packages in .packages and verify that they are installed. Should be something like: {code:java} for package in "${packages[@]}"; do rpm -q --whatprovides $pkg_name || fail; done {code} After this line, we can run the user's script. The bug is actually in yum. If you try to install multiple packages and some doesn't exist in the repo, it doesn't fail. > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1523364980-19608-136 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ]</pre> <h3>Daniel Belenky commented on OVIRT-886:</h3> <p>Thinking about this, we've solved a similar issue in [<a href="https://gerrit.ovirt.org/c/89948/">https://gerrit.ovirt.org/c/89948/</a>|here]. A simple solution could be something like what going through the packages in .packages and verify that they are installed. Should be something like: {code:java} for package in “${packages[@]}”; do rpm -q --whatprovides $pkg_name || fail; done {code} After this line, we can run the user's script.</p> <p>The bug is actually in yum. If you try to install multiple packages and some doesn't exist in the repo, it doesn't fail.</p> <blockquote><h3>Yum install does not throw error on missing package</h3> <pre> Key: OVIRT-886 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Gil Shinar Assignee: infra Labels: mock_runner.sh, standard-ci</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</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> ------------=_1523364980-19608-136--

1 0

[CQ]: 90007,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 10 Apr '18

10 Apr '18

Change 90007,1 (ovirt-engine) 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/90007/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1633/

2 1

[CQ]: 9b7e259 (ovirt-ansible-vm-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 10 Apr '18

10 Apr '18

Change 9b7e259 (ovirt-ansible-vm-infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/9b7e25949580931c1b82… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1631/

2 1

[CQ]: 65b8150 (ovirt-ansible-cluster-upgrade) failed "ovirt-4.2" system tests
by oVirt Jenkins 10 Apr '18

10 Apr '18

Change 65b8150 (ovirt-ansible-cluster-upgrade) 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://github.com/oVirt/ovirt-ansible-cluster-upgrade/commit/65b81502f1ca0… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1626/

2 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1451
by jenkins＠jenkins.phx.ovirt.org 10 Apr '18

10 Apr '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Barak Korren] Change the from address in CQ messages ------------------------------------------ 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 9da6c3099441acf4a644f4c730cca1eadacff171 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9da6c3099441acf4a644f4c730cca1eadacff171 Commit message: "Change the from address in CQ messages" > git rev-list --no-walk 12408d1e905e40783b966b5c73293f29a2a2ad1b # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2449215375584510485.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 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]: 89888,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 09 Apr '18

09 Apr '18

Change 89888,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/89888/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6744/

1 0

[CQ]: 71e5efa (ovirt-ansible) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Apr '18

09 Apr '18

A system test invoked by the "ovirt-4.2" change queue including change 71e5efa (ovirt-ansible) failed. However, this change seems not to be the root cause for this failure. Change 2e43ef0 (ovirt-ansible) 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 2e43ef0 (ovirt-ansible) 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://github.com/oVirt/ovirt-ansible/commit/71e5efa287ec952a636da8ff49845… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible/commit/2e43ef0739d5fcc5b59388f511ac2… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1621/

1 0

[CQ]: 7629a6a (ovirt-ansible-manageiq) failed "ovirt-4.2" system tests
by oVirt Jenkins 09 Apr '18

09 Apr '18

Change 7629a6a (ovirt-ansible-manageiq) 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://github.com/oVirt/ovirt-ansible-manageiq/commit/7629a6aacdda57847039… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1617/

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 39 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 Apr '18

09 Apr '18

------=_Part_732_868214772.1522182179383 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 39 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #39 [Gal Ben Haim] Print the prefix, FS and RAM memory usage before cleanup ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_732_868214772.1522182179383--

1 3