[JIRA] (OVIRT-1827) Re: Access to run OST

[Daniel Belenky (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Belenky closed OVIRT-1827.
-
Resolution: Fixed

Patch to add user to whitelist was merged.

> Re: Access to run OST
> -
>
> Key: OVIRT-1827
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1827
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> fwd to infra-support
> On Wed, Jan 3, 2018 at 1:49 PM, Mor Kalfon  wrote:
> > Dear Infra team,
> >
> > Would it be possible to get a permission to test my (first) patch in OST?
> >
> > https://gerrit.ovirt.org/#/c/85930/
> >
> > Regards,
> > --
> > Mor Kalfon
> > RHV Networking Team
> > Red Hat IL-Raanana
> > Tel: +972-54-6514148 <+972%2054-651-4148>
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 369 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/369/
Build Number: 369
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #355
[Yuval Turgeman] automation: view install log in console output


Changes for Build #356
[Yuval Turgeman] automation: view install log in console output


Changes for Build #357
[Yuval Turgeman] automation: view install log in console output


Changes for Build #358
[Yuval Turgeman] automation: view install log in console output


Changes for Build #359
[Eyal Edri] period cleanup: removing non working emails

[Yuval Turgeman] automation: view install log in console output


Changes for Build #360
[Dan Kenigsberg] add network suite to manaul job suite selector

[Yuval Turgeman] automation: view install log in console output


Changes for Build #361
[Nir Soffer] ioprocess: Exclude fc2* ppc64le tests

[Yuval Turgeman] automation: view install log in console output


Changes for Build #362
[Eyal Edri] he suite: add more maintainers to email alerts

[Eyal Edri] remove getbadgets Jenkins intergration

[Yuval Turgeman] automation: view install log in console output


Changes for Build #363
[Nir Soffer] ioprocess: Disable build-artifacts on fedora/ppc64le

[Yuval Turgeman] automation: view install log in console output


Changes for Build #364
[Yuval Turgeman] automation: view install log in console output


Changes for Build #365
[Yuval Turgeman] automation: view install log in console output


Changes for Build #366
[Yuval Turgeman] automation: view install log in console output


Changes for Build #367
[Yuval Turgeman] automation: view install log in console output


Changes for Build #368
[Yuval Turgeman] automation: view install log in console output


Changes for Build #369
[Gal Ben Haim] mirros: Update centos-ovirt-4.2 repo

[Yuval Turgeman] automation: view install log in console output




-
Failed Tests:
-
No tests ran.___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 85870,6 (vdsm) failed "ovirt-master" system tests

[oVirt Jenkins]

Change 85870,6 (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/85870/6

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4626/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 85908,6 (ovirt-engine) failed "ovirt-master" system tests

[oVirt Jenkins]

Change 85908,6 (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/85908/6

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4618/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1827) Re: Access to run OST

[Daniel Belenky (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Belenky updated OVIRT-1827:
--
Status: In Progress  (was: To Do)

> Re: Access to run OST
> -
>
> Key: OVIRT-1827
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1827
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Daniel Belenky
>Assignee: infra
>
> fwd to infra-support
> On Wed, Jan 3, 2018 at 1:49 PM, Mor Kalfon  wrote:
> > Dear Infra team,
> >
> > Would it be possible to get a permission to test my (first) patch in OST?
> >
> > https://gerrit.ovirt.org/#/c/85930/
> >
> > Regards,
> > --
> > Mor Kalfon
> > RHV Networking Team
> > Red Hat IL-Raanana
> > Tel: +972-54-6514148 <+972%2054-651-4148>
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1827) Re: Access to run OST

[Daniel Belenky (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Belenky reassigned OVIRT-1827:
-

Assignee: Daniel Belenky  (was: infra)

> Re: Access to run OST
> -
>
> Key: OVIRT-1827
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1827
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> fwd to infra-support
> On Wed, Jan 3, 2018 at 1:49 PM, Mor Kalfon  wrote:
> > Dear Infra team,
> >
> > Would it be possible to get a permission to test my (first) patch in OST?
> >
> > https://gerrit.ovirt.org/#/c/85930/
> >
> > Regards,
> > --
> > Mor Kalfon
> > RHV Networking Team
> > Red Hat IL-Raanana
> > Tel: +972-54-6514148 <+972%2054-651-4148>
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 85943, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-4.2" change queue including change 85943,1
(ovirt-engine-api-model) failed. However, this change seems not to be the root
cause for this failure. Change 84359,1 (ovirt-engine-api-model) 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 84359,1 (ovirt-engine-api-
model) 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/85943/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/84359/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/191/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 85944, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-4.2" change queue including change 85944,1
(ovirt-engine-api-model) failed. However, this change seems not to be the root
cause for this failure. Change 84359,1 (ovirt-engine-api-model) 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 84359,1 (ovirt-engine-api-
model) 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/85944/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/84359/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/190/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 85942, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-4.2" change queue including change 85942,1
(ovirt-engine-api-model) failed. However, this change seems not to be the root
cause for this failure. Change 84359,1 (ovirt-engine-api-model) 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 84359,1 (ovirt-engine-api-
model) 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/85942/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/84359/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/188/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 85934, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

[oVirt Jenkins]

A system test invoked by the "ovirt-4.2" change queue including change 85934,1
(ovirt-engine-api-model) failed. However, this change seems not to be the root
cause for this failure. Change 84359,1 (ovirt-engine-api-model) 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 84359,1 (ovirt-engine-api-
model) 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/85934/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/84359/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/186/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1827) Re: Access to run OST

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-1827:
-

 Summary: Re: Access to run OST
 Key: OVIRT-1827
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1827
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Daniel Belenky
Assignee: infra


fwd to infra-support

On Wed, Jan 3, 2018 at 1:49 PM, Mor Kalfon  wrote:

> Dear Infra team,
>
> Would it be possible to get a permission to test my (first) patch in OST?
>
> https://gerrit.ovirt.org/#/c/85930/
>
> Regards,
> --
> Mor Kalfon
> RHV Networking Team
> Red Hat IL-Raanana
> Tel: +972-54-6514148 <+972%2054-651-4148>
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 

DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Access to run OST

[Daniel Belenky]

fwd to infra-support

On Wed, Jan 3, 2018 at 1:49 PM, Mor Kalfon  wrote:

> Dear Infra team,
>
> Would it be possible to get a permission to test my (first) patch in OST?
>
> https://gerrit.ovirt.org/#/c/85930/
>
> Regards,
> --
> Mor Kalfon
> RHV Networking Team
> Red Hat IL-Raanana
> Tel: +972-54-6514148 <+972%2054-651-4148>
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 

DANIEL BELENKY
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Access to run OST

[Mor Kalfon]

Dear Infra team,

Would it be possible to get a permission to test my (first) patch in OST?

https://gerrit.ovirt.org/#/c/85930/

Regards,
-- 
Mor Kalfon
RHV Networking Team
Red Hat IL-Raanana
Tel: +972-54-6514148
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1826) Re: [lago-project/lago] Log running ssh_script (#691)

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1826:

Resolution: Won't Fix
Status: Done  (was: To Do)

no need to open a ticket for this, this is a task for lago maintainers, not the 
ovirt infa team (there is an intersection between the two groups, thoug, but 
lago tasks are tracked in github), and I'm sure they got enough emails about 
your PR by now)

> Re: [lago-project/lago] Log running ssh_script (#691)
> -
>
> Key: OVIRT-1826
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1826
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Can someone please approve me and/or review etc.? Thanks.
> On Wed, Jan 3, 2018 at 12:40 PM, oVirt infra bot 
> wrote:
> > Hello contributor, thanks for submitting a PR for this project!
> >
> > I am the bot who triggers "standard-CI" builds for this project.
> > As a security measure, I will not run automated tests on PRs that are not
> > from white-listed contributors.
> >
> > In order to allow automated tests to run, please ask one of the project
> > maintainers to review the code and then do one of the following:
> >
> >1. Type ci test please on this PR to trigger automated tests for it.
> >2. Type ci add to whitelist on this PR to trigger automated tests for
> >it and also add you to the contributor white-list so that your future PRs
> >will be tested automatically.
> >3. If you are planning to contribute to more than one project, maybe
> >it's better to ask them to add you to the project organization, so you'll
> >be able to run tests for all the organization's projects.
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > ,
> > or mute the thread
> > 
> > .
> >
> -- 
> Didi



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1826) Re: [lago-project/lago] Log running ssh_script (#691)

[Yedidyah Bar David (oVirt JIRA)]

Yedidyah Bar David created OVIRT-1826:
-

 Summary: Re: [lago-project/lago] Log running ssh_script (#691)
 Key: OVIRT-1826
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1826
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra


Can someone please approve me and/or review etc.? Thanks.

On Wed, Jan 3, 2018 at 12:40 PM, oVirt infra bot 
wrote:

> Hello contributor, thanks for submitting a PR for this project!
>
> I am the bot who triggers "standard-CI" builds for this project.
> As a security measure, I will not run automated tests on PRs that are not
> from white-listed contributors.
>
> In order to allow automated tests to run, please ask one of the project
> maintainers to review the code and then do one of the following:
>
>1. Type ci test please on this PR to trigger automated tests for it.
>2. Type ci add to whitelist on this PR to trigger automated tests for
>it and also add you to the contributor white-list so that your future PRs
>will be tested automatically.
>3. If you are planning to contribute to more than one project, maybe
>it's better to ask them to add you to the project organization, so you'll
>be able to run tests for all the organization's projects.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 
> .
>



-- 
Didi



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[vdsm][tag][master] Vdsm tagged: v4.20.10

[Francesco Romani]

Hi infra,

we have a new Vdsm tag on branch master for oVirt 4.2.1:

tag v4.20.10
Tagger: Francesco Romani 
Date:   Wed Jan 3 11:01:15 2018 +0100

Vdsm 4.20.10 for oVirt 4.2.1 RC 1

commit 00bc04e666b7660d052f04718a9cf10cf7848235

+++

NOTE ABOUT BRANCHING:
* We are merging again patches targeted for 4.2.1 on master
* We don't yet have plans to branch out ovirt-4.2 from master.
Following the usual Vdsm habit, we will branch out late, *after* Engine
does.


Bests,

-- 
Francesco Romani
Senior SW Eng., Virtualization R
Red Hat
IRC: fromani github: @fromanirh

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra