July 2018 - Infra - Ovirt List Archives

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 356 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/356/ Build Number: 356 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #356 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

6 years, 4 months

1
2
0 / 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1729

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...> ------------------------------------------ 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_6...> > 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 c5c7cfa3f5dbe97905fe1771616e2738526d5c95 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c5c7cfa3f5dbe97905fe1771616e2738526d5c95 Commit message: "Add ovirt-engine-metrics and ovirt-dwh to STDCI-v2" > git rev-list --no-walk c5c7cfa3f5dbe97905fe1771616e2738526d5c95 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6054783004933054963.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/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/gen' Build step 'Execute shell' marked build as failure

6 years, 4 months

1
1
0 / 0

[JIRA] (OVIRT-2275) Finish to update "How to run OST" docs

by Greg Sheremeta (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2275?page=com.atlassian.jir... ] Greg Sheremeta commented on OVIRT-2275: --------------------------------------- ETA? I can't get it to run with or without mock. I'm getting lost in the docs. > Finish to update "How to run OST" docs > -------------------------------------- > > Key: OVIRT-2275 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2275 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > We need to finish updating https://gerrit.ovirt.org/#/c/90523/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 513

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/513//artifact/exported... Cheers, Jenkins

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2264: ---------------------------------- I think this failure happens because of delay in the network which is causing the storage image copy to be slower -> causing a failure on deactivate of storage domain. two ways of solving: 1. fix network issues 2. add re-tries on tests [~ederevea] [~gbenhaim(a)redhat.com] can you please have a look and see if you can confirm/suggest a different reason/solution > Cannot deactivate Storage while there are running tasks on this Storage > ----------------------------------------------------------------------- > > Key: OVIRT-2264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2264 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we failed test: 007_sd_reattach.deactivate_storage_domain in vdsm project with error: Cannot deactivate Storage while there are running tasks on this Storage. -Please wait until tasks will finish and try again.]". HTTP response code is 409. > I am opening this as a race in case something changed in OST tests which would cause this to repeat. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506 > https://gerrit.ovirt.org/#/c/92313/2 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2286) 007_sd_reattach.deactivate_storage_domain fails because of running tasks

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2286?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2286: ----------------------------- Resolution: Incomplete Status: Done (was: To Do) closing as this is a clone > 007_sd_reattach.deactivate_storage_domain fails because of running tasks > ------------------------------------------------------------------------ > > Key: OVIRT-2286 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2286 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago, ost_race > > This is a known issue which we should try and solve on ost tests. > the issue is that we try to put domain in maintenance while there are still running tasks - this is blocked by engine by design. > We should fix any actions in ost to be re-run once blocked on this error. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2571/ > {quote} > The task that is stuck is downloadImageFromStream > 2018-07-04 10:12:52,659-04 WARN [org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainWithOvfUpdateCommand] (default task-1) [ce1c28ba-1550-457f-b5e3-ad051488f897] There are running tasks: 'AsyncTask:{commandId='0b18c13f-0fce- > 4303-8f85-ae5a2b051991', rootCommandId='0b18c13f-0fce-4303-8f85-ae5a2b051991', storagePoolId='8dd2fe5a-9dca-42e2-8593-1de1b18b4887', taskId='f2af86fb-dbbb-430c-afd9-2f25131583b1', vdsmTaskId='45ee0fc8-830d-47d5-9c4a-6d4ed72ae6a1', stepId= > 'null', taskType='downloadImageFromStream', status='running'} > The task succeeded but after the deactivate storage domain attempt: > 2018-07-04 10:13:01,579-04 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [1c611686] Command 'ProcessOvfUpdateForStorageDomain' id: '6342fce4-96ff-4ae3-8b40-8155a > 5509761' child commands '[0b18c13f-0fce-4303-8f85-ae5a2b051991, 8e16826f-93dd-442a-8a74-13d14222d45e]' executions were completed, status 'SUCCEEDED' > {quote} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2286) 007_sd_reattach.deactivate_storage_domain fails because of running tasks

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2286?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2286: ---------------------------------- I will close this as this is a clone of ovirt-2264 > 007_sd_reattach.deactivate_storage_domain fails because of running tasks > ------------------------------------------------------------------------ > > Key: OVIRT-2286 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2286 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago, ost_race > > This is a known issue which we should try and solve on ost tests. > the issue is that we try to put domain in maintenance while there are still running tasks - this is blocked by engine by design. > We should fix any actions in ost to be re-run once blocked on this error. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2571/ > {quote} > The task that is stuck is downloadImageFromStream > 2018-07-04 10:12:52,659-04 WARN [org.ovirt.engine.core.bll.storage.domain.DeactivateStorageDomainWithOvfUpdateCommand] (default task-1) [ce1c28ba-1550-457f-b5e3-ad051488f897] There are running tasks: 'AsyncTask:{commandId='0b18c13f-0fce- > 4303-8f85-ae5a2b051991', rootCommandId='0b18c13f-0fce-4303-8f85-ae5a2b051991', storagePoolId='8dd2fe5a-9dca-42e2-8593-1de1b18b4887', taskId='f2af86fb-dbbb-430c-afd9-2f25131583b1', vdsmTaskId='45ee0fc8-830d-47d5-9c4a-6d4ed72ae6a1', stepId= > 'null', taskType='downloadImageFromStream', status='running'} > The task succeeded but after the deactivate storage domain attempt: > 2018-07-04 10:13:01,579-04 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [1c611686] Command 'ProcessOvfUpdateForStorageDomain' id: '6342fce4-96ff-4ae3-8b40-8155a > 5509761' child commands '[0b18c13f-0fce-4303-8f85-ae5a2b051991, 8e16826f-93dd-442a-8a74-13d14222d45e]' executions were completed, status 'SUCCEEDED' > {quote} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2287: ----------------------------- Issue Type: Bug (was: By-EMAIL) > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/... > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2287: ----------------------------- Labels: ost_failures ost_lago (was: ) > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/... > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2287: ----------------------------- Priority: Highest (was: Medium) > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/... > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2018