November 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Nir Soffer (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510841668-15493-416 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Nir Soffer created OVIRT-1770: --------------------------------- Summary: Build on fedora 26 fails, accessing console log extremely slow Key: OVIRT-1770 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I wait forever for this url: http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… here example: $ time curl http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562 real 0m22.107s user 0m0.005s sys 0m0.009s Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510841668-15493-416 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Nir Soffer created OVIRT-1770:</h3> <pre> Summary: Build on fedora 26 fails, accessing console log extremely slow Key: OVIRT-1770 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra</pre> <p>I wait forever for this url: <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <p>here example:</p> <p>$ time curl <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <blockquote><p>/dev/null</p></blockquote> <pre>% Total % Received % Xferd Average Speed Time Time Time</pre> <p>Current</p> <pre>Dload Upload Total Spent Left</pre> <p>Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562</p> <p>real 0m22.107s user 0m0.005s sys 0m0.009s</p> <p>Can we fix to be less then a second?</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510841668-15493-416--

1 0

Build on fedora 26 fails, accessing console log extremely slow
by Nir Soffer 16 Nov '17

16 Nov '17

I wait forever for this url: http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… here example: $ time curl http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562 real 0m22.107s user 0m0.005s sys 0m0.009s Can we fix to be less then a second?

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510838318-17486-395 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1769 at 11/16/17 1:18 PM: --------------------------------------------------------------- You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... Instead, a new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master' was (Author: bkorren(a)redhat.com) You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master' > 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#100071) ------------=_1510838318-17486-395 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>Barak Korren edited comment on OVIRT-1769 at 11/16/17 1:18 PM:</h3> <p>You can`t run a ‘*-4.1’ suit on ‘master’ code, the final part of the suit name determines which code it tests… Instead, a new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like ‘compat-suit-master’</p> <p>was (Author: bkorren(a)redhat.com) You can`t run a ‘*-4.1’ suit on ‘master’ code, the final part of the suit name determines which code it tests… instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like ‘compat-suit-master’</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#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510838318-17486-395--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510838253-23453-415 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1769: -------------------------------- Epic Link: OVIRT-400 > 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#100071) ------------=_1510838253-23453-415 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>Barak Korren updated OVIRT-1769:</h3> <pre>Epic Link: OVIRT-400</pre> <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#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510838253-23453-415--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510838252-25756-414 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1769: -------------------------------- Epic Link: OVIRT-400 > 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#100071) ------------=_1510838252-25756-414 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>Barak Korren updated OVIRT-1769:</h3> <pre>Epic Link: OVIRT-400</pre> <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#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510838252-25756-414--

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by Barak Korren (oVirt JIRA) 16 Nov '17

16 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1769: ------------------------------------- You can`t run a '*-4.1' suit on 'master' code, the final part of the suit name determines which code it tests... instead I new suit should be composed of the necessary parts in other suits. Since suites are mostly just sets of symlinks into a pool of shared files, this is not hard to do. I suppose the new suit could be called something like 'compat-suit-master' > 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#100071)

1 0

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility
by danken (oVirt JIRA) 16 Nov '17

16 Nov '17

This is a multi-part message in MIME format... ------------=_1510837432-10010-387 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit danken created OVIRT-1769: ----------------------------- Summary: 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#100071) ------------=_1510837432-10010-387 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>danken created OVIRT-1769:</h3> <pre> Summary: 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</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.</p> <p>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> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1510837432-10010-387--

1 0

[oVirt Jenkins] standard-enqueue - Build #6956 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 16 Nov '17

16 Nov '17

------=_Part_304_831800607.1510762884944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6956/ Build Name: #6956 Build Description: Gerrit: 82230 - mom (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82230 - title: Use ping2 RPC method to test connection - project: mom - branch: master - author: Andrej Krejcir <akrejcir(a)redhat.com> ------=_Part_304_831800607.1510762884944--

3 3

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #989
by jenkins＠jenkins.phx.ovirt.org 16 Nov '17

16 Nov '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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 54d8fd1698946c60f7eb0f36bd04d4b011dd42bf (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 54d8fd1698946c60f7eb0f36bd04d4b011dd42bf Commit message: "Use oVirt version for names of metamodel jobs" > git rev-list 54d8fd1698946c60f7eb0f36bd04d4b011dd42bf # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2445833562698152819.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 1456, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 772, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 755, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 734, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 711, 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

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #771
by jenkins＠jenkins.phx.ovirt.org 16 Nov '17

16 Nov '17

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/771/display/…>

1 1