[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 931 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/931/
Build Number: 931
Build Status:  Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/47337

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model




-
Failed Tests:
-
No tests ran. 

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

[vdsm] merge rights on master branch

[Dan Kenigsberg]

Nir Soffer has been contributing to Vdsm for more than two years now.
Beyond his storage-related expertise, he is well-known for his thorough
code reviews and his pains when the master branch is broken. It's time
for him to take even bigger responsibility.

David, please grant Nir Soffer with merge rights on the master branch of
Vdsm.

I'll keep merging network, virt, and infra patches myself, but much less
than before. Adam keeps his merge right as before (he tends to use them
on emergencies only).

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

Re: [vdsm] merge rights on master branch

[David Caro]

Done, let me know if you need me to add him any more permissions (vdsm
permisson groups is a bit complicated, I might have missed something)

On 11/17 12:47, Dan Kenigsberg wrote:
> Nir Soffer has been contributing to Vdsm for more than two years now.
> Beyond his storage-related expertise, he is well-known for his thorough
> code reviews and his pains when the master branch is broken. It's time
> for him to take even bigger responsibility.
> 
> David, please grant Nir Soffer with merge rights on the master branch of
> Vdsm.
> 
> I'll keep merging network, virt, and infra patches myself, but much less
> than before. Adam keeps his merge right as before (he tends to use them
> on emergencies only).
> 
> Regards,
> Dan.

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 932 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/932/
Build Number: 932
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48580

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #932
[Arik Hadas] core: eliminate CDA on export RAM snapshot




-
Failed Tests:
-
No tests ran. 

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

Re: [ovirt-devel] Maintainer rights on vdsm - ovirt-3.5-gluster

[Sahina Bose]

Thanks!

On 11/16/2015 07:44 PM, David Caro wrote:

Done!

On 11/16 15:28, Dan Kenigsberg wrote:

On Wed, Apr 29, 2015 at 10:03:47AM +0200, David Caro wrote:

Done

On 04/20, Dan Kenigsberg wrote:

On Mon, Apr 20, 2015 at 03:20:18PM +0530, Sahina Bose wrote:

Hi!

On the vdsm branch "ovirt-3.5-gluster", could you provide merge rights to
Bala (barum...@redhat.com) ?

+1 from me.

ovirt-3.5-gluster needs a rebase on top of the current ovirt-3.5

Thanks. Few months have passed, and now we need Sahina herself as an
admin of the this branch. Would you please add her as well?


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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 842 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/842/
Build Number: 842
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48580

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #842
[Arik Hadas] core: eliminate CDA on export RAM snapshot




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 844 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/844/
Build Number: 844
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/47706

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #842
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #843
[Eli Mesika] db: fix erroneous formatting


Changes for Build #844
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 934 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/934/
Build Number: 934
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/47706

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #932
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #933
[Eli Mesika] db: fix erroneous formatting


Changes for Build #934
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 933 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/933/
Build Number: 933
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48665

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #932
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #933
[Eli Mesika] db: fix erroneous formatting




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 843 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/843/
Build Number: 843
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48665

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #842
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #843
[Eli Mesika] db: fix erroneous formatting




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged » x86_64,epel-7 - Build # 65 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=epel-7/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=epel-7/65/
Build Number: 65
Build Status:  Failure
Triggered By: Started by upstream project 
"ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged" build number 65

-
Changes Since Last Success:
-
Changes for Build #65
[Ryan Barry] Refresh the status of the engine every time the UI is reloaded




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-node-plugin-hosted-engine_master_create-rpms_merged » x86_64,fedora-21 - Build # 83 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=fedora-21/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=fedora-21/83/
Build Number: 83
Build Status:  Failure
Triggered By: Started by upstream project 
"ovirt-node-plugin-hosted-engine_master_create-rpms_merged" build number 83

-
Changes Since Last Success:
-
Changes for Build #83
[Ryan Barry] Refresh the status of the engine every time the UI is reloaded




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 845 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/845/
Build Number: 845
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/46515

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #842
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #843
[Eli Mesika] db: fix erroneous formatting


Changes for Build #844
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only


Changes for Build #845
[Roy Golan] core: Auto import Hosted Engine Storage Domain




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 846 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/846/
Build Number: 846
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/44268

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #842
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #843
[Eli Mesika] db: fix erroneous formatting


Changes for Build #844
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only


Changes for Build #845
[Roy Golan] core: Auto import Hosted Engine Storage Domain


Changes for Build #846
[Yedidyah Bar David] packaging: setup: nicer error messages about pg conf




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 935 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/935/
Build Number: 935
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/46515

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #932
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #933
[Eli Mesika] db: fix erroneous formatting


Changes for Build #934
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only


Changes for Build #935
[Roy Golan] core: Auto import Hosted Engine Storage Domain




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-node-plugin-hosted-engine_master_create-rpms_merged » x86_64,epel-7 - Build # 83 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=epel-7/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=epel-7/83/
Build Number: 83
Build Status:  Failure
Triggered By: Started by upstream project 
"ovirt-node-plugin-hosted-engine_master_create-rpms_merged" build number 83

-
Changes Since Last Success:
-
Changes for Build #83
[Ryan Barry] Refresh the status of the engine every time the UI is reloaded




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged - Build # 65 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_3.5_create-rpms_merged/65/
Build Number: 65
Build Status:  Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48508

-
Changes Since Last Success:
-
Changes for Build #65
[Ryan Barry] Refresh the status of the engine every time the UI is reloaded




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-node-plugin-hosted-engine_master_create-rpms_merged - Build # 83 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/83/
Build Number: 83
Build Status:  Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48508

-
Changes Since Last Success:
-
Changes for Build #83
[Ryan Barry] Refresh the status of the engine every time the UI is reloaded




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-node-plugin-hosted-engine_master_create-rpms_merged » x86_64,fedora-22 - Build # 83 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=fedora-22/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-node-plugin-hosted-engine_master_create-rpms_merged/ARCH=x86_64,DISTRIBUTION=fedora-22/83/
Build Number: 83
Build Status:  Failure
Triggered By: Started by upstream project 
"ovirt-node-plugin-hosted-engine_master_create-rpms_merged" build number 83

-
Changes Since Last Success:
-
Changes for Build #83
[Ryan Barry] Refresh the status of the engine every time the UI is reloaded




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 936 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/936/
Build Number: 936
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/44268

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #932
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #933
[Eli Mesika] db: fix erroneous formatting


Changes for Build #934
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only


Changes for Build #935
[Roy Golan] core: Auto import Hosted Engine Storage Domain


Changes for Build #936
[Yedidyah Bar David] packaging: setup: nicer error messages about pg conf




-
Failed Tests:
-
No tests ran. 

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 841 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/841/
Build Number: 841
Build Status:  Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/47337

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model




-
Failed Tests:
-
No tests ran. 

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

Re: [ovirt-devel] Reported-By - giving credit to our testers

[David Caro]

On 11/13 08:55, Sandro Bonazzola wrote:
> On Thu, Nov 12, 2015 at 3:45 PM, Nir Soffer  wrote:
> 
> > Hi all,
> >
> > Our QE (and sometimes our users) are working hard testing and
> > reporting bugs, but
> > their effort is never mentioned in our code.
> >
> > Looking at kernel git history, I found that they are using the
> > Reported-By header for
> > giving credit to the person reporting a bug. I suggest we adapt this
> > header.
> >
> > Here are some examples how we can use it:
> >
> > - https://gerrit.ovirt.org/#/c/48483/3//COMMIT_MSG
> > -
> > https://github.com/oVirt/vdsm/commit/fb4c72af5e4c200409c74834111d44d92959ebbd
> > -
> > https://github.com/oVirt/vdsm/commit/f8127d88add881a4775e7030dde2433125c7b598
> 
> 
> infra: looking at above commit messages, can we get automatically added the
> following lines?
> 
> Reviewed-on: https://gerrit.ovirt.org/46540
> on patch creation
> 
> Reviewed-by: Francesco Romani 
> on patch comment

There's no easy way to plug in extra stuff, that is done on vdsm by gerrit
itself because the project is set to 'cherry-pick', but that has consequences,
for starters, when you submit a patch, the commit that gets in is not the same
that you where reviewing (as the commit message changed) and thus you will be
forced to rebase all the patches that depended on it.

There's no built-in way either to change the commit on push (when
updating/creating the patch) without creating a new patch. That means that to
have that added, each time you send a patch a new one will be created, and each
time you add a comment for the first time to the patch, another patch will be
created too. Forcing the devel to refetch the commit each time he/she pushes.

Not sure that smoothes up the dev process...

I think that the less painful path will be to use a commit hook locally, so the
commit message is changed locally first, but that will require the dev to
install it (we can ease that with a script or similar though)


> 
> 
> 
> >
> >
> > Thanks,
> > Nir
> > ___
> > Devel mailing list
> > de...@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
> >
> 
> 
> 
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com

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


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Improving our github presense

[Nir Soffer]

Hi all,

Looking in ovirt github page, there are only 2 members:
https://github.com/orgs/oVirt/people

Is is possible to add automatically all contributors to this list?

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

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 847 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/847/
Build Number: 847
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48686

-
Changes Since Last Success:
-
Changes for Build #841
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #842
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #843
[Eli Mesika] db: fix erroneous formatting


Changes for Build #844
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only


Changes for Build #845
[Roy Golan] core: Auto import Hosted Engine Storage Domain


Changes for Build #846
[Yedidyah Bar David] packaging: setup: nicer error messages about pg conf


Changes for Build #847
[Juan Hernandez] core: Make SUPPORTED_DOMAIN_TYPES package protected




-
Failed Tests:
-
No tests ran. 

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

Re: automation wrongly moving bugs to MODIFIED

[Eyal Edri]

On Tue, Nov 17, 2015 at 10:53 AM, Yedidyah Bar David 
wrote:

> On Tue, Nov 17, 2015 at 10:47 AM, David Caro  wrote:
> > On 11/17 10:44, Yedidyah Bar David wrote:
> >> See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
> >> was moved to modified. When I later pushed the patch to 3.6, it
> >> correctly moved it back to POST. Not sure we should even automatically
> >> move to modified if merged to 3.6, because there might be other
> >> changes needed for that bug - it might be best to let the owner to
> >> decide.
> >
> > The issue here is that there's no way for the hooks to know that you
> will be
> > pushing more patches, so when it saw that there were no more open
> patches it
> > moved the bug to MODIFIED. Is there any reason why you did not open the
> patches
> > first?
>
> There are two different issues here:
>
> 1. If merging to master branch, and bug is 3.6, bug should not be
> moved to modified
> at all.
>

imo, the gerrit hook should give -1 on this.
either don't put bug-url at all, or put 4.0 bug-url.


>
> 2. If merging to 3.6 branch, and bug is 3.6, we might or might not
> want to move to
> modified. Not always people push all patches at once - sometimes they
> prefer to have
> some preparation patch merged (perhaps after a long review process, during
> which
> the patch is changed quite a lot), then continue with more patches. This
> wasn't
> current case, although I still think we might want to open it to
> discussion.
>

i replied on this on the previous reply


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


-- 
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: automation wrongly moving bugs to MODIFIED

[Eyal Edri]

indeed.
we need to decide here what automation we want (each flow has its cons &
pros)

moving bugs from POST->MODIFIED
  - pros
- bugs are not forgotten on POST and waiting for manual action,
leaving possibility of not moving to ON_QA on a release even though they
are fixed.

 - cons
- bot can't know if bug is solved completely and more patches are
coming.


solution:
- use bug-url ONLY in the main patch that when its merged then
bug will move to MODIFIED, all other patches should use related-to: (we can
ensure bug won't change status for related to patches)


moving MODIFIED->POST
  - i think in any case we should stop doing this, and its the
maintainer responsibility to move it back to POST if he didn't add all
patches.
  - adding a comment will help the bug owner know about this issue.

e.





On Tue, Nov 17, 2015 at 10:47 AM, David Caro  wrote:

> On 11/17 10:44, Yedidyah Bar David wrote:
> > See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
> > was moved to modified. When I later pushed the patch to 3.6, it
> > correctly moved it back to POST. Not sure we should even automatically
> > move to modified if merged to 3.6, because there might be other
> > changes needed for that bug - it might be best to let the owner to
> > decide.
>
> The issue here is that there's no way for the hooks to know that you will
> be
> pushing more patches, so when it saw that there were no more open patches
> it
> moved the bug to MODIFIED. Is there any reason why you did not open the
> patches
> first?
>
> >
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1282397
> >
> > Best,
> > --
> > Didi
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R
>
> Tel.: +420 532 294 605
> Email: dc...@redhat.com
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: automation wrongly moving bugs to MODIFIED

[Yedidyah Bar David]

On Tue, Nov 17, 2015 at 10:54 AM, Eyal Edri  wrote:
> indeed.
> we need to decide here what automation we want (each flow has its cons &
> pros)
>
> moving bugs from POST->MODIFIED
>   - pros
> - bugs are not forgotten on POST and waiting for manual action,
> leaving possibility of not moving to ON_QA on a release even though they are
> fixed.

I think it's still a bit risky and should be left for a human. At least as long
as we do not do TDD.

>
>  - cons
> - bot can't know if bug is solved completely and more patches are
> coming.
>
>
> solution:
> - use bug-url ONLY in the main patch that when its merged then
> bug will move to MODIFIED, all other patches should use related-to: (we can
> ensure bug won't change status for related to patches)

I can live with this, but as I wrote in another mail in this thread, I think
that's a bit overloading the meaning of Related-To.

>
>
> moving MODIFIED->POST
>   - i think in any case we should stop doing this, and its the
> maintainer responsibility to move it back to POST if he didn't add all
> patches.

Really? Do you see any risk in moving to POST?
-- 
Didi
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: automation wrongly moving bugs to MODIFIED

[Yedidyah Bar David]

On Tue, Nov 17, 2015 at 11:10 AM, David Caro  wrote:
> On 11/17 11:06, Yedidyah Bar David wrote:
>> On Tue, Nov 17, 2015 at 10:56 AM, Eyal Edri  wrote:
>> >
>> >
>> > On Tue, Nov 17, 2015 at 10:53 AM, Yedidyah Bar David 
>> > wrote:
>> >>
>> >> On Tue, Nov 17, 2015 at 10:47 AM, David Caro  wrote:
>> >> > On 11/17 10:44, Yedidyah Bar David wrote:
>> >> >> See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
>> >> >> was moved to modified. When I later pushed the patch to 3.6, it
>> >> >> correctly moved it back to POST. Not sure we should even automatically
>> >> >> move to modified if merged to 3.6, because there might be other
>> >> >> changes needed for that bug - it might be best to let the owner to
>> >> >> decide.
>> >> >
>> >> > The issue here is that there's no way for the hooks to know that you
>> >> > will be
>> >> > pushing more patches, so when it saw that there were no more open
>> >> > patches it
>> >> > moved the bug to MODIFIED. Is there any reason why you did not open the
>> >> > patches
>> >> > first?
>> >>
>> >> There are two different issues here:
>> >>
>> >> 1. If merging to master branch, and bug is 3.6, bug should not be
>> >> moved to modified
>> >> at all.
>> >
>> >
>> > imo, the gerrit hook should give -1 on this.
>> > either don't put bug-url at all, or put 4.0 bug-url.
>>
>> Not sure about this. I agree it makes some sense. It definitely don't need to
>> move to modified :-)
>>
>> Since we decided to not always clone bugs, and since we require merging to
>> master before merging to stable branch, I think it does make sense to include
>> the bug-url even in the master patch. obviously, Related-To is also good 
>> enough,
>> even though a bit misleading - I usually write Related-To when the patch is 
>> not
>> directly part of a fix for a bug but only related to it.
>
> We used the related-to in the past, but iirc it was dropped as not everyone
> used it and people that did, used it for different things.
>
> I still think that opening all the patches before merging any of them is a 
> good
> solution.

Perhaps, if everyone is well aware of this.

I still think there is no good reason to take this risk.

I think saying "This bug is fixed" should always be left to a human.

We have bots (or at least people doing this in bulk) for moving bugs
from modified
to QA. Moving to POST to MODIFIED is the only step left for a human to
decide. IMO
it should left so.
-- 
Didi
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: automation wrongly moving bugs to MODIFIED

[Yedidyah Bar David]

On Tue, Nov 17, 2015 at 10:47 AM, David Caro  wrote:
> On 11/17 10:44, Yedidyah Bar David wrote:
>> See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
>> was moved to modified. When I later pushed the patch to 3.6, it
>> correctly moved it back to POST. Not sure we should even automatically
>> move to modified if merged to 3.6, because there might be other
>> changes needed for that bug - it might be best to let the owner to
>> decide.
>
> The issue here is that there's no way for the hooks to know that you will be
> pushing more patches, so when it saw that there were no more open patches it
> moved the bug to MODIFIED. Is there any reason why you did not open the 
> patches
> first?

There are two different issues here:

1. If merging to master branch, and bug is 3.6, bug should not be
moved to modified
at all.

2. If merging to 3.6 branch, and bug is 3.6, we might or might not
want to move to
modified. Not always people push all patches at once - sometimes they
prefer to have
some preparation patch merged (perhaps after a long review process, during which
the patch is changed quite a lot), then continue with more patches. This wasn't
current case, although I still think we might want to open it to discussion.
-- 
Didi
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Logwatch for linode01.ovirt.org (Linux)

[logwatch]

 ### Logwatch 7.3.6 (05/19/07)  
Processing Initiated: Tue Nov 17 03:26:09 2015
Date Range Processed: yesterday
  ( 2015-Nov-16 )
  Period is day.
  Detail Level of Output: 0
  Type of Output: unformatted
   Logfiles for Host: linode01.ovirt.org
  ## 
 
 - Dovecot Begin  

 Dovecot disconnects:
Logged out: 2 Time(s)
no auth attempts: 4 Time(s) 
 -- Dovecot End - 

 
 - httpd Begin  

 
 A total of 1 sites probed the server 
162.144.119.155
 
 Requests with error response codes
400 Bad Request
   /admin.php: 1 Time(s)
   /admin/: 1 Time(s)
   /admin/login.php: 1 Time(s)
   /administrator/index.php: 1 Time(s)
   /bitrix/admin/index.php?lang=en: 1 Time(s)
   /index.php: 1 Time(s)
   /user/: 1 Time(s)
   /wp-login.php: 1 Time(s)
404 Not Found
   /: 577 Time(s)
   /**pipermail/users/2012-March/**001158.htm ... rch/001158.html: 1 Time(s)
   //wp-admin/admin-ajax.php: 1 Time(s)
   //wp-admin/admin-ajax.php?action=revolutio ... ./wp-config.php: 1 Time(s)
   //wp-admin/admin-ajax.php?action=revslider ... ./wp-config.php: 1 Time(s)
   //wp-admin/includes/themes.php?x1: 1 Time(s)
   //wp-admin/options-link.php?x1: 1 Time(s)
   //xmlrpc.php: 5 Time(s)
   /:: 1 Time(s)
   /mailman/listinfo/users: 1 Time(s)
   /__mailman/listinfo/users: 1 Time(s)
   /admin.php: 5 Time(s)
   /admin/: 5 Time(s)
   /admin/login.php: 5 Time(s)
   /administrator/index.php: 5 Time(s)
   /apple-touch-icon-precomposed.png: 2 Time(s)
   /apple-touch-icon.png: 2 Time(s)
   /bitrix/admin/index.php?lang=en: 5 Time(s)
   /blog/: 1 Time(s)
   /blog/robots.txt: 1 Time(s)
   /blog/wp-admin/: 6 Time(s)
   /category/news/feed: 1 Time(s)
   /category/news/feed/: 18 Time(s)
   /favicon.ico: 808 Time(s)
   /news-and-events/workshop/: 1 Time(s)
   /old/wp-admin/: 7 Time(s)
   /pipermail/2011-September/date.html: 1 Time(s)
   /pipermail/2011-September/subject.html: 1 Time(s)
   /pipermail/2012-August/date.html: 1 Time(s)
   /pipermail/2014-May/subject.html: 1 Time(s)
   /pipermail/2015-June/thread.html: 1 Time(s)
   /pipermail/devel/2012-january/000483.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/012280.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/015493.html: 1 Time(s)
   /pipermail/engine-patches/2012-April/015602.html: 1 Time(s)
   /pipermail/engine-patches/2012-August/031082.html: 1 Time(s)
   /pipermail/engine-patches/2012-August/031317.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/044910.html: 1 Time(s)
   /pipermail/engine-patches/2012-December/045695.html: 1 Time(s)
   /pipermail/engine-patches/2012-January/003324.html: 1 Time(s)
   /pipermail/engine-patches/2012-July/027145.html: 1 Time(s)
   /pipermail/engine-patches/2012-July/028900.html: 1 Time(s)
   /pipermail/engine-patches/2012-June/021568.html: 1 Time(s)
   /pipermail/engine-patches/2012-June/022786.html: 1 Time(s)
   /pipermail/engine-patches/2012-November/041821.html: 1 Time(s)
   /pipermail/engine-patches/2012-November/042583.html: 1 Time(s)
   /pipermail/engine-patches/2012-October/036843.html: 1 Time(s)
   /pipermail/engine-patches/2012-October/038133.html: 1 Time(s)
   /pipermail/engine-patches/2012-September/036066.html: 1 Time(s)
   /pipermail/engine-patches/2013-December/131013.html: 1 Time(s)
   /pipermail/engine-patches/2013-December/131353.html: 1 Time(s)
   /pipermail/engine-patches/2013-December/135195.html: 1 Time(s)
   /pipermail/engine-patches/2013-February/055161.html: 1 Time(s)
   /pipermail/engine-patches/2013-January/052823.html: 1 Time(s)
   /pipermail/engine-patches/2013-July/086729.html: 1 Time(s)
   /pipermail/engine-patches/2013-June/077690.html: 1 Time(s)
   /pipermail/engine-patches/2013-June/078877.html: 1 Time(s)
   /pipermail/engine-patches/2013-October/114289.html: 1 Time(s)
   /pipermail/engine-patches/2013-September/107191.html: 1 Time(s)
   /pipermail/engine-patches/2014-January/139237.html: 1 Time(s)
   /pipermail/infra/2012-August/wp-admin/admi ... ./wp-config.php: 2 Time(s)
   /pipermail/infra/2012-August/wp-admin/admin-ajax.php: 4 Time(s)
   /pipermail/infra/2013-December/004705.html/trackback/: 1 Time(s)
   /pipermail/infra/2013-December/tiki-register.php: 2 Time(s)
   /pipermail/infra/2013-February//xmlrpc.php: 1 Time(s)
   /pipermail/infra/2013-February/002129.html ... Zenw/xmlrpc.php: 4 Time(s)
   /pipermail/infra/2013-February/002129.html ... enw//xmlrpc.php: 7 Time(s)
  

automation wrongly moving bugs to MODIFIED

[Yedidyah Bar David]

See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
was moved to modified. When I later pushed the patch to 3.6, it
correctly moved it back to POST. Not sure we should even automatically
move to modified if merged to 3.6, because there might be other
changes needed for that bug - it might be best to let the owner to
decide.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1282397

Best,
-- 
Didi
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-326) [us] please fix the job

[sbonazzo (oVirt JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sbonazzo updated  OVIRT-326 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 oVirt - virtualization made easy /  OVIRT-326 
 
 
 
  [us] please fix the job  
 
 
 
 
 
 
 
 
 

Change By:
 
 sbonazzo 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 

Assignee:
 
 Sagi Shnaidman sbonazzo 
 
 
 

Status:
 
 New Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.0-OD-08-005#70107-sha1:5fb2f7e) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

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

Re: automation wrongly moving bugs to MODIFIED

[David Caro]

On 11/17 11:06, Yedidyah Bar David wrote:
> On Tue, Nov 17, 2015 at 10:56 AM, Eyal Edri  wrote:
> >
> >
> > On Tue, Nov 17, 2015 at 10:53 AM, Yedidyah Bar David 
> > wrote:
> >>
> >> On Tue, Nov 17, 2015 at 10:47 AM, David Caro  wrote:
> >> > On 11/17 10:44, Yedidyah Bar David wrote:
> >> >> See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug
> >> >> was moved to modified. When I later pushed the patch to 3.6, it
> >> >> correctly moved it back to POST. Not sure we should even automatically
> >> >> move to modified if merged to 3.6, because there might be other
> >> >> changes needed for that bug - it might be best to let the owner to
> >> >> decide.
> >> >
> >> > The issue here is that there's no way for the hooks to know that you
> >> > will be
> >> > pushing more patches, so when it saw that there were no more open
> >> > patches it
> >> > moved the bug to MODIFIED. Is there any reason why you did not open the
> >> > patches
> >> > first?
> >>
> >> There are two different issues here:
> >>
> >> 1. If merging to master branch, and bug is 3.6, bug should not be
> >> moved to modified
> >> at all.
> >
> >
> > imo, the gerrit hook should give -1 on this.
> > either don't put bug-url at all, or put 4.0 bug-url.
> 
> Not sure about this. I agree it makes some sense. It definitely don't need to
> move to modified :-)
> 
> Since we decided to not always clone bugs, and since we require merging to
> master before merging to stable branch, I think it does make sense to include
> the bug-url even in the master patch. obviously, Related-To is also good 
> enough,
> even though a bit misleading - I usually write Related-To when the patch is 
> not
> directly part of a fix for a bug but only related to it.

We used the related-to in the past, but iirc it was dropped as not everyone
used it and people that did, used it for different things.

I still think that opening all the patches before merging any of them is a good
solution.


> -- 
> Didi

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R

Tel.: +420 532 294 605
Email: dc...@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605


signature.asc
Description: PGP signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: CI does not run for specific patch, cannot trigger job

[Eyal Edri]

there is an open patch that fix this: https://gerrit.ovirt.org/#/c/48518/
once merged, this issue should be resolved.

e.

On Wed, Nov 18, 2015 at 9:29 AM, Sandro Bonazzola 
wrote:

>
>
> On Tue, Nov 17, 2015 at 10:43 PM, Nir Soffer  wrote:
>
>> Hmm, rebase via gerrit did the trick, CI is running now.
>>
>> But why it did not run when the previous 3 versions were posted?
>>
>
> Uploaded patch set 3: Commit message was updated.
>
> No CI runs on commit message change. Only if code changes.
>
>
>
>>
>> On Tue, Nov 17, 2015 at 11:40 PM, Nir Soffer  wrote:
>> > For some reason, the CI would not run for this patch:
>> > https://gerrit.ovirt.org/48578
>> >
>> > I tried to trigger manually, but it tells me:
>> >
>> > No jobs triggered for this event
>> >
>> > Anyone has a clue whats going on, and how can we make the CI
>> > gods happy so they run this patch?
>> >
>> > Nir
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: vdsm_master_create-rpms-el7-x86_64_merged failing without a reason

[Barak Korren]

On 18 November 2015 at 09:27, Sandro Bonazzola  wrote:
>
>
> On Tue, Nov 17, 2015 at 11:19 PM, Nir Soffer  wrote:
>>
>>
>> http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el7-x86_64_merged/1898/console
>>
>> I don't have any idea why this job fails.
>
>
> 00:00:33.606 Start: yum install
> 00:00:47.200 ERROR: Command failed. See logs for output.
>
>
> and looking at logs:
>
>
> DEBUG util.py:377:  Installed size: 423 M
> DEBUG util.py:377:
> http://download.fedoraproject.org/pub/epel/testing/7/x86_64/e/epel-rpm-macros-7-4.noarch.rpm:
> [Errno 14] HTTP Error 404 - Not Found
> DEBUG util.py:377:  Trying other mirror.
> DEBUG util.py:377:  Error downloading packages:
> DEBUG util.py:377:epel-rpm-macros-7-4.noarch: [Errno 256] No more
> mirrors to try.
> DEBUG util.py:488:  Child return code was: 1
>
>
>
>>
>>
>> Can anyone explain this failure or maybe fix it?
>>
>
> Adding infra-owner: issue here is that only the master repository is used
> instead of the mirror list.
> Please ensure that EPEL (and any other mirrored repository) is referenced by
> mirrorlist or metalink and not by baseurl.
>
Its running inside mock, so it should be using the proxy (which can
use mirrors) instead of trying to access EPEL directly.
In fact it is using the proxy with this:

  [centos-epel]
  name=centos-epel
  baseurl=http://proxy.phx.ovirt.org:5000/centos-epel/7/x86_64
  failovermethod=priority

Only it also has this configured which doesn't use the proxy:

  [epel-testing]
  name=epel-testing
  baseurl=http://download.fedoraproject.org/pub/epel/testing/7/$basearch
  gpgcheck=0
  enabled=1
  metadata_expire=30m

Not sure if EPEL testing is even mirrored, do we really need it?

Also, this is an old style job, maybe its about time to switch to a
CI-standard job?

>
>
>>
>> Nir
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>



-- 
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] ovirt-engine_master_upgrade-from-master_el7_merged - Build # 937 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
 
Build: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/937/
Build Number: 937
Build Status:  Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/48686

-
Changes Since Last Success:
-
Changes for Build #931
[Juan Hernandez] restapi: Generate JAX-RS interfaces from model


Changes for Build #932
[Arik Hadas] core: eliminate CDA on export RAM snapshot


Changes for Build #933
[Eli Mesika] db: fix erroneous formatting


Changes for Build #934
[Roy Golan] core: Allow to remove Hosted Engine direct lun disks only


Changes for Build #935
[Roy Golan] core: Auto import Hosted Engine Storage Domain


Changes for Build #936
[Yedidyah Bar David] packaging: setup: nicer error messages about pg conf


Changes for Build #937
[Juan Hernandez] core: Make SUPPORTED_DOMAIN_TYPES package protected




-
Failed Tests:
-
No tests ran. 

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

vdsm_master_create-rpms-el7-x86_64_merged failing without a reason

[Nir Soffer]

http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el7-x86_64_merged/1898/console

I don't have any idea why this job fails.

Can anyone explain this failure or maybe fix it?

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

CI does not run for specific patch, cannot trigger job

[Nir Soffer]

For some reason, the CI would not run for this patch:
https://gerrit.ovirt.org/48578

I tried to trigger manually, but it tells me:

No jobs triggered for this event

Anyone has a clue whats going on, and how can we make the CI
gods happy so they run this patch?

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

Re: CI does not run for specific patch, cannot trigger job

[Nir Soffer]

Hmm, rebase via gerrit did the trick, CI is running now.

But why it did not run when the previous 3 versions were posted?

On Tue, Nov 17, 2015 at 11:40 PM, Nir Soffer  wrote:
> For some reason, the CI would not run for this patch:
> https://gerrit.ovirt.org/48578
>
> I tried to trigger manually, but it tells me:
>
> No jobs triggered for this event
>
> Anyone has a clue whats going on, and how can we make the CI
> gods happy so they run this patch?
>
> Nir
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra