[JIRA] (OVIRT-1938) [OST] Build fail - mom >= 0.5.12 require, 0.5.11-1 available

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=36126#comment-36126
 ] 

Martin Sivak commented on OVIRT-1938:
-

mom-0.5.12 is part of 4.2.2 both US and DS. It is not part of 4.2.0 so I 
suppose OST might want to use some extra repos?

http://resources.ovirt.org/pub/ovirt-4.2-pre/rpm/el7/noarch/mom-0.5.12-1.el7.centos.noarch.rpm

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=654039

> [OST] Build fail - mom >= 0.5.12 require, 0.5.11-1 available
> 
>
> Key: OVIRT-1938
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1938
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>




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

[JIRA] (OVIRT-1849) enable all gerrit hooks for cockpit-ovirt project

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35676#comment-35676
 ] 

Martin Sivak commented on OVIRT-1849:
-

I am not the maintainer, but we have to check all the sla bugs related to 
cockpit in depth as the status does not reflect the patches.

[~rbarry] should give his opinion here too.

> enable all gerrit hooks for cockpit-ovirt project
> -
>
> Key: OVIRT-1849
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1849
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri
>Assignee: infra
>
> It looks like the cockpit-ovirt project doesn't have all hooks enabled, 
> current these are the hooks its using:
> /home/gerrit2/review_site/hooks/custom_hooks/update_tracker
> /home/gerrit2/review_site/hooks/custom_hooks/comment-added.propagate_review_values
> If we want that the hooks will also update bz status and do other 
> verification like backporing, we need to add more hooks.
> [~sbona...@redhat.com] [~msi...@redhat.com] please comment which hooks you'd 
> like to enable or all of them.
> Info on the hooks can be found here 
> :http://ovirt-infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Projects/index.html#enabling-custom-gerrit-hooks
> [~amarchuk] fyi



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

[JIRA] (OVIRT-1529) Gerrit reviewer plugin adds all reviewers even to draft patches

[Martin Sivak (oVirt JIRA)]

Martin Sivak created OVIRT-1529:
---

 Summary: Gerrit reviewer plugin adds all reviewers even to draft 
patches
 Key: OVIRT-1529
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1529
 Project: oVirt - virtualization made easy
  Issue Type: Bug
  Components: Gerrit/git
Reporter: Martin Sivak
Assignee: infra


Draft versions of patches are supposed to be private and visible only to hand 
selected people. The reviewer plugin effectively kills draft status of the 
patch by assigning all relevant people to it.

I would expect auto-reviewer rules are only applied upon publishing a draft 
patch.



--
This message was sent by Atlassian JIRA
(v1000.1112.0#100055)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29614#comment-29614
 ] 

Martin Sivak commented on OVIRT-1299:
-

Exactly what I would like to achieve. With one improvement in step 3. I usually 
release in the same copr repo so in the ideal world I would just provide the 
repo url once and every time you do a compose (or nightly) the tooling would 
check for updates.

> Please provide a koji (and if possible bodhi) instance for ovirt repositories
> -
>
> Key: OVIRT-1299
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>
> Some of the maintainers of oVirt project wants to have control on the builds 
> going into the release repositories without 3rd party intervention on it.
> They would like to have a dist-git + koji like developer experience.
> A bodhi instance would help reviewing the package before it lands on 
> repositories.



--
This message was sent by Atlassian JIRA
(v1000.883.0#100040)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29611#comment-29611
 ] 

Martin Sivak commented on OVIRT-1299:
-

The difference is that you depend on gerrit and on specific branch name to know 
 which build-artifact script to execute. My requests does not require that, I 
will provide the git url and tarball url (or a dir with those) instead.

Something very similar to what I want is the releng tools repository Sandro 
uses. An example: 
https://gerrit.ovirt.org/gitweb?p=releng-tools.git;a=blob;f=releases/ovirt-4.1.1.conf;h=f20c23f5f7d88225e2e729ebab552e5d69544c41;hb=0988bf1bd9d5f91f35733031571f1e8407e28647

The only issue we have with this is that it is not properly documented 
(inheritance rules, ...), does not support source tarballs and CI is probably 
not using it at all.




> Please provide a koji (and if possible bodhi) instance for ovirt repositories
> -
>
> Key: OVIRT-1299
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>
> Some of the maintainers of oVirt project wants to have control on the builds 
> going into the release repositories without 3rd party intervention on it.
> They would like to have a dist-git + koji like developer experience.
> A bodhi instance would help reviewing the package before it lands on 
> repositories.



--
This message was sent by Atlassian JIRA
(v1000.883.0#100040)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29607#comment-29607
 ] 

Martin Sivak edited comment on OVIRT-1299 at 4/5/17 1:00 PM:
-

Do not make this more complex than it has to be. A simple text or ini file (in 
ovirt specific repository, not in the project itself!) where the maintainer can 
say which build (a link to jenkins, copr, koji, github, ...) should go to which 
release is enough. The same for source tarball. Just let us provide a link (git 
hash url, gitweb export or github for example).

All your tooling like publishers or CI or anything else can then consume this 
configuration without forcing us to use a fixed tag or branch structure. The 
maintainer should be in control of the releases or platform, not the automation.

oVirt is a distribution of pieces and some pieces have slightly different 
development model. Even some core oVirt project use GitHub as the primary 
source now.

This has been discussed couple of times already, for example here 
http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here 
http://lists.ovirt.org/pipermail/devel/2017-January/029161.html



was (Author: msi...@redhat.com):
Do not make this more complex than it has to be. A simple text or ini file 
where the maintainer can say which build (a link to jenkins, copr, koji, 
github, ...) should go to which release is enough. The same for source tarball. 
Just let us provide a link (git hash url, gitweb export or github for example).

All your tooling like publishers or CI or anything else can then consume this 
configuration without forcing us to use a fixed tag or branch structure. The 
maintainer should be in control of the releases or platform, not the automation.

oVirt is a distribution of pieces and some pieces have slightly different 
development model. Even some core oVirt project use GitHub as the primary 
source now.

This has been discussed couple of times already, for example here 
http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here 
http://lists.ovirt.org/pipermail/devel/2017-January/029161.html


> Please provide a koji (and if possible bodhi) instance for ovirt repositories
> -
>
> Key: OVIRT-1299
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>
> Some of the maintainers of oVirt project wants to have control on the builds 
> going into the release repositories without 3rd party intervention on it.
> They would like to have a dist-git + koji like developer experience.
> A bodhi instance would help reviewing the package before it lands on 
> repositories.



--
This message was sent by Atlassian JIRA
(v1000.883.0#100040)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29607#comment-29607
 ] 

Martin Sivak commented on OVIRT-1299:
-

Do not make this more complex than it has to be. A simple text or ini file 
where the maintainer can say which build (a link to jenkins, copr, koji, 
github, ...) should go to which release is enough. The same for source tarball. 
Just let us provide a link (git hash url, gitweb export or github for example).

All your tooling like publishers or CI or anything else can then consume this 
configuration without forcing us to use a fixed tag or branch structure. The 
maintainer should be in control of the releases or platform, not the automation.

oVirt is a distribution of pieces and some pieces have slightly different 
development model. Even some core oVirt project use GitHub as the primary 
source now.

This has been discussed couple of times already, for example here 
http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here 
http://lists.ovirt.org/pipermail/devel/2017-January/029161.html


> Please provide a koji (and if possible bodhi) instance for ovirt repositories
> -
>
> Key: OVIRT-1299
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>
> Some of the maintainers of oVirt project wants to have control on the builds 
> going into the release repositories without 3rd party intervention on it.
> They would like to have a dist-git + koji like developer experience.
> A bodhi instance would help reviewing the package before it lands on 
> repositories.



--
This message was sent by Atlassian JIRA
(v1000.883.0#100040)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27883#comment-27883
 ] 

Martin Sivak commented on OVIRT-1193:
-

Eyal, it was my request inspired by Kubernetes. One message per changeset 
(first comment) is hardly obtrusive and it can provide customized links for the 
patchset (real links with proper IDs instead of just a generic help message).

Please realize that we want to have as low barrier of entry as possible, so 
everything has to be immediately obvious from the first message (either a 
direct link or copy/paste command). There are also people who do not really use 
the UI too much (we get all the comments using email too) so UI improvement 
does not solve it for those cases.

But feel free to do a survey.

> add on request 'ci help' command via Gerrit
> ---
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak  wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> -- 
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/



--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1193) Re: Howto message for every gerrit review

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27653#comment-27653
 ] 

Martin Sivak commented on OVIRT-1193:
-

> This is doable, but I think experienced users may find this annoying
> it ifs too long.
>
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.

It does not have to be long, just a summary of all the links once when
the change is posted (so the links can contain the proper change id
and jenkins links).

I am actually more annoyed by the fact that I have to look for the information.

> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).

That would be even better

> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.

That might work too, but I feel a bot sending a message is faster and
easier to do.

Martin

On Thu, Feb 23, 2017 at 2:18 PM, Barak Korren  wrote:
> On 23 February 2017 at 15:10, Martin Sivak  wrote:
>> Hi,
>>
>> do you think it would make sense to send a copy-and-paste ready
>> message with help to every new gerrit change?
>>
>> It could provide all the system test (lago) links, mention the Rerun
>> hooks syntax and so on. Just so we do not have to search for it all
>> the time?
>
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
>
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
>
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
>
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
>
> Adding infra-support to get a Jira ticket opened.
>
> --
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/

> Re: Howto message for every gerrit review
> -
>
> Key: OVIRT-1193
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>
> On 23 February 2017 at 15:10, Martin Sivak  wrote:
> > Hi,
> >
> > do you think it would make sense to send a copy-and-paste ready
> > message with help to every new gerrit change?
> >
> > It could provide all the system test (lago) links, mention the Rerun
> > hooks syntax and so on. Just so we do not have to search for it all
> > the time?
> This is doable, but I think experienced users may find this annoying
> it ifs too long.
> I'm thinking it may be better to have such a message just suggesting
> to type something like '@ci help' to get the full help.
> It may even be possible to make it clickable with some trickery rather
> then just copy-and-paster ready (I will need to check if its possible
> to inject links into Gerrit comments).
> Apart from that, Roy offered to write a Gerrit plugin that will add
> buttons with the various CI commands.
> Adding infra-support to get a Jira ticket opened.
> -- 
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/



--
This message was sent by Atlassian JIRA
(v1000.773.3#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27650#comment-27650
 ] 

Martin Sivak commented on OVIRT-1154:
-

And we should start maintaining the contributor/maintainer list too. It will 
help with assigning reviewers to newly posted patches. Please see my comment 
about that in the relevant JIRA: 
https://ovirt-jira.atlassian.net/browse/OVIRT-1165?focusedCommentId=27649=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27649

> Improve and automate the jenkins-whitelist mechanism
> 
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> Right now our white list is based on a text file with email addresses in it. 
> Its kinda silly when we already have lists and groups of users in Gerrit.
> Some suggestions:
> * make any members of a project's "maintainers" group automatically 
> white-listed
> * make a specific group for other white-listed people 



--
This message was sent by Atlassian JIRA
(v1000.773.3#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27648#comment-27648
 ] 

Martin Sivak commented on OVIRT-1154:
-

I am not opposed to Gerrit comments, but those need to be part of the message 
the user gets so we do not have to search for the right syntax. Barak asked me 
to paste my email about the matter here, so here you go:

> Btw, I just found a project that uses whitelist - kubernetes. But they
> make it very easy for maintainers to accept patches. Check for example
> this pull request: https://github.com/kubernetes/kubernetes/pull/41119
>
> The idea I like is that the CI will immediately tell me what needs to
> be done in the comments. No need to search through documentation for
> the right keyword.
>
> - The bot told the contributor who the relevant maintainers are,
> computed the list of people with enough permissions and notified them
> too. And just a comment by maintainer was needed to enable CI for the
> pull request.
> - The same for failing tests - they provide the command to retrigger
> it directly in the message
>
> It all basically boils down to "Do not make me think" approach.
> Everything that needs to be done is immediately obvious without
> searching. And that I could accept even with the whitelist enabled.

> Improve and automate the jenkins-whitelist mechanism
> 
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> Right now our white list is based on a text file with email addresses in it. 
> Its kinda silly when we already have lists and groups of users in Gerrit.
> Some suggestions:
> * make any members of a project's "maintainers" group automatically 
> white-listed
> * make a specific group for other white-listed people 



--
This message was sent by Atlassian JIRA
(v1000.773.3#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-862) Please give Denis Chalygin the usual developer permissions

[Martin Sivak (oVirt JIRA)]

Martin Sivak created OVIRT-862:
--

 Summary: Please give Denis Chalygin the usual developer permissions
 Key: OVIRT-862
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-862
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Martin Sivak
Assignee: infra


We need the usual permissions for Gerrit and Jenkins. His email is
dchaplyg. He is a new RH employee under Doron.

--
Martin Sivak
SLA / oVirt



--
This message was sent by Atlassian JIRA
(v1000.571.1#100021)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-494) Master broken again - networking tests

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14911#comment-14911
 ] 

Martin Sivak commented on OVIRT-494:


OK, it seems it was either a glitch or my database was somehow corrupted.
IT works now. Sorry for the noise.

On Mon, Apr 18, 2016 at 1:20 PM, eyal edri [Administrator] (oVirt JIRA) <



> Master broken again - networking tests
> --
>
> Key: OVIRT-494
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-494
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Martin Sivak
>Assignee: infra
>
> Hi,
> I just found out that I can't build the master branch
> (d31dfb3b0492af708bb303c82bddf1a51e5d9aa0)  because of
> Tests in error:
>   
> testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
> NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK
> Martin



--
This message was sent by Atlassian JIRA
(v7.2.0-OD-05-030#72002)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-494) Master broken again - networking tests

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14909#comment-14909
 ] 

Martin Sivak commented on OVIRT-494:


OK, so it seems the basic tests are fine and this fails in DAO tests,
let me recreate my DB to see what happens.

On Mon, Apr 18, 2016 at 12:13 PM, Martin Sivak  wrote:
> The git hash is not the offending patch, just the HEAD where I found out.
>
> Martin
>
> On Mon, Apr 18, 2016 at 12:11 PM, Eyal Edri  wrote:
>> How did that pass jenkins tests?
>> Was the offending patch merged with -1?
>>
>> E.
>>
>> On Mon, Apr 18, 2016 at 1:09 PM, Martin Sivak  wrote:
>>>
>>> Hi,
>>>
>>> I just found out that I can't build the master branch
>>> (d31dfb3b0492af708bb303c82bddf1a51e5d9aa0)  because of
>>>
>>> Tests in error:
>>>
>>> testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
>>> NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK
>>>
>>>
>>>
>>> Martin
>>
>>
>>
>>
>> --
>> Eyal Edri
>> Associate Manager
>> RHEV DevOps
>> EMEA ENG Virtualization R
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)


> Master broken again - networking tests
> --
>
> Key: OVIRT-494
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-494
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Martin Sivak
>Assignee: infra
>
> Hi,
> I just found out that I can't build the master branch
> (d31dfb3b0492af708bb303c82bddf1a51e5d9aa0)  because of
> Tests in error:
>   
> testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
> NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK
> Martin



--
This message was sent by Atlassian JIRA
(v7.2.0-OD-05-030#72002)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-494) Master broken again - networking tests

[Martin Sivak (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907#comment-14907
 ] 

Martin Sivak commented on OVIRT-494:


The git hash is not the offending patch, just the HEAD where I found out.

Martin

On Mon, Apr 18, 2016 at 12:11 PM, Eyal Edri  wrote:
> How did that pass jenkins tests?
> Was the offending patch merged with -1?
>
> E.
>
> On Mon, Apr 18, 2016 at 1:09 PM, Martin Sivak  wrote:
>>
>> Hi,
>>
>> I just found out that I can't build the master branch
>> (d31dfb3b0492af708bb303c82bddf1a51e5d9aa0)  because of
>>
>> Tests in error:
>>
>> testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
>> NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK
>>
>>
>>
>> Martin
>
>
>
>
> --
> Eyal Edri
> Associate Manager
> RHEV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)


> Master broken again - networking tests
> --
>
> Key: OVIRT-494
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-494
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Martin Sivak
>Assignee: infra
>
> Hi,
> I just found out that I can't build the master branch
> (d31dfb3b0492af708bb303c82bddf1a51e5d9aa0)  because of
> Tests in error:
>   
> testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
> NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK
> Martin



--
This message was sent by Atlassian JIRA
(v7.2.0-OD-05-030#72002)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-494) Master broken again - networking tests

[Martin Sivak (oVirt JIRA)]

Martin Sivak created OVIRT-494:
--

 Summary: Master broken again - networking tests
 Key: OVIRT-494
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-494
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Martin Sivak
Assignee: infra


Hi,

I just found out that I can't build the master branch
(d31dfb3b0492af708bb303c82bddf1a51e5d9aa0)  because of

Tests in error:
  
testGetViolationMessage(org.ovirt.engine.core.bll.validator.network.LegacyNetworkExclusivenessValidatorTest):
NETWORK_INTERFACES_NOT_EXCLUSIVELY_USED_BY_NETWORK



Martin




--
This message was sent by Atlassian JIRA
(v7.2.0-OD-05-030#72002)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-488) Gerrit is not cloning ovirt-optimizer to Github

[Martin Sivak (oVirt JIRA)]

Martin Sivak created OVIRT-488:
--

 Summary: Gerrit is not cloning ovirt-optimizer to Github
 Key: OVIRT-488
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-488
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Martin Sivak
Assignee: infra


Hi,

I noticed that the clone takes an unusual amount of time. I posted a
patch to ovirt-optimizer gerrit repository [1] about 90 minutes ago
and it still has not appeared in the GitHub clone [2].

Is that normal? David told me the clone is usually almost instantaneous.

[1] https://gerrit.ovirt.org/gitweb?p=ovirt-optimizer.git;a=summary,
[2] https://github.com/oVirt/ovirt-optimizer/commits/master

Thanks

Martin




--
This message was sent by Atlassian JIRA
(v7.2.0-OD-05-030#72002)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra