[JIRA] (OVIRT-2137) default updated cluster test fails -
ACTION_TYPE_FAILED_CPU_NOT_FOUND
by Dafna Ron (oVirt JIRA)
Dafna Ron created OVIRT-2137:
--------------------------------
Summary: default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND
Key: OVIRT-2137
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2137
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra
Change 91888,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/91888/3
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/
I think that we are sending a request to cpu and because of the change done on NULL strings we are failing to get type of cpu which fails the test:
' 2018-06-04 11:57:19,852-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}'
2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Compiled stored procedure. Call string is [{call getvdsbyclusteri
d(?, ?, ?)}]
2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] SqlCall for procedure [GetVdsByClusterId] compiled
2018-06-04 11:57:19,878-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: getAllForCluster, params: [9cbb05e6-680f-11e8-b07e-5452c0a8c904], timeE
lapsed: 25ms
2018-06-04 11:57:19,879-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUST
ER,VAR__ACTION__UPDATE,VAR__TYPE__CLUSTER,ACTION_TYPE_FAILED_CPU_NOT_FOUND
2018-06-04 11:57:19,881-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}'
2018-06-04 11:57:19,881-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationP
arameters:{commandId='36bf82e7-eec8-4b36-99af-db5ade902593', user='null', commandType='Unknown'}], timeElapsed: 58ms
2018-06-04 11:57:19,886-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-6) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.]
'
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as
virt maintainer
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2136?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-2136:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
> ---------------------------------------------------------------
>
> Key: OVIRT-2136
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: danken
> Assignee: Barak Korren
>
> Please add Milan to vdsm-maintainers list.
> ---------- Forwarded message ----------
> From: Edward Haas <ehaas(a)redhat.com>
> Date: Mon, Jun 4, 2018 at 3:35 PM
> Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
> To: "devel(a)ovirt.org" <devel(a)ovirt.org>
> Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas
> <edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg
> <danken(a)redhat.com>
> +1
> Thanks,
> Edy.
> > On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote:
> >
> > Approved.
> >
> > On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski
> > <piotr.kliczewski(a)gmail.com> wrote:
> >> +1
> >>
> >>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote:
> >>>
> >>>
> >>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> >>>>
> >>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com>
> >>>> wrote:
> >>>>>
> >>>>> Hi all,
> >>>>>
> >>>>> Milan Zamazal has been working on the oVirt project for more than 2.5
> >>>>> years.
> >>>>> Let me highlight some of his many contributions to the project:
> >>>>>
> >>>>> - Since January this year - 2018, he's been a maintainer for the stable
> >>>>> branches.
> >>>>> - He developed important features like memory hotunplug, which required
> >>>>> tight cooperation
> >>>>> and communication with the other layers of the stack (libvirt, qemu).
> >>>>> - He is a mentor in the Outreachy program, which lead to creation of the
> >>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer
> >>>>> - He contributed more than 290 patches to the Vdsm project in master
> >>>>> branch alone, excluding backports and contributions to Engine
> >>>>> - He contributed and is contributing testcases and fixes to the oVirt
> >>>>> System Test suite, a tool which was already pivotal in ensuring the
> >>>>> quality of the oVirt project.
> >>>>>
> >>>>> As reviewer, Milan is responsive and his comments are always
> >>>>> comprehensive and well focused,
> >>>>> with strong attitude towards getting things done and done right.
> >>>>>
> >>>>> Milan also demonstrated his ability to adapt to the needs of the project:
> >>>>> - he demonstrated careful and thoughtful patch management while
> >>>>> maintaining the stable branches
> >>>>> - he also demonstrated he's not shy to tackle large and needed changes
> >>>>> during the 4.1 and 4.2 cycles,
> >>>>> when we deeply reorganized the XML processing in the virt code.
> >>>>>
> >>>>> For those reasons, and many more, I think he will be a good addition to
> >>>>> the maintainers team, and I propose him as virt co-maintainer.
> >>>>>
> >>>>> Please share your thoughts
> >>>>
> >>>>
> >>>> +1
> >>>
> >>>
> >>> FWIW, +1
> >>>
> >>>>
> >>>>
> >>>> Nir
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Devel mailing list -- devel(a)ovirt.org
> >>>> To unsubscribe send an email to devel-leave(a)ovirt.org
> >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >>>> oVirt Code of Conduct:
> >>>> https://www.ovirt.org/community/about/community-guidelines/
> >>>> List Archives:
> >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QELJ7YNZVW6...
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Devel mailing list -- devel(a)ovirt.org
> >>> To unsubscribe send an email to devel-leave(a)ovirt.org
> >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >>> oVirt Code of Conduct:
> >>> https://www.ovirt.org/community/about/community-guidelines/
> >>> List Archives:
> >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YIMB6QHQ37D...
> >>>
> >> _______________________________________________
> >> Devel mailing list -- devel(a)ovirt.org
> >> To unsubscribe send an email to devel-leave(a)ovirt.org
> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YBK7IHQELSE...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as
virt maintainer
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2136?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-2136:
--------------------------------
Component/s: Gerrit/git
> Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
> ---------------------------------------------------------------
>
> Key: OVIRT-2136
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Components: Gerrit/git
> Reporter: danken
> Assignee: infra
>
> Please add Milan to vdsm-maintainers list.
> ---------- Forwarded message ----------
> From: Edward Haas <ehaas(a)redhat.com>
> Date: Mon, Jun 4, 2018 at 3:35 PM
> Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
> To: "devel(a)ovirt.org" <devel(a)ovirt.org>
> Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas
> <edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg
> <danken(a)redhat.com>
> +1
> Thanks,
> Edy.
> > On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote:
> >
> > Approved.
> >
> > On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski
> > <piotr.kliczewski(a)gmail.com> wrote:
> >> +1
> >>
> >>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote:
> >>>
> >>>
> >>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> >>>>
> >>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com>
> >>>> wrote:
> >>>>>
> >>>>> Hi all,
> >>>>>
> >>>>> Milan Zamazal has been working on the oVirt project for more than 2.5
> >>>>> years.
> >>>>> Let me highlight some of his many contributions to the project:
> >>>>>
> >>>>> - Since January this year - 2018, he's been a maintainer for the stable
> >>>>> branches.
> >>>>> - He developed important features like memory hotunplug, which required
> >>>>> tight cooperation
> >>>>> and communication with the other layers of the stack (libvirt, qemu).
> >>>>> - He is a mentor in the Outreachy program, which lead to creation of the
> >>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer
> >>>>> - He contributed more than 290 patches to the Vdsm project in master
> >>>>> branch alone, excluding backports and contributions to Engine
> >>>>> - He contributed and is contributing testcases and fixes to the oVirt
> >>>>> System Test suite, a tool which was already pivotal in ensuring the
> >>>>> quality of the oVirt project.
> >>>>>
> >>>>> As reviewer, Milan is responsive and his comments are always
> >>>>> comprehensive and well focused,
> >>>>> with strong attitude towards getting things done and done right.
> >>>>>
> >>>>> Milan also demonstrated his ability to adapt to the needs of the project:
> >>>>> - he demonstrated careful and thoughtful patch management while
> >>>>> maintaining the stable branches
> >>>>> - he also demonstrated he's not shy to tackle large and needed changes
> >>>>> during the 4.1 and 4.2 cycles,
> >>>>> when we deeply reorganized the XML processing in the virt code.
> >>>>>
> >>>>> For those reasons, and many more, I think he will be a good addition to
> >>>>> the maintainers team, and I propose him as virt co-maintainer.
> >>>>>
> >>>>> Please share your thoughts
> >>>>
> >>>>
> >>>> +1
> >>>
> >>>
> >>> FWIW, +1
> >>>
> >>>>
> >>>>
> >>>> Nir
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Devel mailing list -- devel(a)ovirt.org
> >>>> To unsubscribe send an email to devel-leave(a)ovirt.org
> >>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >>>> oVirt Code of Conduct:
> >>>> https://www.ovirt.org/community/about/community-guidelines/
> >>>> List Archives:
> >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QELJ7YNZVW6...
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Devel mailing list -- devel(a)ovirt.org
> >>> To unsubscribe send an email to devel-leave(a)ovirt.org
> >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >>> oVirt Code of Conduct:
> >>> https://www.ovirt.org/community/about/community-guidelines/
> >>> List Archives:
> >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YIMB6QHQ37D...
> >>>
> >> _______________________________________________
> >> Devel mailing list -- devel(a)ovirt.org
> >> To unsubscribe send an email to devel-leave(a)ovirt.org
> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YBK7IHQELSE...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1834:
-------------------------------------
{quote}
I know that signal handling in Jenkins is a difficult task. Maybe let's change the job to wipe the workspace before running git?
{quote}
That would destroy all the caches we worked very hard to keep around, including the Git cache itself which cab be quite significant.
As I already commented elsewhere, this is not an easy problem to solve in our current architecture:
For V1 Jobs - because Jenkins freestyle jobs do not allow you to easily add functionality before the git cloning is performed.
For V2 jobs - pipelines to not allow you to embed arbitrary shell scripts in the jobs so you need to clone the repo before you can run any meaningful preparation steps.
This issue is essentially an aspect of what we call "the chicken and egg" issue where we have to prepare the Jenkins slave before we can clone any code to it, but we need the code to do the preparation. Our current direction for solving this long-term is to move the slave preparation steps out from the jobs (OVIRT-1984)
> Jenkins failure - perhaps bad permissions
> -----------------------------------------
>
> Key: OVIRT-1834
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tes...
> *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01*
> hudson.plugins.git.GitException: Failed to fetch from
> git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at
> hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at
> hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01*
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at
> org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01*
> at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01*
> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01*
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01*
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01*
> at hudson.model.Run.execute(Run.java:1724)*10:53:01* at
> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at
> hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01*
> at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by:
> hudson.plugins.git.GitException: Command "git clean -fdx" returned
> status code 1:*10:53:01* stdout: Removing
> basic-suite-master/LagoInitFile*10:53:01* Removing
> basic-suite-master/extra_sources*10:53:01* Removing
> basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing
> basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01*
> Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing
> basic-suite-master/test_utils/constants.pyc*10:53:01* Removing
> basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing
> exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01*
> Removing mock_script_sid.x4jv1R*10:53:01* Removing
> mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning:
> failed to remove .pki/*10:53:01* warning: failed to remove
> deployment-basic-suite-master/default/uuid*10:53:01* warning: failed
> to remove deployment-basic-suite-master/default/id_rsa
> ...
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2136) Fwd: [ovirt-devel] Re: Propose Milan Zamazal as
virt maintainer
by danken (oVirt JIRA)
danken created OVIRT-2136:
-----------------------------
Summary: Fwd: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
Key: OVIRT-2136
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2136
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: danken
Assignee: infra
Please add Milan to vdsm-maintainers list.
---------- Forwarded message ----------
From: Edward Haas <ehaas(a)redhat.com>
Date: Mon, Jun 4, 2018 at 3:35 PM
Subject: Re: [ovirt-devel] Re: Propose Milan Zamazal as virt maintainer
To: "devel(a)ovirt.org" <devel(a)ovirt.org>
Cc: Piotr Kliczewski <piotr.kliczewski(a)gmail.com>, Edward Haas
<edwardh(a)redhat.com>, Arik Hadas <ahadas(a)redhat.com>, Dan Kenigsberg
<danken(a)redhat.com>
+1
Thanks,
Edy.
> On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote:
>
> Approved.
>
> On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski
> <piotr.kliczewski(a)gmail.com> wrote:
>> +1
>>
>>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote:
>>>
>>>
>>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
>>>>
>>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani <fromani(a)redhat.com>
>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Milan Zamazal has been working on the oVirt project for more than 2.5
>>>>> years.
>>>>> Let me highlight some of his many contributions to the project:
>>>>>
>>>>> - Since January this year - 2018, he's been a maintainer for the stable
>>>>> branches.
>>>>> - He developed important features like memory hotunplug, which required
>>>>> tight cooperation
>>>>> and communication with the other layers of the stack (libvirt, qemu).
>>>>> - He is a mentor in the Outreachy program, which lead to creation of the
>>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer
>>>>> - He contributed more than 290 patches to the Vdsm project in master
>>>>> branch alone, excluding backports and contributions to Engine
>>>>> - He contributed and is contributing testcases and fixes to the oVirt
>>>>> System Test suite, a tool which was already pivotal in ensuring the
>>>>> quality of the oVirt project.
>>>>>
>>>>> As reviewer, Milan is responsive and his comments are always
>>>>> comprehensive and well focused,
>>>>> with strong attitude towards getting things done and done right.
>>>>>
>>>>> Milan also demonstrated his ability to adapt to the needs of the project:
>>>>> - he demonstrated careful and thoughtful patch management while
>>>>> maintaining the stable branches
>>>>> - he also demonstrated he's not shy to tackle large and needed changes
>>>>> during the 4.1 and 4.2 cycles,
>>>>> when we deeply reorganized the XML processing in the virt code.
>>>>>
>>>>> For those reasons, and many more, I think he will be a good addition to
>>>>> the maintainers team, and I propose him as virt co-maintainer.
>>>>>
>>>>> Please share your thoughts
>>>>
>>>>
>>>> +1
>>>
>>>
>>> FWIW, +1
>>>
>>>>
>>>>
>>>> Nir
>>>>
>>>>
>>>> _______________________________________________
>>>> Devel mailing list -- devel(a)ovirt.org
>>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QELJ7YNZVW6...
>>>>
>>>
>>>
>>> _______________________________________________
>>> Devel mailing list -- devel(a)ovirt.org
>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YIMB6QHQ37D...
>>>
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
>> List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YBK7IHQELSE...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-1834) Jenkins failure - perhaps bad permissions
by Gal Ben Haim (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1834?page=com.atlassian.jir... ]
Gal Ben Haim commented on OVIRT-1834:
-------------------------------------
I don't see any valid solution from OST side.
[~bkorren(a)redhat.com] [~dbelenky(a)redhat.com] any idea how we can solve it?
I know that signal handling in Jenkins is a difficult task. Maybe let's change the job to wipe the workspace before running git?
> Jenkins failure - perhaps bad permissions
> -----------------------------------------
>
> Key: OVIRT-1834
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1834
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: infra
>
> http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tes...
> *10:53:01* ERROR: Error fetching remote repo 'origin'*10:53:01*
> hudson.plugins.git.GitException: Failed to fetch from
> git://gerrit.ovirt.org/ovirt-system-tests.git*10:53:01* at
> hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:825)*10:53:01* at
> hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1092)*10:53:01*
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)*10:53:01* at
> org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)*10:53:01*
> at hudson.scm.SCM.checkout(SCM.java:495)*10:53:01* at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1202)*10:53:01*
> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)*10:53:01*
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)*10:53:01*
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)*10:53:01*
> at hudson.model.Run.execute(Run.java:1724)*10:53:01* at
> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:53:01* at
> hudson.model.ResourceController.execute(ResourceController.java:97)*10:53:01*
> at hudson.model.Executor.run(Executor.java:421)*10:53:01* Caused by:
> hudson.plugins.git.GitException: Command "git clean -fdx" returned
> status code 1:*10:53:01* stdout: Removing
> basic-suite-master/LagoInitFile*10:53:01* Removing
> basic-suite-master/extra_sources*10:53:01* Removing
> basic-suite-master/reposync-config.repo_repoclosure*10:53:01* Removing
> basic-suite-master/test-scenarios/000_check_repo_closure.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/001_initialize_engine.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/002_bootstrap.pyc*10:53:01*
> Removing basic-suite-master/test-scenarios/003_00_metrics_bootstrap.pyc*10:53:01*
> Removing basic-suite-master/test_utils/__init__.pyc*10:53:01* Removing
> basic-suite-master/test_utils/constants.pyc*10:53:01* Removing
> basic-suite-master/test_utils/network_utils_v4.pyc*10:53:01* Removing
> exported-artifacts/*10:53:01* Removing mock_logs.LjHRcpGf/*10:53:01*
> Removing mock_script_sid.x4jv1R*10:53:01* Removing
> mocker-epel-7-x86_64.el7.cfg*10:53:01* *10:53:01* stderr: warning:
> failed to remove .pki/*10:53:01* warning: failed to remove
> deployment-basic-suite-master/default/uuid*10:53:01* warning: failed
> to remove deployment-basic-suite-master/default/id_rsa
> ...
> --
> Didi
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jir... ]
Dafna Ron updated OVIRT-2076:
-----------------------------
Resolution: Fixed
Status: Done (was: To Do)
> name clash on vdsm module at host-deploy
> ----------------------------------------
>
> Key: OVIRT-2076
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2076
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: cq-issue-traking, ost_code_regression, ost_failures
>
> Add host is failing and was reported by gal for hc
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te...
> (Relevant) error snippet from the host deploy log:
> <error>
> 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None)
> 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported
> 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception
> Traceback (most recent call last):
> File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod
> method['method']()
> File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf
> _('Cannot resolve ovirt_hosted_engine_ha module')
> RuntimeError: Cannot resolve ovirt_hosted_engine_ha module
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jir... ]
Dafna Ron commented on OVIRT-2076:
----------------------------------
Both passed on CQ and the vdsm build was fixed.
> name clash on vdsm module at host-deploy
> ----------------------------------------
>
> Key: OVIRT-2076
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2076
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: cq-issue-traking, ost_code_regression, ost_failures
>
> Add host is failing and was reported by gal for hc
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te...
> (Relevant) error snippet from the host deploy log:
> <error>
> 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None)
> 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported
> 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception
> Traceback (most recent call last):
> File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod
> method['method']()
> File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf
> _('Cannot resolve ovirt_hosted_engine_ha module')
> RuntimeError: Cannot resolve ovirt_hosted_engine_ha module
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
