- Infra - oVirt List Archives

CPU is incompatible (was: Change in ovirt-system-tests[master]: Test hosted-engine cleanup)
by Yedidyah Bar David 02 Apr '18

02 Apr '18

On Mon, Apr 2, 2018 at 11:38 AM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: Test hosted-engine cleanup > ...................................................................... > > > Patch Set 23: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/21/ : FAILURE 06:56:13 [check-patch.el7.x86_64] libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: xsave, avx, rdtscp Any idea? > > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/88331 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-system-tests > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I5876a419dc2437de51149b1fe02ffd900e6ab29e > Gerrit-Change-Number: 88331 > Gerrit-PatchSet: 23 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Comment-Date: Mon, 02 Apr 2018 08:38:04 +0000 > Gerrit-HasComments: No -- Didi

2 2

Re: Change in ovirt-system-tests[master]: Install otopi-debug-plugins in hosted-engine suites
by Yedidyah Bar David 02 Apr '18

02 Apr '18

On Mon, Apr 2, 2018 at 11:15 AM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: Install otopi-debug-plugins in hosted-engine suites > ...................................................................... > > > Patch Set 7: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/25/ : FAILURE The engine did not manage to start yet, we failed on download_engine_certs. Pushed: https://gerrit.ovirt.org/89717 Not sure how come it does not happen much more. Does the new STDV2 change anything significant re load/timing/etc.? V1 below succeeded. > > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/89062 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-system-tests > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I34ce668e5709db78f0836f01a1ca9a8a50612b45 > Gerrit-Change-Number: 89062 > Gerrit-PatchSet: 7 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Comment-Date: Mon, 02 Apr 2018 08:15:26 +0000 > Gerrit-HasComments: No -- Didi

3 2

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

02 Apr '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Daniel Belenky] docker cleanup:Fix edge case for unamed containers [Daniel Belenky] nested_config: Count nesting level of options [Daniel Belenky] Introduce conditional execution in STDCI DSL [Daniel Belenky] Add OST STDCI V2 jobs ------------------------------------------ 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 b277ad136abaf6d35d74352e4166d6c23f133d68 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b277ad136abaf6d35d74352e4166d6c23f133d68 Commit message: "Add OST STDCI V2 jobs" > git rev-list --no-walk a29b6a34b28e15292b8b73911da5d3e8760a9cf0 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins8670225119782506825.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/centos-qemu-ev-testing-el7/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 2

Re: o-s-t fails on docker cleanup?
by Barak Korren 02 Apr '18

02 Apr '18

Adding Dbelenky, infra. On 2 April 2018 at 09:47, Yaniv Kaul <ykaul(a)redhat.com> wrote: > From [1], for example: > > 23:38:29 device-mapper: remove ioctl on > docker-8:3-3221462509-a1a2c5a4ca437bb3760f453aebcf1f12661009b511c5cb81ea088e5acd19b771 > failed: Device or resource busy > 23:38:29 Command failed > 23:38:29 Removing the used loop devices... > 23:38:29 Redirecting to /bin/systemctl restart libvirtd.service > 23:38:30 Stopping and removing all running containers > 23:38:30 Traceback (most recent call last): > 23:38:30 File > "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", > line 468, in <module> > 23:38:30 main() > 23:38:30 File > "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", > line 31, in main > 23:38:30 stop_all_running_containers(client) > 23:38:30 File > "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", > line 120, in stop_all_running_containers > 23:38:30 _get_container_name(container), _get_container_id(container) > 23:38:30 File > "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py", > line 128, in _get_container_name > 23:38:30 return container['Labels']['name'] > 23:38:30 KeyError: 'name' > > > > Let me know if it's a known issue, or should I open a JIRA on it. > > > Y. > [1] > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 1

[JIRA] (OVIRT-1957) [VDSM] check-merge lago VM does not respond.
by Edward Haas (oVirt JIRA) 02 Apr '18

02 Apr '18

This is a multi-part message in MIME format... ------------=_1522652466-21442-182 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Edward Haas created OVIRT-1957: ---------------------------------- Summary: [VDSM] check-merge lago VM does not respond. Key: OVIRT-1957 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1957 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra Hello, Seems like from time to time, VDSM master check-merge, which raises a Lago VM to run the functional tests is failing. Based on the logs, we seem to loose the VM (please re-check me on this) with no apparent reason. The tests that run at the time this is happening just check the VDSM API validation, they are not even touching the configuration. Could you please try to help us with this issue? Thanks, Edy. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1522652466-21442-182 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Edward Haas created OVIRT-1957:</h3> <pre> Summary: [VDSM] check-merge lago VM does not respond. Key: OVIRT-1957 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1957 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra</pre> <p>Hello,</p> <p>Seems like from time to time, VDSM master check-merge, which raises a Lago VM to run the functional tests is failing. Based on the logs, we seem to loose the VM (please re-check me on this) with no apparent reason. The tests that run at the time this is happening just check the VDSM API validation, they are not even touching the configuration.</p> <p>Could you please try to help us with this issue?</p> <p>Thanks, Edy.</p> <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> ------------=_1522652466-21442-182--

1 0

Conflict between python2-paramiko and python-paramiko (was: Change in ovirt-system-tests[master]: hosted-engine basic suites: Fix collection)
by Yedidyah Bar David 02 Apr '18

02 Apr '18

On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: hosted-engine basic suites: Fix collection > ...................................................................... > > > Patch Set 5: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… : FAILURE 08:08:06 file /usr/lib/python2.7/site-packages/paramiko/__init__.pyc from install of python2-paramiko-1.16.1-2.el7.noarch conflicts with file from package python-paramiko-2.1.1-2.el7.noarch 08:08:06 file /usr/lib/python2.7/site-packages/paramiko/__init__.pyo from install of python2-paramiko-1.16.1-2.el7.noarch conflicts with file from package python-paramiko-2.1.1-2.el7.noarch 08:08:06 file /usr/lib/python2.7/site-packages/paramiko/_version.py from install of python2-paramiko-1.16.1-2.el7.noarch conflicts with file from package python-paramiko-2.1.1-2.el7.noarch ... Known issue? -- Didi

2 5

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 27-03-2018 ] [ 004_basic_sanity.disk_operations ]
by Dafna Ron 02 Apr '18

02 Apr '18

Hi, We have a failure on 004_basic_sanity.disk_operations. the reported change seems to me to be connected to the failure. *Link and headline of suspected patches: core: introduce CreateSnapshotForVm - https://gerrit.ovirt.org/#/c/87671/ <https://gerrit.ovirt.org/#/c/87671/>Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6564/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6564/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6564/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6564/artifact…>(Relevant) error snippet from the log: <error>2018-03-27 11:30:16,167-04 WARN [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default task-11) [9f713a3d-82a9-4db8-8207-bb69a0a2c550] Validation of action 'CreateSnapshotForVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__CREATE,VAR__TYPE__SNAPSHOT,ACTION_TYPE_FAILED_SNAPSHOT_IS_BEING_TAKEN_FOR_VM,$VmName vm12018-03-27 11:30:16,176-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-11) [9f713a3d-82a9-4db8-8207-bb69a0a2c550] method: runAction, params: [CreateSnapshotForVm, CreateSnapshotForVmParameters:{commandId='d8bfdb0e-5ae4-4fed-8852-a0b29e377708', user='null', commandType='Unknown', vmId='65e7fea5-8b7d-4281-bd0d-6a84de207a00'}], timeElapsed: 57ms2018-03-27 11:30:16,186-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-11) [] Operation Failed: [Cannot create Snapshot. Snapshot is currently being created for VM vm1.]2018-03-27 11:30:16,820-04 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [16c08ce6-9a73-489f-a1f2-56e21699f14a] Command 'CopyImageGroupVolumesData' (id: '4c4023b4-21e8-4a98-8ac3-aba51967d160') waiting on child command id: '3d96b933-6e3b-4838-94bc-db3ff0cadcdc' type:'CopyData' to complete2018-03-27 11:30:16,833-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [16c08ce6-9a73-489f-a1f2-56e21699f14a] method: get, params: [a85992e9-40b8-4c80-9c93-3bf767f6efa4], timeElapsed: 8ms</error>*

4 9

[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
by Yedidyah Bar David (oVirt JIRA) 02 Apr '18

02 Apr '18

This is a multi-part message in MIME format... ------------=_1522648927-23302-146 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yedidyah Bar David created OVIRT-1956: ----------------------------------------- Summary: manual job upgrade options/table are messy Key: OVIRT-1956 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1956 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi, This was originally reported as [1]. It's not completely clear what each choice of 'ENGINE_VERSION' and 'SUITE_TYPE' runs. We should clarify that, add to the table missing information if needed, including noting somehow combinations that should not work, if any (e.g. upgrade from 4.0 to 4.2 or master). In addition to what I wrote in [1], I now checked and saw that a patch [2] for 4.1 made the change-queue run [3]: - basic-suite - upgrade-from-prevrelease - this caused upgrade from 4.0 to 4.1 - upgrade-from-release - this caused upgrade from 4.1 (released?) to 4.1 (tested) Which looks just fine to me, but if that's also supported by the manual job, it's very hard to guess from the table. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1552703 [2] https://gerrit.ovirt.org/89556 [3] http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/ex… -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1522648927-23302-146 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Yedidyah Bar David created OVIRT-1956:</h3> <pre> Summary: manual job upgrade options/table are messy Key: OVIRT-1956 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1956 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi,</p> <p>This was originally reported as [1].</p> <p>It's not completely clear what each choice of ‘ENGINE_VERSION’ and ‘SUITE_TYPE’ runs. We should clarify that, add to the table missing information if needed, including noting somehow combinations that should not work, if any (e.g. upgrade from 4.0 to 4.2 or master).</p> <p>In addition to what I wrote in [1], I now checked and saw that a patch [2] for 4.1 made the change-queue run [3]:</p> <ul><li><p>basic-suite</p></li> <li><p>upgrade-from-prevrelease – this caused upgrade from 4.0 to 4.1</p></li> <li><p>upgrade-from-release – this caused upgrade from 4.1 (released?) to</p></li></ul> <p>4.1 (tested)</p> <p>Which looks just fine to me, but if that's also supported by the manual job, it's very hard to guess from the table.</p> <p>[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1552703">https://bugzilla.redhat.com/show_bug.cgi?id=1552703</a> [2] <a href="https://gerrit.ovirt.org/89556">https://gerrit.ovirt.org/89556</a> [3] <a href="http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/ex…">http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/ex…</a> — Didi</p> <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> ------------=_1522648927-23302-146--

1 0

[JIRA] (OVIRT-1955) Create YAML templates for STDCI V2 poll-upstream-sources jobs
by Barak Korren (oVirt JIRA) 02 Apr '18

02 Apr '18

Barak Korren created OVIRT-1955: ----------------------------------- Summary: Create YAML templates for STDCI V2 poll-upstream-sources jobs Key: OVIRT-1955 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1955 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra Priority: High STDCI V2 code currently supports responding on GitHub and Gerrit events. We basically have 2 job templates that are supposed to be used the same way for all projects so that there is almost no per-project setup in JJB YAML besides basic listing of the project itself. This model handles most STDCI stages well besides "poll-upstream-sources", because "poll-upstream-sources" does not respond on SCM events and instead it runs on a timed basis. In the long run we want to have an stdci.yaml based solution where poll jobs will be created dynamically as needed, but we need a short-term solution. For the short term solution, we need to create a JJB job template that will create a timed V2 style job. This template will need to be used in a similar fashion to how the V1 templates are used, by having some project-specific JJB YAML. This is why we also call this effort the "V1.5" template. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1955) Create YAML templates for STDCI V2 poll-upstream-sources jobs
by Barak Korren (oVirt JIRA) 02 Apr '18

02 Apr '18

This is a multi-part message in MIME format... ------------=_1522648834-31694-393 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1955?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1955: -------------------------------- Epic Link: OVIRT-400 > Create YAML templates for STDCI V2 poll-upstream-sources jobs > ------------------------------------------------------------- > > Key: OVIRT-1955 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1955 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: first_time_task > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1522648834-31694-393 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1955?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1955:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Create YAML templates for STDCI V2 poll-upstream-sources jobs</h3> <pre> Key: OVIRT-1955 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1955 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra Priority: High Labels: first_time_task</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> ------------=_1522648834-31694-393--

1 0