- Infra - oVirt List Archives

[CQ]: 93786, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Aug '18

21 Aug '18

A system test invoked by the "ovirt-master" change queue including change 93786,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93787,3 (vdsm) 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 93787,3 (vdsm) 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://gerrit.ovirt.org/#/c/93786/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93787/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9180/

1 0

[CQ]: 93787,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 21 Aug '18

21 Aug '18

Change 93787,3 (vdsm) 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/93787/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9178/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1864
by jenkins＠jenkins.phx.ovirt.org 21 Aug '18

21 Aug '18

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 e8618a77f594da66dd957e08702fe84cd2f876ca (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e8618a77f594da66dd957e08702fe84cd2f876ca Commit message: "Onboard stdci-sample-liora repo" > git rev-list --no-walk e8618a77f594da66dd957e08702fe84cd2f876ca # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6004180188489504788.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-base-el6/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2446) Github push trigger will fail if was trigger by a tag push
by Roy Golan (oVirt JIRA) 21 Aug '18

21 Aug '18

Roy Golan created OVIRT-2446: -------------------------------- Summary: Github push trigger will fail if was trigger by a tag push Key: OVIRT-2446 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2446 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra When pushing a tag to a GH it triggers the jenkins webhook. In the invoked job, it will try to fech a new head with that tag, but that will fail since the repo doesn't have a head since it is started as git init. A breakdown from https://jenkins.ovirt.org/job/oVirt_ovirt-openshift-extensions_standard-on-… - git init a repo *14:57:15* > git init /home/jenkins/workspace/oVirt_ovirt-openshift-extensions_standard-on-ghpush/ovirt-openshift-extensions # timeout=10 - git fetch tags (maybe the problem is here as it doesn't reffer to refs/tags) *15:35:07* [check-merged.el7.x86_64] > git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/* - fetch upstream changes, which is here a tag v0.3.2, so it uses 'refs/tags/v0.3.2' *14:57:18* > git fetch --tags --progress https://github.com/oVirt/ovirt-openshift-extensions +refs/tags/v0.3.2:myhead This fails with *14:57:19* stderr: error: cannot update ref 'refs/heads/myhead': trying to write non-commit object 3c7b5a5d243d1f3bcecbe7b527726b06113d0ec5 to branch 'refs/heads/myhead' While in regular merge with a tag on it uses 'refs/heads/master': *15:35:10* [check-merged.el7.x86_64] > git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/master:myhead Since refs/tags/v0.3.2 doesn't exist locally it can't reference it. Since refs/heads/master exists locally it can create the alias 'myhead' to it. I would like to have the option to push a tag and trigger a build but this is not working atm without a commit attached to it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Galit Rosenthal (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Galit Rosenthal commented on OVIRT-2264: ---------------------------------------- Sent a mail to Steven, wait for his answer > 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#100090)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2054: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) open for more than 2 weeks, will reopen if it happens again > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2054: ---------------------------------- I want to start a new policy of closing tickets if we don't get answers for 2 weeks or the issue isn't happening for 2 weeks. Otherwise we'll be swamped with tickets. If a race happens again, you can search for it in JIRA with ost_race to check if it happened in the past before opening a new ticket. > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2193: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) No replies from developers, closing. If this will reappear, another 2 week period will be set to get a possible debug or RCA from developers. > vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory > ---------------------------------------------------------------------- > > Key: OVIRT-2193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we have a failed vdsm test in basic master suite. > 004_basic_sanity.preview_snapshot_with_memory > seems like a regression. > ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe > /previewsnapshot'. > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was > not provided. > at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] > at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' > Change 90532,7 (vdsm) 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/90532/7 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2193: ---------------------------------- [~dron] we can't keep chasing this, For now let's set a deadline of 2 weeks for get replies on races from developers. ( eventually we'll shorten it for one week ). if there isn't a maintainer that answers or provides info within a week, please close the ticket. > vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory > ---------------------------------------------------------------------- > > Key: OVIRT-2193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we have a failed vdsm test in basic master suite. > 004_basic_sanity.preview_snapshot_with_memory > seems like a regression. > ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe > /previewsnapshot'. > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was > not provided. > at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] > at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' > Change 90532,7 (vdsm) 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/90532/7 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2444) jenkin's generic webhook times out
by Evgheni Dereveanchin (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2444?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2444: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > jenkin's generic webhook times out > ---------------------------------- > > Key: OVIRT-2444 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2444 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Roy Golan > Assignee: Evgheni Dereveanchin > > After merging a pool request [1] I didn't see the check-merged working. I > went into the webhook section > and so that jenkins wasn't responding in time. > Also a simple 'curl http://jenkins.ovirt.org/generic-webhook-trigger/invoke' > doesn't return > [1] https://github.com/oVirt/ovirt-openshift-extensions/pull/60 > Please help > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0