[JIRA] (OVIRT-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1135:
--

Sure.

> consider changing the welcoming message in Jenkins.ovirt.org to something 
> more meaningful 
> --
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer  wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org 
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



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

[JIRA] (OVIRT-1528) Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1528:
--

I think it was closed by accident when Barak moved it to 'new feature'.

On Thu, Jul 13, 2017 at 3:57 PM, Evgheni Dereveanchin (oVirt JIRA) <




-- 

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)


> Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org
> 
>
> Key: OVIRT-1528
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1528
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Maor Lipchuk
>Assignee: Evgheni Dereveanchin
>Priority: Highest
>
> Hi all,
> I would like to create a new repository in our gerrit.ovirt.org which
> will include a tool to support DR solution for oVirt (see [1])
> Currently it is being developed on my personal github account (see
> [2]), but once it will be migrated to be managed in gerrit.ovirt.org
> it could be great since I can add it a standard CI tests.
> [1] 
> https://docs.google.com/document/d/1tMbTVvcS8wKW4c1V_Ee754bFtqRwl2fkPBNDXHpouVE/edit
> [2] https://github.com/maorlipchuk/ansible_ovirt_DR
> Thanks,
> Maor



--
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-1143) Standard CI V2

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1143:
-
Fix Version/s: (was: OVIRT-INFRA-FEB-2017)

> Standard CI V2 
> ---
>
> Key: OVIRT-1143
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eedri
>Assignee: infra
>  Labels: standard-ci
>
> There are a few things we need to consider for oVirt Standard CI V2, 
> This ticket will be a parent ticket for all of them and will serve as main 
> RFE.



--
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-1520) access to *ovirt.org servers

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1520:
--

please send a similar patch to [1] to add youself.

[~ederevea] do we still need to update the foreman hostgroup as well for new 
users?

[1] https://gerrit.ovirt.org/#/c/74498/

> access to *ovirt.org servers
> 
>
> Key: OVIRT-1520
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1520
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Dafna Ron
>Assignee: infra
>
> I need access to the *ovirt.org servers 
> here is my ssh public key: 
> http://pastebin.test.redhat.com/502005



--
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-1501) Jenkins slave is stuck on virsh cleanup

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1501:
-
Epic Link: OVIRT-403

> Jenkins slave is stuck on virsh cleanup
> ---
>
> Key: OVIRT-1501
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1501
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Daniel Belenky
>Assignee: infra
>
> Jenkins slave was stuck on virsh cleanup.
> The following job: 
> [Link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/461/]
>  timed out after 6 hours.
> The next job that tried to run on the same slave 
> [link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/462/]
>  couldn't destroy the domain.
> I couldn't manually destroy the domain either, and I've ended up rebooting 
> the VM.
> The slave that was rebooted: vm0015.workers-phx.ovirt.org.



--
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-1501) Jenkins slave is stuck on virsh cleanup

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1501:
-
Epic Link: OVIRT-403

> Jenkins slave is stuck on virsh cleanup
> ---
>
> Key: OVIRT-1501
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1501
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Daniel Belenky
>Assignee: infra
>
> Jenkins slave was stuck on virsh cleanup.
> The following job: 
> [Link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/461/]
>  timed out after 6 hours.
> The next job that tried to run on the same slave 
> [link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/462/]
>  couldn't destroy the domain.
> I couldn't manually destroy the domain either, and I've ended up rebooting 
> the VM.
> The slave that was rebooted: vm0015.workers-phx.ovirt.org.



--
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-1501) Jenkins slave is stuck on virsh cleanup

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1501:
--

[~ederevea]see if you can have a look to see if we can improve the cleanup

> Jenkins slave is stuck on virsh cleanup
> ---
>
> Key: OVIRT-1501
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1501
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Daniel Belenky
>Assignee: infra
>
> Jenkins slave was stuck on virsh cleanup.
> The following job: 
> [Link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/461/]
>  timed out after 6 hours.
> The next job that tried to run on the same slave 
> [link|http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/462/]
>  couldn't destroy the domain.
> I couldn't manually destroy the domain either, and I've ended up rebooting 
> the VM.
> The slave that was rebooted: vm0015.workers-phx.ovirt.org.



--
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-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1135:
--

[~JMarks] maybe you have ideas on what kind of info we can add here? some 
general links on the oVirt project?

I think we should add links to the infra team on the ovirt.org wiki + links to 
readthedocs:

something like:
https://www.ovirt.org/develop/infra/infrastructure/
http://ovirt-infra-docs.readthedocs.io/en/latest/

> consider changing the welcoming message in Jenkins.ovirt.org to something 
> more meaningful 
> --
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer  wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org 
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
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-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1135:


Assignee: Evgheni Dereveanchin  (was: infra)

> consider changing the welcoming message in Jenkins.ovirt.org to something 
> more meaningful 
> --
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer  wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org 
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
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-1135) consider changing the welcoming message in Jenkins.ovirt.org to something more meaningful

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1135:
-
Issue Type: Improvement  (was: By-EMAIL)

> consider changing the welcoming message in Jenkins.ovirt.org to something 
> more meaningful 
> --
>
> Key: OVIRT-1135
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1135
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>
> Thanks,
> I've removed the duplicate message, and opening a ticket on this to
> consider more meaningful links or layout on the main page.
> On Sat, Feb 11, 2017 at 6:42 PM, Nir Soffer  wrote:
> > Hi all,
> >
> > If you click the "All" tab, you get double welcome message with
> > similar content.
> > Welcome to oVirt Jenkins continuous integration serverFor more
> > information about the oVirt project visit http://www.ovirt.org
> > Welcome to oVirt Jenkins continuous integration serverFor more info about
> > the oVirt project, visit oVirt.org 
> > See http://jenkins.ovirt.org/view/All/
> >
> > I think we can remove the welcome message entirely, it makes sense only
> > when
> > you visit http://jenkins.ovirt.org/, and only for unlogged users.
> >
> > Logged users do not need the welcome message, it takes valuable space on
> > the screen that
> > can be used for useful data.
> >
> > Nir
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
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-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1198:
-
Issue Type: Bug  (was: By-EMAIL)

> Job times out on: 'Removing the used loop devices' on the initial clean up 
> stage
> 
>
> Key: OVIRT-1198
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: ngol...@redhat.com
>Assignee: infra
>
> 15:44:38 Making sure there are no device mappings...
> 15:44:38 Removing the used loop devices...
> 21:44:37 Build timed out (after 360 minutes). Marking the build as failed.
> 21:44:37 Build was aborted
> (Notice the 6 hours between).
> http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/console
> I think I saw another one earlier this week, also on fc25.



--
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-1379) add support for fedora rawhide in mock_runner

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1379:
-
Issue Type: New Feature  (was: By-EMAIL)

> add support for fedora rawhide in mock_runner
> -
>
> Key: OVIRT-1379
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1379
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Barak Korren
>Assignee: infra
>
> Moving this to Jira.
> On 15 May 2017 at 10:31, Barak Korren  wrote:
> > On 15 May 2017 at 10:13, Sandro Bonazzola  wrote:
> >>
> >>
> >>
> >> On Sat, May 13, 2017 at 11:12 PM, Nir Soffer  wrote:
> >>>
> >>> Hi Sandro, what is needed to build and public ovirt-imageio for Fedora 
> >>> rawhide?
> >>
> >>
> >> We miss support for rawhide in mock runner, within jenkins git repo.
> >> Adding Barak
> >
> > Get we get a mock configuration for it from somewhere?
> > They are building it in Koji so I guess they have rawhide buildroots 
> > already no?
> >
> > Is there any other special behaviour needed besides the proper mock
> > configuration?
> >
> > --
> > Barak Korren
> > RHV DevOps team , RHCE, RHCi
> > Red Hat EMEA
> > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> -- 
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted



--
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-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1427:
-
Issue Type: New Feature  (was: By-EMAIL)

> Dependencies between ovirt-engine and vdsm-jsonrpc-java
> ---
>
> Key: OVIRT-1427
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Piotr Kliczewski
>Assignee: infra
>
> Recently we had and issue that newer version of vdsm-jsonrpc-java was
> available but engine spec was not updated yet. Engine patch contained spec
> and module.xml changes which provided dependencies required by new version
> of jsonrpc. CI used the new version of jsonrpc without engine patch being
> merged which caused several issues.
> This ticket is open to track how we could mitigate similar issues in the
> future.
> Thanks,
> Piotr



--
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-1442) Re: Build timed out in Vdsm check-merged

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1442:
-
Issue Type: Bug  (was: By-EMAIL)

> Re: Build timed out in Vdsm check-merged
> 
>
> Key: OVIRT-1442
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1442
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> I clicked on 'keep forever' so it won't go away if we want to debug.
> On Wed, Jun 14, 2017 at 9:57 AM, Milan Zamazal  wrote:
> > Another "Build timed out":
> >
> > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-
> > x86_64/1967/console
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Eyal edri
> ASSOCIATE MANAGER
> RHV DevOps
> EMEA VIRTUALIZATION R
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
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-1442) Re: Build timed out in Vdsm check-merged

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1442:


Assignee: Evgheni Dereveanchin  (was: infra)

> Re: Build timed out in Vdsm check-merged
> 
>
> Key: OVIRT-1442
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1442
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> I clicked on 'keep forever' so it won't go away if we want to debug.
> On Wed, Jun 14, 2017 at 9:57 AM, Milan Zamazal  wrote:
> > Another "Build timed out":
> >
> > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-
> > x86_64/1967/console
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Eyal edri
> ASSOCIATE MANAGER
> RHV DevOps
> EMEA VIRTUALIZATION R
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
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-1517) upgrade the 'Gerrit Trigger' plugin

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1517:


Assignee: Evgheni Dereveanchin  (was: infra)

> upgrade the 'Gerrit Trigger' plugin 
> 
>
> Key: OVIRT-1517
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1517
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>Priority: High
>
> We're lacking behind on the Gerrit trigger plugin version installed on our 
> Jenkins.
> Latest version is 2.24 [1], while we have 2.23 installed, and there seem to 
> be lots of fixed that might help to fix 
> https://ovirt-jira.atlassian.net/browse/OVIRT-1502
> [1] 
> https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-Version2.24.0(releasedJul32017)



--
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-1517) upgrade the 'Gerrit Trigger' plugin

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1517:
--

Changelog:

Version 2.24.0 (released Jul 3 2017)
JENKINS-43904 Set tag for review comments on REST (pull #317)
Fixed some logging in GerritDynamicUrlProcessor (pull #315)

Version 2.23.3 (released Jun 9 2017)
JENKINS-39010 Interpret the incoming comment message as multi-line text (pull 
#312)
JENKINS-40965 Get out of gerrit event stream loop in illegal state (g-e pull 
#62)
JENKINS-38542 NPE when canceling a task when no job (pull #314)

Version 2.23.2 (released Apr 19 2017)
Update Gerrit documentation links to latest major release (pull #311)
Fix CommentAdded event for Gerrit snapshot version < 2.13 (pull #310)

Version 2.23.1 (released Apr 11 2017)
JENKINS-40059 - CommentAdded trigger firing on every comment (pull #302, pull 
#309)
Display full commit message in tooltip (pull #306)
Change Nr. is a link to review detail (pull #305)
Prevent double HTML escaping of subject in search results (pull #304)
#59 Bumped Gerrit Events to version 2.10.1 to fix an buffer issue for incoming 
JSON.


> upgrade the 'Gerrit Trigger' plugin 
> 
>
> Key: OVIRT-1517
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1517
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>Priority: High
>
> We're lacking behind on the Gerrit trigger plugin version installed on our 
> Jenkins.
> Latest version is 2.24 [1], while we have 2.23 installed, and there seem to 
> be lots of fixed that might help to fix 
> https://ovirt-jira.atlassian.net/browse/OVIRT-1502
> [1] 
> https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-Version2.24.0(releasedJul32017)



--
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-1517) upgrade the 'Gerrit Trigger' plugin

[eedri (oVirt JIRA)]

eedri created OVIRT-1517:


 Summary: upgrade the 'Gerrit Trigger' plugin 
 Key: OVIRT-1517
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1517
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: eedri
Assignee: infra
Priority: High


We're lacking behind on the Gerrit trigger plugin version installed on our 
Jenkins.

Latest version is 2.24 [1], while we have 2.23 installed, and there seem to be 
lots of fixed that might help to fix 
https://ovirt-jira.atlassian.net/browse/OVIRT-1502




[1] 
https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-Version2.24.0(releasedJul32017)



--
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-1517) upgrade the 'Gerrit Trigger' plugin

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1517:
-
Epic Link: OVIRT-403

> upgrade the 'Gerrit Trigger' plugin 
> 
>
> Key: OVIRT-1517
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1517
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>Priority: High
>
> We're lacking behind on the Gerrit trigger plugin version installed on our 
> Jenkins.
> Latest version is 2.24 [1], while we have 2.23 installed, and there seem to 
> be lots of fixed that might help to fix 
> https://ovirt-jira.atlassian.net/browse/OVIRT-1502
> [1] 
> https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-Version2.24.0(releasedJul32017)



--
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-1511) FC 24 build artifacts job for Python SDK constantly fails

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1511:


Assignee: Evgheni Dereveanchin  (was: infra)

Evgheni, can you check if we have issues with mock configuration for fc24 or a 
bad slave?

> FC 24 build artifacts job for Python SDK constantly fails
> -
>
> Key: OVIRT-1511
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1511
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Ondra Machacek
>Assignee: Evgheni Dereveanchin
>
> http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.1_build-artifacts-fc24-x86_64/115/console



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

[JIRA] (OVIRT-1511) FC 24 build artifacts job for Python SDK constantly fails

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1511:
--

Fails on:

*19:33:10*  # /usr/bin/yum --installroot
/var/lib/mock/fedora-24-x86_64-0647740b503ca31b52523ef488912256-11410/root/
--releasever 24 install @buildsys-build gcc git
java-1.8.0-openjdk-devel libxml2 libxml2-devel maven python
python-devel python-enum34 python-flake8 python-lxml python-nose
python-pycurl python-six python-wheel python3 python3-devel
python3-enum34 python3-lxml python3-nose python3-pycurl python3-six
python3-wheel --setopt=tsflags=nocontexts*19:33:10* Failed to set
locale, defaulting to C*19:33:10* Package python-lxml is obsoleted by
python2-lxml, trying to install python2-lxml-3.7.2-1.fc24.x86_64
instead*19:33:10* Package python-nose is obsoleted by python2-nose,
trying to install python2-nose-1.3.7-11.fc24.noarch instead*19:33:10*
Package python-wheel is obsoleted by python2-wheel, trying to install
python2-wheel-0.30.0a0-2.fc24.noarch instead


>From the .packages file:


gcc
git
java-1.8.0-openjdk-devel
libxml2
libxml2-devel
maven
python
python-devel
python-enum34
python-flake8
python-lxml
python-nose
python-pycurl
python-six
python-wheel
python3
python3-devel
python3-enum34
python3-lxml
python3-nose
python3-pycurl
python3-six
python3-wheel



Maybe start by updating that list?




On Sun, Jul 9, 2017 at 10:47 PM, Ondra Machacek (oVirt JIRA) <




-- 

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018 <+972%209-769-2018>
irc: eedri (on #tlv #rhev-dev #rhev-integ)


> FC 24 build artifacts job for Python SDK constantly fails
> -
>
> Key: OVIRT-1511
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1511
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Ondra Machacek
>Assignee: infra
>
> http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.1_build-artifacts-fc24-x86_64/115/console



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

[JIRA] (OVIRT-1515) jenkins: Failed to clean docker images

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1515:


Assignee: Daniel Belenky  (was: infra)

> jenkins: Failed to clean docker images
> --
>
> Key: OVIRT-1515
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1515
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: Daniel Belenky
>
> Hi all,
> In [1]:
> 07:38:50 CLEANUP: Stop all running containers and remove unwanted images
> 07:38:50 Error response from daemon: Driver devicemapper failed to
> remove root filesystem
> 4d16a86320abc1709c5b784377ffd8764c272b3ace3b4d6219c9c6fcab59981f:
> failed to remove device
> 20f33836994d6aa2b8f31a57b51395deb0cb5f6ffa0534dee1734ab3d248f20a:devicemapper:
> Can't set task name /dev/mapper/docker-253:3-134291085-pool
> 07:38:50 Untagged: check_patch_container:exported-artifacts
> 07:38:50 Untagged:
> docker.io/ovirtinfra/check_patch_container@sha256:e7b8a6ea6a9ab75bc985dbef8fcbc0ca22b5b729a94917af06964b39d44c26e1
> 07:38:50 Untagged:
> docker.io/ovirtinfra/check_patch_container:59702271a78b9fd32ee9fc5dde412a9cde94564b
> 07:38:50 Deleted:
> sha256:96b35e5dd70ee3f1d85422b22866343abb712ddca4b583402c24fc4e35df7643
> 07:38:50 Deleted:
> sha256:188b4d6db5bdb66257787ba53d9af5aab668eaf2f6a77eb53c585cdd29657ee4
> 07:38:53 ERROR: Failed to clean docker images
> Thanks,
> [1] 
> http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/2099/console
> -- 
> Didi



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

[JIRA] (OVIRT-886) Yum install does not throw error on missing package

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-886:
-

Can you add links to jobs with the error?

> Yum install does not throw error on missing package
> ---
>
> Key: OVIRT-886
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Gil Shinar
>Assignee: infra
>
> When running el7 mock on fc24 (not necessary the issue) and one of the 
> required packages is missing because a repository in .repos hadn't been 
> added, yum will not fail and the package will not be installed



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

[JIRA] (OVIRT-886) Yum install does not throw error on missing package

[eedri (oVirt JIRA)]

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

eedri reopened OVIRT-886:
-

> Yum install does not throw error on missing package
> ---
>
> Key: OVIRT-886
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Gil Shinar
>Assignee: infra
>
> When running el7 mock on fc24 (not necessary the issue) and one of the 
> required packages is missing because a repository in .repos hadn't been 
> added, yum will not fail and the package will not be installed



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

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-713:

Resolution: Cannot Reproduce
Status: Done  (was: To Do)

> Clean reposync directory after n times of sync failure
> --
>
> Key: OVIRT-713
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Gal Ben Haim
>Assignee: infra
>
> Sometimes reposync fail to sync rpms that already been synced. 
> To resolve this issue, lago removes those rpms, and runs reposync again.
> This resolution doesn't always work, and then we need to clean all the rpms 
> that were synced.
> We want lago to clear the cached rpms after n times of sync failure, and then 
> try to sync again.



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

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1396:
-
Priority: High  (was: Medium)

> Add a new 'test-system-artifacts' Standard-CI stage
> ---
>
> Key: OVIRT-1396
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: oVirt CI
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>
> This is a part of [containers 
> CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKDeG5rXBVXgSaHHQfvZ1la41E/edit?usp=sharing]
>  flow implementation process.
> An order to allow building and testing processes for containers to be 
> triggered after package that are needed for them are built, we will introduce 
> the "{{test-system-artifacts}}" standard-CI stage.
> This stage will be invoked from the 'experimental' or 'change-queue-tester' 
> pipelines jost like the existing OST-based flows.
> In order to provide package and repo information to the std-CI script invoked 
> by this stage we well need to implement OVIRT-1391



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

[JIRA] (OVIRT-1292) make ovirt-release RPMs RHEL compatible

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1292:
--

[~sbona...@redhat.com] is there anything we can do in the release rpm to fix it?

> make ovirt-release RPMs RHEL compatible
> ---
>
> Key: OVIRT-1292
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1292
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>
> Some oVirt users are using the ovirt-release el7 RPMs to test oVirt on RHEL.
> Unfortunately, RHEL uses the '7Server' link which doesn't exist in CentOS 
> resulting in breakage like: 
> 'http://mirror.centos.org/centos/7Server/virt/x86_64/kvm-common/' 
> while 'http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/' exist
> We should either ask CentOS to add that link on the repo or find a way to fix 
> it ourselves in the release rpm.



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

[JIRA] (OVIRT-1276) generate a link to OST automation job

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1276:
-
Issue Type: Improvement  (was: By-EMAIL)

> generate a link to OST automation job
> -
>
> Key: OVIRT-1276
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: rgo...@redhat.com
>Assignee: infra
>
> When activating the 'ci please help' robo verb, please generate a link with
> job parameters for the ost job:
> Say I told the robot to build my 4.1 patch, than asside from the aftifact
> link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as
> a release and so on. In that way a user is a click away from firing a job.
> This could be then continued with 'ci please build and ost' kinda of thing
> \R



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

[JIRA] (OVIRT-1276) generate a link to OST automation job

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1276:
--

I'm guessing you mean 'ci please build' and not 'ci please help', and you want 
us to add a link to the manual OST job, right?

We need to check the YAML templates and see what is the best way to do it.

> generate a link to OST automation job
> -
>
> Key: OVIRT-1276
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: rgo...@redhat.com
>Assignee: infra
>
> When activating the 'ci please help' robo verb, please generate a link with
> job parameters for the ost job:
> Say I told the robot to build my 4.1 patch, than asside from the aftifact
> link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as
> a release and so on. In that way a user is a click away from firing a job.
> This could be then continued with 'ci please build and ost' kinda of thing
> \R



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

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1252:
--

[~bkor...@redhat.com] is this still relevant after the deployment of the new 
logic of deploy rpms?

> post-merge build-artifacts jobs can run out of order
> 
>
> Key: OVIRT-1252
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Barak Korren
>Assignee: infra
>  Labels: standard-ci
>
> Right now build-artifacts jobs that run post merge get run on every patch and 
> are allowed to run in parallel.
> The end result of this is that they do not always finish in the same order in 
> which the patches were merged. This ends up causing the latest build link in 
> Jenkins to not always point to the real latest build. It may also means that 
> packages get pushed to OST not in the right order.
> To fix this we need to make sure the build-artifacts jobs do not run in 
> parallel. Alternatively we could split the build artifacts job into a trigger 
> job and a builder job where the trigger job gets run on every patch in 
> parallel and the builder job only runs where resources are available.



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

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1162:
-
Priority: High  (was: Medium)

> Make sure cron failure email from resources.ovirt.org reach the infra list
> --
>
> Key: OVIRT-1162
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>
> There are quite a few things that run there with cron and we need to know 
> when they fail.



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

[JIRA] (OVIRT-1183) Reinstall some of the Jenkins hypervisors in PHX as ovirt-node

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1183:


Assignee: Evgheni Dereveanchin  (was: infra)

> Reinstall some of the Jenkins hypervisors in PHX as ovirt-node 
> ---
>
> Key: OVIRT-1183
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1183
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> Since we're running oVirt in PHX and already managed to find critical bugs 
> due to it,
> It would be nice to have a few hypervisors running ovirt-node instead of 
> CentOS.
> We can use it for Jenkins DC at first to see how it goes.



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

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1500:
-
Priority: Low  (was: Medium)

> CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
> ---
>
> Key: OVIRT-1500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Gerrit/git, oVirt CI
>Reporter: Allon Mureinik
>Assignee: infra
>Priority: Low
>
> In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, 
> but was not marked as so in gerrit.
> Looking through gerrit's history, here's what I *think* is going on:
> 08:41 - patchset #1 is submitted
> 08:41 - CI (check-patch) starts for both EL7 and fc25
> _At this point I noticed a typo in the commit method. I fixed it and posted 
> patchset #2_
> 08:42 - patchset #2 is submitted
> _CI was never triggered for patchset #2. Is this because the only difference 
> between it and patchset #1 is the commit message?_ 
> 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. 
> This is not inherited to patchset #2 for some reason.
> Expected behavior:
> If CI for patchset #1 passed and the only difference is the commit message 
> (not the parent commit and not the content), I'd expect the CI score to be 
> inherited.



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

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1500:
--

I'll lower priority and keep it for a while in case it pops again, if its not 
common then we will probably close it.
Thanks for reporting anyway! 

> CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
> ---
>
> Key: OVIRT-1500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Gerrit/git, oVirt CI
>Reporter: Allon Mureinik
>Assignee: infra
>
> In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, 
> but was not marked as so in gerrit.
> Looking through gerrit's history, here's what I *think* is going on:
> 08:41 - patchset #1 is submitted
> 08:41 - CI (check-patch) starts for both EL7 and fc25
> _At this point I noticed a typo in the commit method. I fixed it and posted 
> patchset #2_
> 08:42 - patchset #2 is submitted
> _CI was never triggered for patchset #2. Is this because the only difference 
> between it and patchset #1 is the commit message?_ 
> 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. 
> This is not inherited to patchset #2 for some reason.
> Expected behavior:
> If CI for patchset #1 passed and the only difference is the commit message 
> (not the parent commit and not the content), I'd expect the CI score to be 
> inherited.



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

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1408:
-
Resolution: Fixed
Status: Done  (was: To Do)

> Please remove github/ovirt-web-ui from standard CI
> --
>
> Key: OVIRT-1408
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Marek Libra
>Assignee: infra
>
> Please remove github/ovirt-web-ui from standard CI since Travis is used 
> instead.



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

[JIRA] (OVIRT-1076) Create jobs to link Jira to Gerrit

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1076:


Assignee: Dafna Ron  (was: infra)

This can be a cool coding task to try out.
It will require learning a bit the JIRA API and also to get familiar with the 
Gerrit python API we already use on other jobs.

> Create jobs to link Jira to Gerrit
> --
>
> Key: OVIRT-1076
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1076
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: Dafna Ron
>
> Jira probably has an API, so we can make jobs that will find Gerrit patches 
> with 'Jira-Ticket' header and link that to the matching Jira ticket.
> We can also perhaps make the link show the patch status and be updated as the 
> patch status changes.



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

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1061:


Assignee: Evgheni Dereveanchin  (was: infra)

probably best to remove it and make sure all our services are documented in 
infra-docs instead.

> Update http://monitoring.ovirt.org/ovirt.apps/
> --
>
> Key: OVIRT-1061
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring
> and production services currently being used in oVirt infra.
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-1425) Decrease global timeouts from 6h to 2h

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1425:


Assignee: Dafna Ron  (was: infra)

> Decrease global timeouts from 6h to 2h
> --
>
> Key: OVIRT-1425
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1425
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: Barak Korren
>Assignee: Dafna Ron
>  Labels: standard-ci
>
> The timeout is currently 6h, this was needed back when we had very long 
> upgrade jobs.
> We should probably decrease it to 2h, or maybe even less. Most stuff we have 
> these days shouldn't be running more then ~40m.



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

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1170:
-
Blocked By: waiting for user feedback
Status: Blocked  (was: To Do)

> add option to disable networking (or have it off by default)
> 
>
> Key: OVIRT-1170
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: gsher...@redhat.com
>Assignee: infra
>
> Add option to disable networking (or have it off by default). Basically, we 
> want to prevent a job from accessing the internet if we want repeatable 
> builds and/or are doing a downstream build somewhere else. Other/downstream 
> build environments often have networking off. Copr has an option: (See: 
> https://lists.fedorahosted.org/archives/list/copr-de...@lists.fedorahosted.org/thread/LZZPJ534ZDRD7YYFDC3BXDUVVPF5B735/
>  )
> In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to 
> stay offline, but an evil node module called 'phantomjs' connects to the 
> internet in a post-offline-install hook. I'd like the option to disallow that 
> and have the build fail.



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

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1155:
-
Priority: High  (was: Medium)

> Please enable https on resources.ovirt.org
> --
>
> Key: OVIRT-1155
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>Priority: High
>
> If no technical issue is preventing us to enable https, please enable it
> for resources.ovirt.org.
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1155:


Assignee: Evgheni Dereveanchin  (was: infra)

> Please enable https on resources.ovirt.org
> --
>
> Key: OVIRT-1155
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>Priority: High
>
> If no technical issue is preventing us to enable https, please enable it
> for resources.ovirt.org.
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-1099) request for admin permissions on jenkins staging

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1099:
-
Resolution: Done
Status: Done  (was: To Do)

> request for admin permissions on jenkins staging
> 
>
> Key: OVIRT-1099
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1099
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: infra
>
> Hi,
> Can you please give me admin rights on the jenkins staging instance? 
> I'll like to review the new BlueOcean and do some tests there.



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

[JIRA] (OVIRT-1087) drop gerrit log watch emails in favor or real monitoring

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1087:


Assignee: Evgheni Dereveanchin  (was: infra)

> drop gerrit log watch emails in favor or real monitoring
> 
>
> Key: OVIRT-1087
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1087
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> Right now Gerrit sends regular emails from log-watch with various info, such 
> as [1].
> We need to go over these alerts and see if some make sense to convert to 
> alerts on nagios and disable the rest.
> [1].
>   /changes/67155/revisions/57f6a24d70230c5e7 ... README/reviewed: 2 
> Time(s)
>/changes/67587/revisions/807e4950b3a74d127 ... 6f9f5be2/rebase: 1 
> Time(s)
>/changes/68315/revisions/182e8209319a41adc ... kefile/reviewed: 2 
> Time(s)
>/changes/70704/edit?list: 1 Time(s)
>/changes/71065/reviewers/1001042: 1 Time(s)
>/changes/71129/revisions/07edcd447865468bc ... 086f7545/drafts: 2 
> Time(s)
>/changes/71315/reviewers/1000458: 1 Time(s)
>/changes/71337/revisions/3f37d51915b0c7235 ... 829ed631/submit: 1 
> Time(s)
>/changes/?q=change:70704+has:draft=0: 1 Time(s)
>/changes/?q=is:open+owner:self=is:open+r ... +limit:10=881: 2 
> Time(s)
> 404 Not Found
>/changes/55626/detail?O=50004: 1 Time(s)
>/changes/70594/detail?O=50004: 2 Time(s)
>/changes/71272/detail?O=50004: 1 Time(s)
>/gerrit_ui/undefined.cache.js: 1 Time(s)
>/ovirt-system-tests: 2 Time(s)



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

[JIRA] (OVIRT-1064) Re-factor experimental groovy script

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1064:
--

[~bkor...@redhat.com] is this in progress or done perhaps? 

> Re-factor experimental groovy script
> 
>
> Key: OVIRT-1064
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1064
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: Barak Korren
>Assignee: infra
>
> The experimental Groovy scripts has several issues that should be resolved by 
> re-factoring it:
> # Turn the variables defined in the top of the file into constants with upper 
> case manes to ensure they're not used in functions by mistake
> # Remove unused arguments from functions
> # Move the main() function definition to the top of the file so its easier to 
> quickly see an overview of the whole flow
> # Use the "global" constants inside main() instead of passing gazillion 
> parameters to it.
> # Pass parameters directly to function instead of turning them into strings 
> and using interpolation
> # Use 'for-each' loops instead of C-style indexed loops.
> # Use consistent indention throughout the file



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

[JIRA] (OVIRT-1033) The ovirt-engine findbugs job is restricted to running on el7||fc23 slaves

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1033:
-
Resolution: Fixed
Status: Done  (was: To Do)

findbugs moved to check-patch.sh, so it will run on all the nodes defined in 
the project file

> The ovirt-engine findbugs job is restricted to running on el7||fc23 slaves
> --
>
> Key: OVIRT-1033
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1033
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Barak Korren
>Assignee: infra
>
> We should let it run on any slave if possible



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

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1014:
--

[~dan...@redhat.com] does this requirement is still needed?  
[~bkor...@redhat.com] if its still relevant, maybe worth attaching it to the 
main ticket for V2 std-ci.

> avoid repetition in automation/*packages
> 
>
> Key: OVIRT-1014
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: danken
>Assignee: infra
>
> Currently we have many automation/*packages* files, mostly repeating each 
> other.
> Most of the information there is then repeated in vdsm.spec as well.
> It would be nice to have a hierarchical way to define packages. E.g. having 
> most packages in automation/build-artifacts-manual.packages, and adding 
> el7-specific dependencies in avoid repetition in 
> automation/build-artifacts-manual.packages.el7.
> It would be even better to have a single palce (yaml file?) to declare each 
> required package and its version, for each platform/architecture. We can then 
> use it to generate the spec file.



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

[JIRA] (OVIRT-974) Document ovirt.org hosting info and troubleshooting

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-974:
---

Assignee: Marc Dequènes (Duck)  (was: infra)

> Document ovirt.org hosting info and troubleshooting
> ---
>
> Key: OVIRT-974
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-974
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: Marc Dequènes (Duck)
>
> Currently ovirt.org is hosted on OpenShift gear and managed by OSAS.
> We need to document the procedure on how to fix issues on it when they arrise 
> and list contact persons who can help. 
> [~ederevea] maybe documenting it on infra-docs is a good idea.



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

[JIRA] (OVIRT-1007) repo closure job should find also optional pkg

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1007:
-
Priority: Low  (was: Medium)

> repo closure job should find also optional pkg
> --
>
> Key: OVIRT-1007
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eedri
>Assignee: infra
>Priority: Low
>
> http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console



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

[JIRA] (OVIRT-1009) Re: When trigged manually the check-merged job

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1009:
-
Resolution: Cannot Reproduce
Status: Done  (was: To Do)

please reopen if you see it again and provide details.

> Re: When trigged manually the check-merged job
> --
>
> Key: OVIRT-1009
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1009
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: eedri
>Assignee: infra
>
> Adding infra-support to open a ticket on it.
> But it will help if you'll provide example of what you are expecting to see
> so we'll check its possible.
> On Mon, Jan 9, 2017 at 11:32 AM, Yaniv Bronheim  wrote:
> > When trigged manually the check-merged job for specific patch we don't see
> > the link in the patch History - see in https://gerrit.ovirt.org/#/
> > c/69802/3
> >
> > it used to be different .. can we get the link back?
> >
> > Thanks.
> >
> > --
> > *Yaniv Bronhaim.*
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



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

[JIRA] (OVIRT-844) move node builds jobs to run on Lago VM

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-844:

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

Lago isn't relevant here, livecdcreator is used for PXE installation to build 
the image.

> move node builds jobs to run on Lago VM
> ---
>
> Key: OVIRT-844
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-844
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>
> the node jobs keeps failing on cleanup issues which will be solved if we move 
> the job to run on Lago.
> lets do it for master(4.1) as POC and see if it helps.
> http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/
> the job doesn't nessasarily needs a BM slave, so we will need to check what 
> infra changes are needed (puppet classes to install lago?) in order to run it.



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

[JIRA] (OVIRT-886) Yum install does not throw error on missing package

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-886:

Resolution: Cannot Reproduce
Status: Done  (was: To Do)

> Yum install does not throw error on missing package
> ---
>
> Key: OVIRT-886
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Gil Shinar
>Assignee: infra
>
> When running el7 mock on fc24 (not necessary the issue) and one of the 
> required packages is missing because a repository in .repos hadn't been 
> added, yum will not fail and the package will not be installed



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

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-926:

Resolution: Cannot Reproduce
Status: Done  (was: To Do)

> check why 3.6 experimental job failed even if not error in shown on job
> ---
>
> Key: OVIRT-926
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eedri
>Assignee: infra
>  Labels: ost_failures
>
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/
> [~gbenh...@redhat.com][~ngol...@redhat.com][~ederevea][~bkor...@redhat.com] 
> any ideas?



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

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1500:
--

[~mureinik] how often are you hitting this issue? 
If we will enable Jenkins jobs to run also on changes w/o 'code change' it 
might have a significant impact on the CI resources and potentially increase 
the number of jobs running on CI ( w/o a real code change ) and will result in 
longer waiting time per job.



> CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
> ---
>
> Key: OVIRT-1500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Gerrit/git, oVirt CI
>Reporter: Allon Mureinik
>Assignee: infra
>
> In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, 
> but was not marked as so in gerrit.
> Looking through gerrit's history, here's what I *think* is going on:
> 08:41 - patchset #1 is submitted
> 08:41 - CI (check-patch) starts for both EL7 and fc25
> _At this point I noticed a typo in the commit method. I fixed it and posted 
> patchset #2_
> 08:42 - patchset #2 is submitted
> _CI was never triggered for patchset #2. Is this because the only difference 
> between it and patchset #1 is the commit message?_ 
> 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. 
> This is not inherited to patchset #2 for some reason.
> Expected behavior:
> If CI for patchset #1 passed and the only difference is the commit message 
> (not the parent commit and not the content), I'd expect the CI score to be 
> inherited.



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

[JIRA] (OVIRT-682) Improve CI logging

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-682:

Priority: Low  (was: Medium)

> Improve CI logging
> --
>
> Key: OVIRT-682
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: eedri
>Assignee: infra
>Priority: Low
>  Labels: standard-ci
>
> On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer  wrote:
> > Hi all,
> >
> > Lately vdsm builds are failing in the install packages stage with
> > this unhelpful error:
> >
> > 13:59:42 INFO: installing package(s): autoconf automake gdb ...
> > 13:59:53 ERROR: Command failed. See logs for output.
> >
> > I downloaded the logs.tgz file from
> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> > x86_64/1154/artifact/exported-artifacts/logs.tgz
> >
> > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/
> > root.log
> > I found found this error:
> >
> > DEBUG util.py:421:  Error: Package:
> > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch
> > (ovirt-snapshot)
> > DEBUG util.py:421: Requires: ioprocess =
> > 0.17.0-1.201608111609.gitbd272f2.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.15.1-1.fc24.x86_64 (fedora)
> > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.16.1-1.fc24.x86_64 (updates)
> > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64
> > (ovirt-snapshot)
> > DEBUG util.py:421: ioprocess =
> > 0.17.0-1.201607121058.gitbd272f2.fc24
> > DEBUG util.py:421: Available:
> > ioprocess-0.17.0-1.20160829.gitbd272f2.fc24.x86_64
> > (ovirt-snapshot)
> > DEBUG util.py:421: ioprocess =
> > 0.17.0-1.20160829.gitbd272f2.fc24
> >
> > So we have 2 issues here:
> >
> > 1. We need *all* errors in the console
> > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> > x86_64/1154/console
> Not sure its possible or easy to do, these errors usually come from mock
> and are not relevant to the code running on the console.
> I've cc'd infra-support and updated topic to track it and check our options.
> Going foward, we might want to install a log collector like logstash and
> then searching errors there should be much easier.
> >
> >
> > 2. Someone need to fix the ovirt-snapshot repository - it should have
> > the missing ioprocess
> > package.
> > Maybe the project xml is not correct?
> >
> > Nir
> >
> -- 
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



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

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-713:
-

[~gbenh...@redhat.com][~ngol...@redhat.com] was there any progress on this? if 
we still suffer from reposync errors, might worth prioritizing.

> Clean reposync directory after n times of sync failure
> --
>
> Key: OVIRT-713
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Gal Ben Haim
>Assignee: infra
>
> Sometimes reposync fail to sync rpms that already been synced. 
> To resolve this issue, lago removes those rpms, and runs reposync again.
> This resolution doesn't always work, and then we need to clean all the rpms 
> that were synced.
> We want lago to clear the cached rpms after n times of sync failure, and then 
> try to sync again.



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

[JIRA] (OVIRT-638) Tune Gerrit

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-638:

Priority: Low  (was: Medium)

> Tune Gerrit
> ---
>
> Key: OVIRT-638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-638
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>
> We should probably tune Gerrit to take proper advantage of the bigger server 
> we now have.
> This could be useful:
> http://ctf-dev-environment-vagrant.s3.amazonaws.com/Gerrit-Performance-Tuning-Cheat-Sheet.pdf
> Few notable details:
> # Most RAM on the new server is currently taken by the FS cache instead of 
> the Gerrit Java processes.
> # It seems that the Gerrit can do Git garbage collection on its own, and do 
> so more efficiently then doing so with the Git command line.



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

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-686:

Priority: Low  (was: Medium)

> Find a better way to show unstable status in CI
> ---
>
> Key: OVIRT-686
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>Priority: Low
>
> Today we have the main view on jenkins.ovirt.org showing the unstable list of 
> jobs,
> While its effective in showing the current stable jobs, its not optimal in 
> showing trends, history or dashboard view of the jenkins itself.
> We need to find a jenkins plugin or a dashboard to show the current status of 
> Jenkins in a more efficient and informative way.
> There are numerous dashboards and view plugins, just need to find the right 
> one for oVirt.



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

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1173:
-
Priority: Low  (was: Medium)

> Please use git shallow clone as jobs default
> 
>
> Key: OVIRT-1173
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: rgo...@redhat.com
>Assignee: infra
>Priority: Low
>  Labels: standard-ci
>
> Most if not all the git clone of the jobs don't need history at all.
> For ovirt-engine I see it downloading *11Mb* using --depth 1 vs.  *157Mb*
> for regular clone.
> R



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

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-978:

Priority: Low  (was: Medium)

> Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from 
> git service
> 
>
> Key: OVIRT-978
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: danken
>Assignee: infra
>Priority: Low
>
> Occasionally, e.g.
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/console
> I see these failures
> 07:29:50 Manually triggered by user ish...@redhat.com for Gerrit:
> https://gerrit.ovirt.org/68804
> 07:29:50 [EnvInject] - Loading node environment variables.
> 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx
> local_disk nested) in workspace
> /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64
> 07:29:50  > git rev-parse --is-inside-work-tree # timeout=10
> 07:29:50 Fetching changes from the remote Git repository
> 07:29:50  > git config remote.origin.url
> git://gerrit.ovirt.org/vdsm.git # timeout=10
> 07:29:50 Cleaning workspace
> 07:29:50  > git rev-parse --verify HEAD # timeout=10
> 07:29:50 Resetting working tree
> 07:29:50  > git reset --hard # timeout=10
> 07:29:51  > git clean -fdx # timeout=10
> 07:29:51 Pruning obsolete local branches
> 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git
> 07:29:51  > git --version # timeout=10
> 07:29:51  > git -c core.askpass=true fetch --tags --progress
> git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune
> 07:29:51 ERROR: Error fetching remote repo 'origin'
> 07:29:51 hudson.plugins.git.GitException: Failed to fetch from
> git://gerrit.ovirt.org/vdsm.git



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

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-978:
-

havn't seen failures due to it for quite some time, keeping it as low priority 
in case we hit it again.

> Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from 
> git service
> 
>
> Key: OVIRT-978
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: danken
>Assignee: infra
>Priority: Low
>
> Occasionally, e.g.
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/console
> I see these failures
> 07:29:50 Manually triggered by user ish...@redhat.com for Gerrit:
> https://gerrit.ovirt.org/68804
> 07:29:50 [EnvInject] - Loading node environment variables.
> 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx
> local_disk nested) in workspace
> /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64
> 07:29:50  > git rev-parse --is-inside-work-tree # timeout=10
> 07:29:50 Fetching changes from the remote Git repository
> 07:29:50  > git config remote.origin.url
> git://gerrit.ovirt.org/vdsm.git # timeout=10
> 07:29:50 Cleaning workspace
> 07:29:50  > git rev-parse --verify HEAD # timeout=10
> 07:29:50 Resetting working tree
> 07:29:50  > git reset --hard # timeout=10
> 07:29:51  > git clean -fdx # timeout=10
> 07:29:51 Pruning obsolete local branches
> 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git
> 07:29:51  > git --version # timeout=10
> 07:29:51  > git -c core.askpass=true fetch --tags --progress
> git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune
> 07:29:51 ERROR: Error fetching remote repo 'origin'
> 07:29:51 hudson.plugins.git.GitException: Failed to fetch from
> git://gerrit.ovirt.org/vdsm.git



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

[JIRA] (OVIRT-1502) gerrit does not print check_merged output

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1502:
--

I'm not sure it was sending emails, this might be duplicate: 
https://ovirt-jira.atlassian.net/browse/OVIRT-833

> gerrit does not print check_merged output
> -
>
> Key: OVIRT-1502
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: ybronhei
>Assignee: infra
>
> Hello,
> Recently vdsm gerrit job check-merged doesn't send report after its done -
> check all recent jobs - they were done but the gerrit url doesn't show the
> output nor send email about failures.
> Thanks in advance
> Yaniv Bronhaim.
> -- 
> Yaniv Bronhaim.



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

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1500:
--

[~bkor...@redhat.com][~ederevea] do we know who manages the flag scores on 
Gerrit? Is it configured on Gerrit Trigger side or on Gerrit conf itself? 
Is it configurable at all? 

I vaguely remember a hook that was maintaining the scores on trivial rebase. 

> CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
> ---
>
> Key: OVIRT-1500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Gerrit/git, oVirt CI
>Reporter: Allon Mureinik
>Assignee: infra
>
> In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, 
> but was not marked as so in gerrit.
> Looking through gerrit's history, here's what I *think* is going on:
> 08:41 - patchset #1 is submitted
> 08:41 - CI (check-patch) starts for both EL7 and fc25
> _At this point I noticed a typo in the commit method. I fixed it and posted 
> patchset #2_
> 08:42 - patchset #2 is submitted
> _CI was never triggered for patchset #2. Is this because the only difference 
> between it and patchset #1 is the commit message?_ 
> 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. 
> This is not inherited to patchset #2 for some reason.
> Expected behavior:
> If CI for patchset #1 passed and the only difference is the commit message 
> (not the parent commit and not the content), I'd expect the CI score to be 
> inherited.



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

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1468:
--

Let's discuss on the next CI meeting.

> Use CI mirrors for the slaves
> -
>
> Key: OVIRT-1468
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt Infra
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>  Labels: jenkins, mirrors, slaves
>
> Since we've seen that issues like OVIRT-1467 can very quickly break our 
> entire infrastructure, it may be advisable to use out mirrors to isolate the 
> slave VMs from the upstream repos as well, and not just the testing 
> environments.



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

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1468:
-
Priority: High  (was: Medium)

> Use CI mirrors for the slaves
> -
>
> Key: OVIRT-1468
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt Infra
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>  Labels: jenkins, mirrors, slaves
>
> Since we've seen that issues like OVIRT-1467 can very quickly break our 
> entire infrastructure, it may be advisable to use out mirrors to isolate the 
> slave VMs from the upstream repos as well, and not just the testing 
> environments.



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

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1500:
--

bq. CI was never triggered for patchset #2. Is this because the only difference 
between it and patchset #1 is the commit message? 

The current configuration skips any change that doesn't include 'code change':

"Exclude changes without code change from triggering build

If set, this will ignore any patchset which Gerrit considers without any code 
changes from triggering this build. These patches did not contain any 
differences in code from the previous patchset and did not change the parent 
commit.
"
So i'm not sure which inheritance are you reffering to, CI shouldn't run on 
patchset #2 since it was just commit msg update and returned +1 on the 1st 
patchset, no?



> CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
> ---
>
> Key: OVIRT-1500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Gerrit/git, oVirt CI
>Reporter: Allon Mureinik
>Assignee: infra
>
> In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, 
> but was not marked as so in gerrit.
> Looking through gerrit's history, here's what I *think* is going on:
> 08:41 - patchset #1 is submitted
> 08:41 - CI (check-patch) starts for both EL7 and fc25
> _At this point I noticed a typo in the commit method. I fixed it and posted 
> patchset #2_
> 08:42 - patchset #2 is submitted
> _CI was never triggered for patchset #2. Is this because the only difference 
> between it and patchset #1 is the commit message?_ 
> 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. 
> This is not inherited to patchset #2 for some reason.
> Expected behavior:
> If CI for patchset #1 passed and the only difference is the commit message 
> (not the parent commit and not the content), I'd expect the CI score to be 
> inherited.



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

[JIRA] (OVIRT-1097) review ovirt snapshot static repos and remove not needed RPMs

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1097:


Assignee: eedri  (was: infra)

> review ovirt snapshot static repos and remove not needed RPMs
> -
>
> Key: OVIRT-1097
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1097
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: eedri
>Priority: High
>
> We should aim to drop the static repos, any RPMs oVirt needs should come from 
> one of the following sources:
> 1. Built in standard CI via build artifacts job
> 2. If its external, then we need to use the origin repo and not copy it to be 
> on oVirt.
> We can start from master and move to stable versions when its verified.
> existing RPMS on master static: (showing el7 as most OS should be similar )
> .
> ├── noarch
> │   ├── ebay-cors-filter-1.0.1-3.el7.noarch.rpm
> │   ├── ebay-cors-filter-javadoc-1.0.1-3.el7.noarch.rpm
> │   ├── nsis-simple-service-plugin-1.30-1.noarch.rpm
> │   ├── openvswitch-selinux-policy-2.6.90-1.el7.centos.noarch.rpm
> │   ├── openvswitch-test-2.6.90-1.el7.centos.noarch.rpm
> │   ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch.rpm
> │   ├── python-openvswitch-2.6.90-1.el7.centos.noarch.rpm
> │   ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.noarch.rpm
> │   └── 
> rubygem-fluent-plugin-rewrite-tag-filter-doc-1.5.5-1.el7.centos.noarch.rpm
> ├── ppc64
> │   ├── python-cpopen-1.3-4.el7.ppc64.rpm
> │   └── python-cpopen-debuginfo-1.3-4.el7.ppc64.rpm
> ├── ppc64le
> ├── repodata
> │   ├── 
> 008d859bb942a115e9b0077bd65c84f49e5a01eca2209ad393c27a036237783f-filelists.xml.gz
> │   ├── 
> 14a142882a77ec4120c34a7d88dd69bdcf9463915c34d0f139fe6a9f01a78ca5-filelists.sqlite.bz2
> │   ├── 
> 3299fdf213c4ee0e8bea41142691d1ab861496291a2302dfa32a7247eb43660c-primary.xml.gz
> │   ├── 
> 648a0a77bce1ba70babe4c8f5ac90b8f4b89103f8fa429903d572022066367be-primary.sqlite.bz2
> │   ├── 
> 715d2c608d40b1982b5a02c1c98bc6fca827e46d260849afc8eec6ad928caa6f-other.xml.gz
> │   ├── 
> f54bf13a0e486128a9bc41a975e4ecf597b553c47a7cdb70c169ce8c042c3b94-other.sqlite.bz2
> │   └── repomd.xml
> ├── SRPMS
> │   ├── ebay-cors-filter-1.0.1-3.el7.src.rpm
> │   ├── nsis-simple-service-plugin-1.30-1.src.rpm
> │   ├── openvswitch-2.6.90-1.el7.centos.src.rpm
> │   ├── ovirt-engine-wildfly-10.1.0-1.el7.src.rpm
> │   ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.src.rpm
> │   ├── ovirt-web-ui-0.1.0-4.el7.centos.src.rpm
> │   ├── ovirt-web-ui-0.1.1-2.el7.centos.src.rpm
> │   ├── repodata
> │   │   ├── 
> 1f13684ed34daa19755884e49132dcee7b60eafd38b52a51f945a92e63459e65-filelists.xml.gz
> │   │   ├── 
> 3f20e34cc666f1df8667288b5cdf3eb449fed6ab8b032e1a0d9be0fc78d53b56-primary.sqlite.bz2
> │   │   ├── 
> 7e260234efc35f032a0d22f976d17758b2866d742c04911a4758c3552db1-primary.xml.gz
> │   │   ├── 
> 87cdc086330908e1dc39ca53c50eb9b6ba3627b2b562e0d278a0e899fd925167-other.xml.gz
> │   │   ├── 
> e2cb0de1abd9d51f783862d7d498ead766a96261dd942230f0182afee7195bdb-other.sqlite.bz2
> │   │   ├── 
> ed15cb166756bbf49aecd3f8e65ca0da96ca860d64e4fc80a141280a9114e5ee-filelists.sqlite.bz2
> │   │   └── repomd.xml
> │   ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.src.rpm
> │   └── vhostmd-0.5-11.el7.src.rpm
> └── x86_64
> ├── openvswitch-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-debuginfo-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-devel-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-central-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-common-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-docker-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-host-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-vtep-2.6.90-1.el7.centos.x86_64.rpm
> ├── ovirt-engine-wildfly-10.1.0-1.el7.x86_64.rpm
> ├── ovirt-web-ui-0.1.0-4.el7.centos.x86_64.rpm
> ├── ovirt-web-ui-0.1.1-2.el7.centos.x86_64.rpm
> ├── vhostmd-0.5-11.el7.x86_64.rpm
> ├── vhostmd-debuginfo-0.5-11.el7.x86_64.rpm
> ├── vm-dump-metrics-0.5-11.el7.x86_64.rpm
> └── vm-dump-metrics-devel-0.5-11.el7.x86_64.rpm



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

[JIRA] (OVIRT-1097) review ovirt snapshot static repos and remove not needed RPMs

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1097:
-
Priority: High  (was: Medium)

> review ovirt snapshot static repos and remove not needed RPMs
> -
>
> Key: OVIRT-1097
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1097
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: infra
>Priority: High
>
> We should aim to drop the static repos, any RPMs oVirt needs should come from 
> one of the following sources:
> 1. Built in standard CI via build artifacts job
> 2. If its external, then we need to use the origin repo and not copy it to be 
> on oVirt.
> We can start from master and move to stable versions when its verified.
> existing RPMS on master static: (showing el7 as most OS should be similar )
> .
> ├── noarch
> │   ├── ebay-cors-filter-1.0.1-3.el7.noarch.rpm
> │   ├── ebay-cors-filter-javadoc-1.0.1-3.el7.noarch.rpm
> │   ├── nsis-simple-service-plugin-1.30-1.noarch.rpm
> │   ├── openvswitch-selinux-policy-2.6.90-1.el7.centos.noarch.rpm
> │   ├── openvswitch-test-2.6.90-1.el7.centos.noarch.rpm
> │   ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch.rpm
> │   ├── python-openvswitch-2.6.90-1.el7.centos.noarch.rpm
> │   ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.noarch.rpm
> │   └── 
> rubygem-fluent-plugin-rewrite-tag-filter-doc-1.5.5-1.el7.centos.noarch.rpm
> ├── ppc64
> │   ├── python-cpopen-1.3-4.el7.ppc64.rpm
> │   └── python-cpopen-debuginfo-1.3-4.el7.ppc64.rpm
> ├── ppc64le
> ├── repodata
> │   ├── 
> 008d859bb942a115e9b0077bd65c84f49e5a01eca2209ad393c27a036237783f-filelists.xml.gz
> │   ├── 
> 14a142882a77ec4120c34a7d88dd69bdcf9463915c34d0f139fe6a9f01a78ca5-filelists.sqlite.bz2
> │   ├── 
> 3299fdf213c4ee0e8bea41142691d1ab861496291a2302dfa32a7247eb43660c-primary.xml.gz
> │   ├── 
> 648a0a77bce1ba70babe4c8f5ac90b8f4b89103f8fa429903d572022066367be-primary.sqlite.bz2
> │   ├── 
> 715d2c608d40b1982b5a02c1c98bc6fca827e46d260849afc8eec6ad928caa6f-other.xml.gz
> │   ├── 
> f54bf13a0e486128a9bc41a975e4ecf597b553c47a7cdb70c169ce8c042c3b94-other.sqlite.bz2
> │   └── repomd.xml
> ├── SRPMS
> │   ├── ebay-cors-filter-1.0.1-3.el7.src.rpm
> │   ├── nsis-simple-service-plugin-1.30-1.src.rpm
> │   ├── openvswitch-2.6.90-1.el7.centos.src.rpm
> │   ├── ovirt-engine-wildfly-10.1.0-1.el7.src.rpm
> │   ├── ovirt-engine-wildfly-overlay-10.0.0-1.el7.src.rpm
> │   ├── ovirt-web-ui-0.1.0-4.el7.centos.src.rpm
> │   ├── ovirt-web-ui-0.1.1-2.el7.centos.src.rpm
> │   ├── repodata
> │   │   ├── 
> 1f13684ed34daa19755884e49132dcee7b60eafd38b52a51f945a92e63459e65-filelists.xml.gz
> │   │   ├── 
> 3f20e34cc666f1df8667288b5cdf3eb449fed6ab8b032e1a0d9be0fc78d53b56-primary.sqlite.bz2
> │   │   ├── 
> 7e260234efc35f032a0d22f976d17758b2866d742c04911a4758c3552db1-primary.xml.gz
> │   │   ├── 
> 87cdc086330908e1dc39ca53c50eb9b6ba3627b2b562e0d278a0e899fd925167-other.xml.gz
> │   │   ├── 
> e2cb0de1abd9d51f783862d7d498ead766a96261dd942230f0182afee7195bdb-other.sqlite.bz2
> │   │   ├── 
> ed15cb166756bbf49aecd3f8e65ca0da96ca860d64e4fc80a141280a9114e5ee-filelists.sqlite.bz2
> │   │   └── repomd.xml
> │   ├── rubygem-fluent-plugin-rewrite-tag-filter-1.5.5-1.el7.centos.src.rpm
> │   └── vhostmd-0.5-11.el7.src.rpm
> └── x86_64
> ├── openvswitch-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-debuginfo-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-devel-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-central-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-common-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-docker-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-host-2.6.90-1.el7.centos.x86_64.rpm
> ├── openvswitch-ovn-vtep-2.6.90-1.el7.centos.x86_64.rpm
> ├── ovirt-engine-wildfly-10.1.0-1.el7.x86_64.rpm
> ├── ovirt-web-ui-0.1.0-4.el7.centos.x86_64.rpm
> ├── ovirt-web-ui-0.1.1-2.el7.centos.x86_64.rpm
> ├── vhostmd-0.5-11.el7.x86_64.rpm
> ├── vhostmd-debuginfo-0.5-11.el7.x86_64.rpm
> ├── vm-dump-metrics-0.5-11.el7.x86_64.rpm
> └── vm-dump-metrics-devel-0.5-11.el7.x86_64.rpm



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

[JIRA] (OVIRT-1497) repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1497:


Assignee: Daniel Belenky  (was: infra)

Please check if its a cache issue, because it looks like its not failing the 
experimental flows.

> repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo
> --
>
> Key: OVIRT-1497
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Daniel Belenky
>Priority: Highest
>
> Hi,
> just got into
> package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo
>   unresolved deps:
>  libuv-devel = 1:1.8.0-1.el7
> within
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1154/testReport/(root)/000_check_repo_closure/check_repo_closure/
> I'm now trying to figure out where this package comes from.
> It's not in ovirt-master-snapshot-static.
> I've found it on our internal mirror:
> $ ssh mirrors.phx.ovirt.org
> $ cd /var/www/html/repos/yum
> $ find . -name "libuv*el7*"
> ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm
> So looks like it comes from here. But the CentOS test repo has no such
> package.
> https://buildlogs.centos.org/centos/7/opstools/x86_64/common/
> has
> libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K
> libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K
> libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K
> which is also a mistake since that package is not tagged to be there:
> http://cbs.centos.org/koji/buildinfo?buildID=8182
> and isn't in
> https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/
> (already reported to centos people)
> Are we not syncing mirrors but just appending stuff?
> -- 
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 



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

[JIRA] (OVIRT-1497) repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1497:
-
Priority: Highest  (was: Medium)

> repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo
> --
>
> Key: OVIRT-1497
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>Priority: Highest
>
> Hi,
> just got into
> package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo
>   unresolved deps:
>  libuv-devel = 1:1.8.0-1.el7
> within
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1154/testReport/(root)/000_check_repo_closure/check_repo_closure/
> I'm now trying to figure out where this package comes from.
> It's not in ovirt-master-snapshot-static.
> I've found it on our internal mirror:
> $ ssh mirrors.phx.ovirt.org
> $ cd /var/www/html/repos/yum
> $ find . -name "libuv*el7*"
> ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm
> So looks like it comes from here. But the CentOS test repo has no such
> package.
> https://buildlogs.centos.org/centos/7/opstools/x86_64/common/
> has
> libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K
> libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K
> libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K
> which is also a mistake since that package is not tagged to be there:
> http://cbs.centos.org/koji/buildinfo?buildID=8182
> and isn't in
> https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/
> (already reported to centos people)
> Are we not syncing mirrors but just appending stuff?
> -- 
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 



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

[JIRA] (OVIRT-1497) repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1497:
-
Summary: repoclosure fails on missing *libuv* pkg from 
centos-opstools-testing repo  (was: mirroring of upstream repos may be broken)

> repoclosure fails on missing *libuv* pkg from centos-opstools-testing repo
> --
>
> Key: OVIRT-1497
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Hi,
> just got into
> package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo
>   unresolved deps:
>  libuv-devel = 1:1.8.0-1.el7
> within
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1154/testReport/(root)/000_check_repo_closure/check_repo_closure/
> I'm now trying to figure out where this package comes from.
> It's not in ovirt-master-snapshot-static.
> I've found it on our internal mirror:
> $ ssh mirrors.phx.ovirt.org
> $ cd /var/www/html/repos/yum
> $ find . -name "libuv*el7*"
> ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm
> So looks like it comes from here. But the CentOS test repo has no such
> package.
> https://buildlogs.centos.org/centos/7/opstools/x86_64/common/
> has
> libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K
> libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K
> libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K
> which is also a mistake since that package is not tagged to be there:
> http://cbs.centos.org/koji/buildinfo?buildID=8182
> and isn't in
> https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/
> (already reported to centos people)
> Are we not syncing mirrors but just appending stuff?
> -- 
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 



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

[JIRA] (OVIRT-1497) mirroring of upstream repos may be broken

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1497:
--

I'm pretty sure check-patch isn't using mirrors yet, so the problem isn't 
there. [1]
It seems that we keep hitting issues originating from the centos ops tools 
testing repo, I suggest we'll remove it until we can find away to consume the 
release repo, or some other way to verify it before it hits OST.

The amount of errors and issues we hit weekly due to repo closure is not 
realistic and doesn't justify the test itself IMO or the stability of OST and 
ease to test patches.

[1] https://ovirt-jira.atlassian.net/browse/OST-33


> mirroring of upstream repos may be broken
> -
>
> Key: OVIRT-1497
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1497
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Hi,
> just got into
> package: 1:libuv-static-1.8.0-1.el7.x86_64 from internal_repo
>   unresolved deps:
>  libuv-devel = 1:1.8.0-1.el7
> within
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1154/testReport/(root)/000_check_repo_closure/check_repo_closure/
> I'm now trying to figure out where this package comes from.
> It's not in ovirt-master-snapshot-static.
> I've found it on our internal mirror:
> $ ssh mirrors.phx.ovirt.org
> $ cd /var/www/html/repos/yum
> $ find . -name "libuv*el7*"
> ./centos-opstools-testing-el7/base/common/libuv-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-1.8.0-1.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-devel-0.10.34-2.el7.x86_64.rpm
> ./centos-opstools-testing-el7/base/common/libuv-static-0.10.34-2.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-devel-1.10.2-1.el7.x86_64.rpm
> ./epel-el7/base/l/libuv-static-1.10.2-1.el7.x86_64.rpm
> So looks like it comes from here. But the CentOS test repo has no such
> package.
> https://buildlogs.centos.org/centos/7/opstools/x86_64/common/
> has
> libuv-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 60K
> libuv-devel-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 40K
> libuv-static-0.10.34-2.el7.x86_64.rpm 2015-12-23 01:51 59K
> which is also a mistake since that package is not tagged to be there:
> http://cbs.centos.org/koji/buildinfo?buildID=8182
> and isn't in
> https://cbs.centos.org/repos/opstools7-common-testing/x86_64/os/
> (already reported to centos people)
> Are we not syncing mirrors but just appending stuff?
> -- 
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 



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

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1495:
-
Epic Link: OVIRT-403

> Check out Gerrit metrics feature to see if we can push stats to graphana
> 
>
> Key: OVIRT-1495
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eedri
>Assignee: infra
>
> Gerrit 2.13 added a new feature that allows sending metrics to an external 
> source like Graphite.
> It would be interesting to see if we can push status about our Gerrit 
> instance to our Graphana instance.
> More info at:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



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

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eedri (oVirt JIRA)]

eedri created OVIRT-1495:


 Summary: Check out Gerrit metrics feature to see if we can push 
stats to graphana
 Key: OVIRT-1495
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: eedri
Assignee: infra


Gerrit 2.13 added a new feature that allows sending metrics to an external 
source like Graphite.
It would be interesting to see if we can push status about our Gerrit instance 
to our Graphana instance.

More info at:
https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



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

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup

[eedri (oVirt JIRA)]

eedri created OVIRT-1493:


 Summary: Update current DR documentation with info on storage setup
 Key: OVIRT-1493
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: eedri
Assignee: infra
Priority: Highest


Following the last outage on oVirt storage servers, it seems that we are 
missing more info on how to debug and fix issues on the storage service.

current documentation on 
http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/index.html
 only shows configuration but doesn't include troubleshooting like what can we 
check or do in case any of the services that make the storage work fails.



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

[JIRA] (OVIRT-1493) Update current DR documentation with info on storage setup

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1493:
-
Epic Link: OVIRT-403

> Update current DR documentation with info on storage setup
> --
>
> Key: OVIRT-1493
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1493
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: infra
>Priority: Highest
>
> Following the last outage on oVirt storage servers, it seems that we are 
> missing more info on how to debug and fix issues on the storage service.
> current documentation on 
> http://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/Storage_Hosts/index.html
>  only shows configuration but doesn't include troubleshooting like what can 
> we check or do in case any of the services that make the storage work fails.



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

[JIRA] (OVIRT-1491) Change oVirt DC production storage

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1491:
-
Resolution: Duplicate
Status: Done  (was: To Do)

https://ovirt-jira.atlassian.net/browse/OVIRT-1490

> Change oVirt DC production storage 
> ---
>
> Key: OVIRT-1491
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1491
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: infra
>Priority: Highest
>
> It seems that during the history of the DC, there wasn't one time we really 
> used the DRDB features and it makes our storage configuration more complex 
> and hard to maintain/debug than it brings value.
> Lets think on a new SIMPLE storage setup that will increase the availability 
> of oVirt services and will prevent incidents like before where we have a 
> single point of failure if the storage is down. without multiple services 
> that adds more failure points and complexity to the setup.
> One suggestion was to install 2 new storage servers running ISCSI and connect 
> them independently to oVirt and spread the load over both of them, so if one 
> is down the other will keep running.
> We can consider having a few redundant VMs on both servers if possible like 
> the resources server and maybe others as well.
> Please add more suggestions on this ticket, it should be our number one 
> priority right now.



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

[JIRA] (OVIRT-1491) Change oVirt DC production storage

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1491:
-
Epic Link: OVIRT-403

> Change oVirt DC production storage 
> ---
>
> Key: OVIRT-1491
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1491
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: infra
>Priority: Highest
>
> It seems that during the history of the DC, there wasn't one time we really 
> used the DRDB features and it makes our storage configuration more complex 
> and hard to maintain/debug than it brings value.
> Lets think on a new SIMPLE storage setup that will increase the availability 
> of oVirt services and will prevent incidents like before where we have a 
> single point of failure if the storage is down. without multiple services 
> that adds more failure points and complexity to the setup.
> One suggestion was to install 2 new storage servers running ISCSI and connect 
> them independently to oVirt and spread the load over both of them, so if one 
> is down the other will keep running.
> We can consider having a few redundant VMs on both servers if possible like 
> the resources server and maybe others as well.
> Please add more suggestions on this ticket, it should be our number one 
> priority right now.



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

[JIRA] (OVIRT-1491) Change oVirt DC production storage

[eedri (oVirt JIRA)]

eedri created OVIRT-1491:


 Summary: Change oVirt DC production storage 
 Key: OVIRT-1491
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1491
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: eedri
Assignee: infra
Priority: Highest


It seems that during the history of the DC, there wasn't one time we really 
used the DRDB features and it makes our storage configuration more complex and 
hard to maintain/debug than it brings value.

Lets think on a new SIMPLE storage setup that will increase the availability of 
oVirt services and will prevent incidents like before where we have a single 
point of failure if the storage is down. without multiple services that adds 
more failure points and complexity to the setup.

One suggestion was to install 2 new storage servers running ISCSI and connect 
them independently to oVirt and spread the load over both of them, so if one is 
down the other will keep running.

We can consider having a few redundant VMs on both servers if possible like the 
resources server and maybe others as well.

Please add more suggestions on this ticket, it should be our number one 
priority right now.






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

[JIRA] (OVIRT-1492) Status.ovirt.org doesn't report real status

[eedri (oVirt JIRA)]

eedri created OVIRT-1492:


 Summary: Status.ovirt.org doesn't report real status
 Key: OVIRT-1492
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1492
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: eedri
Assignee: infra


Some services are not reachable but it is not shown on status page.



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

[JIRA] (OVIRT-723) check/add support for python3 + dnf on standard CI

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-723:
-

[~d...@redhat.com] is this still relevant?

> check/add support for python3 + dnf on standard CI
> --
>
> Key: OVIRT-723
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Hi,
> Patch [1] fails jenkins [2] like this:
> 11:35:21 [ INFO  ] DNF Repository updates-testing is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-testing-debuginfo is listed
> more than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-debuginfo is listed more
> than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora-debuginfo is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'fedora', 
> disabling.
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'updates',
> disabling.
> 11:35:21 [ INFO  ] Stage: Environment packages setup
> 11:35:21 [ INFO  ] DNF Repository updates-testing is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-testing-debuginfo is listed
> more than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository updates is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository updates-debuginfo is listed more
> than once in the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora is listed more than once in
> the configuration
> 11:35:21 [ INFO  ] DNF Repository fedora-debuginfo is listed more than
> once in the configuration
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Downloading 1 files, 0.00KB
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'fedora', 
> disabling.
> 11:35:21 [ INFO  ] DNF Failed to synchronize cache for repo 'updates',
> disabling.
> 11:35:21 [ ERROR ] DNF Cannot queue package 'iproute': no package matched
> 11:35:21 [ ERROR ] Failed to execute stage 'Environment packages
> setup': no package matched
> I suspected, based on the log, that something is broken about dnf
> configuration, so pushed [3] and ran the job again [4] with [3]
> cherry-picked, and it succeeded. I thought that's enough for a
> verification, so asked to merge it, and it was merged. Later on, lago
> tests started breaking [5] with:
> 09:37:44 Error: nothing provides repoman >= 2.0.12 needed by
> python-lago-ovirt-0.24.0-1.fc23.noarch
> So [3] was reverted [6], Currently pending, but I expect it to be merged soon.
> So we need a better solution.
> While investigating this, Nadav partially understood the issue - we have, at
> certain points in mock_runner, both /etc/yum.conf and /etc/yum/yum.conf.
> Not sure why and whether we need both.
> We tried also various variations on this patch in [7][8][9][10], none worked.
> Probably better to fully support dnf instead of this hack, not sure
> what this requires.
> Thanks,
> [1] https://gerrit.ovirt.org/59831
> [2] 
> http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/44/console
> [3] https://gerrit.ovirt.org/63249
> [4] http://jenkins.ovirt.org/job/otopi_master_check-patch-fc24-x86_64/46/
> [5] 
> http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/console
> [6] https://gerrit.ovirt.org/63405
> [7] https://gerrit.ovirt.org/63386
> [8] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/203
> [9] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/204/
> [10] http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/205/
> -- 
> Didi



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

[JIRA] (OVIRT-768) Decomission of MD5 Password Hashes for Infra Users

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-768:

Issue Type: Improvement  (was: By-EMAIL)

> Decomission of MD5 Password Hashes for Infra Users
> --
>
> Key: OVIRT-768
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-768
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Anton Marchukov
>Assignee: infra
>
> During the work of moving password parameters from foreman to internal
> hiera I noted that there are some users that still have their passwords
> hashed by MD5 algorithm.
> MD5 has known crypto research that make it no longer suitable for storing
> passwords securely:
> https://en.wikipedia.org/wiki/MD5#Security (and corresponding links).
> While the hashes are stored in internal repo it is still shared and prone
> to information leaks. We should ask all users to rehash their passwords
> with SHA-512 and when it is done we can remove MD5 exception
> in site/ovirt_infra/manifests/user.pp so MD5 hashed passwords are no
> longer accepted.
> The current list of users left is available in infra-hiera repo.
> -- 
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat



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

[JIRA] (OVIRT-769) infra-hiera Autodeploy via Gerrit Hooks

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-769:

Issue Type: Improvement  (was: By-EMAIL)

> infra-hiera Autodeploy via Gerrit Hooks
> ---
>
> Key: OVIRT-769
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-769
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Anton Marchukov
>Assignee: infra
>
> infra-hiera repo is already used and configured in r10k to deploy from git.
> However in gerrit there is not hooks that run CI on it and that trigger
> publish when it is merged to git.
> Looks like it is easy to fix and we can reuse most of the hooks we have for
> infra-puppet. Basically the deploy should be done using the same jenkins
> job and it already does that just not triggered.
> As for CI check than we need to check if puppetlint we use is sufficient.
> But it might be a good start.
> -- 
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat



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

[JIRA] (OVIRT-978) Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from git service

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-978:

Issue Type: Improvement  (was: By-EMAIL)

> Move ovirt-engine & vdsm projects from git:// to http:// to reduce load from 
> git service
> 
>
> Key: OVIRT-978
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: danken
>Assignee: infra
>
> Occasionally, e.g.
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/console
> I see these failures
> 07:29:50 Manually triggered by user ish...@redhat.com for Gerrit:
> https://gerrit.ovirt.org/68804
> 07:29:50 [EnvInject] - Loading node environment variables.
> 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx
> local_disk nested) in workspace
> /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64
> 07:29:50  > git rev-parse --is-inside-work-tree # timeout=10
> 07:29:50 Fetching changes from the remote Git repository
> 07:29:50  > git config remote.origin.url
> git://gerrit.ovirt.org/vdsm.git # timeout=10
> 07:29:50 Cleaning workspace
> 07:29:50  > git rev-parse --verify HEAD # timeout=10
> 07:29:50 Resetting working tree
> 07:29:50  > git reset --hard # timeout=10
> 07:29:51  > git clean -fdx # timeout=10
> 07:29:51 Pruning obsolete local branches
> 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git
> 07:29:51  > git --version # timeout=10
> 07:29:51  > git -c core.askpass=true fetch --tags --progress
> git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune
> 07:29:51 ERROR: Error fetching remote repo 'origin'
> 07:29:51 hudson.plugins.git.GitException: Failed to fetch from
> git://gerrit.ovirt.org/vdsm.git



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

[JIRA] (OVIRT-1128) Add Jenkins job for testing

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1128:
-
Issue Type: New Feature  (was: By-EMAIL)

> Add Jenkins job for testing
> ---
>
> Key: OVIRT-1128
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Pavel Zhukov
>Assignee: infra
>  Labels: staging
>
> it'd be good to have jenkins job to test and regenerate jenkins jobs :)
> which uses "good" jjb configuration and available for infra team from
> any machine.
> Currently local JJB instances and configs are used which is not perfect
> because configs can be different as well as jjb versions, not rebased
> repos can be used for testing  Besides of that it requires copying of
> configs between machines and so on.
> --
> Pavel



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

[JIRA] (OVIRT-1156) Fwd: build-artifacts-on-demand marks CI +1

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1156:
-
Issue Type: Bug  (was: By-EMAIL)

> Fwd: build-artifacts-on-demand marks CI +1
> --
>
> Key: OVIRT-1156
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1156
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Barak Korren
>Assignee: infra
>
> Forwarding to Jira.
> -- Forwarded message --
> From: Yedidyah Bar David 
> Date: 16 February 2017 at 15:02
> Subject: build-artifacts-on-demand marks CI +1
> To: infra 
> Hi all,
> I have a change [1] that currently fails some jenkins jobs, so it gets
> -1 from it. After pushing patchset 4 (a mere rebase actually), I ran
> build-artifacts-on-demand ("ci please build"), and it passed, and set
> CI +1. Then I rebased again and again got -1 as expected.
> IMO build-artifacts-on-demand should not set CI +1, it might be
> misleading for the maintainer to think that all is good when in fact
> CI failed.
> [1] https://gerrit.ovirt.org/71590
> --
> Didi
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
> -- 
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/



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

[JIRA] (OVIRT-1173) Please use git shallow clone as jobs default

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1173:
-
Issue Type: New Feature  (was: By-EMAIL)

> Please use git shallow clone as jobs default
> 
>
> Key: OVIRT-1173
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1173
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: rgo...@redhat.com
>Assignee: infra
>  Labels: standard-ci
>
> Most if not all the git clone of the jobs don't need history at all.
> For ovirt-engine I see it downloading *11Mb* using --depth 1 vs.  *157Mb*
> for regular clone.
> R



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

[JIRA] (OVIRT-1198) Job times out on: 'Removing the used loop devices' on the initial clean up stage

[eedri (oVirt JIRA)]

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

eedri commented on OVIRT-1198:
--

[~ngol...@redhat.com] have you seen it again since?

> Job times out on: 'Removing the used loop devices' on the initial clean up 
> stage
> 
>
> Key: OVIRT-1198
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1198
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: ngol...@redhat.com
>Assignee: infra
>
> 15:44:38 Making sure there are no device mappings...
> 15:44:38 Removing the used loop devices...
> 21:44:37 Build timed out (after 360 minutes). Marking the build as failed.
> 21:44:37 Build was aborted
> (Notice the 6 hours between).
> http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/710/console
> I think I saw another one earlier this week, also on fc25.



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

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1226:
-
Resolution: Fixed
Status: Done  (was: Blocked)

this should already be solved by moving find bugs code to check-patch.sh

> https://gerrit.ovirt.org/#/c/73161 marked with CI-1
> ---
>
> Key: OVIRT-1226
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful
> CI runs it had.



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

[JIRA] (OVIRT-1424) Re: Build timed out in Vdsm check-merged (was: False OST failure)

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1424:
-
Resolution: Duplicate
Status: Done  (was: To Do)

ovirt-1442

> Re: Build timed out in Vdsm check-merged (was: False OST failure)
> -
>
> Key: OVIRT-1424
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1424
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: eedri
>Assignee: infra
>
> adding infra-support to open a ticket.
> On Thu, Jun 1, 2017 at 10:28 AM, Milan Zamazal  wrote:
> > Another "Build timed out":
> >
> > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Eyal edri
> ASSOCIATE MANAGER
> RHV DevOps
> EMEA VIRTUALIZATION R
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)



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

[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1477:


Assignee: Barak Korren  (was: infra)

> Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages 
> on it own
> ---
>
> Key: OVIRT-1477
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: Barak Korren
>  Labels: repositories
>
> The 4.1 nightly publisher jobs are still using the old scheme of collecting 
> packages directly from build-artifacts jobs instead of from 'tested'. We 
> should move them to collect from 'tested' like the 'master' niightly 
> publisher jobs.
> As part of this work we should re-factor the YAML for the publisher jobs to 
> make all of them use the same YAML job template instead of hard-coded job 
> definitions.



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

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1479:
-
Epic Link: OVIRT-403  (was: OVIRT-400)

> dnf install in jobs setup scripts fails due to corrupted rpmdb
> --
>
> Key: OVIRT-1479
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: oVirt Infra
>Reporter: ngol...@redhat.com
>Assignee: infra
>  Labels: rpmdb, standard-ci
>
> {code}
> 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML
> 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: 
> BDB1507 Thread died in Berkeley DB library
> 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 
> DB_RUNRECOVERY: Fatal error, run database recovery
> 10:24:59 error: cannot open Packages index using db5 -  (-30973)
> 10:24:59 error: cannot open Packages database in /var/lib/rpm
> 10:24:59 Error: Error: rpmdb open failed
> 10:24:59 + failed=true
> {code}
> http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/91/console



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

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1479:
-
Epic Link: OVIRT-403  (was: OVIRT-400)

> dnf install in jobs setup scripts fails due to corrupted rpmdb
> --
>
> Key: OVIRT-1479
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: oVirt Infra
>Reporter: ngol...@redhat.com
>Assignee: infra
>  Labels: rpmdb, standard-ci
>
> {code}
> 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML
> 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: 
> BDB1507 Thread died in Berkeley DB library
> 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 
> DB_RUNRECOVERY: Fatal error, run database recovery
> 10:24:59 error: cannot open Packages index using db5 -  (-30973)
> 10:24:59 error: cannot open Packages database in /var/lib/rpm
> 10:24:59 Error: Error: rpmdb open failed
> 10:24:59 + failed=true
> {code}
> http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/91/console



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

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1479:
-
Epic Link: OVIRT-400  (was: OVIRT-403)

> dnf install in jobs setup scripts fails due to corrupted rpmdb
> --
>
> Key: OVIRT-1479
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: oVirt Infra
>Reporter: ngol...@redhat.com
>Assignee: infra
>  Labels: rpmdb, standard-ci
>
> {code}
> 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML
> 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: 
> BDB1507 Thread died in Berkeley DB library
> 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 
> DB_RUNRECOVERY: Fatal error, run database recovery
> 10:24:59 error: cannot open Packages index using db5 -  (-30973)
> 10:24:59 error: cannot open Packages database in /var/lib/rpm
> 10:24:59 Error: Error: rpmdb open failed
> 10:24:59 + failed=true
> {code}
> http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/91/console



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

[JIRA] (OVIRT-1479) dnf install in jobs setup scripts fails due to corrupted rpmdb

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1479:
-
Epic Link: OVIRT-400  (was: OVIRT-403)

> dnf install in jobs setup scripts fails due to corrupted rpmdb
> --
>
> Key: OVIRT-1479
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1479
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: oVirt Infra
>Reporter: ngol...@redhat.com
>Assignee: infra
>  Labels: rpmdb, standard-ci
>
> {code}
> 10:24:59 + sudo dnf -y install python3-PyYAML PyYAML
> 10:24:59 error: rpmdb: BDB0113 Thread/process 27225/140313046546176 failed: 
> BDB1507 Thread died in Berkeley DB library
> 10:24:59 error: db5 error(-30973) from dbenv->failchk: BDB0087 
> DB_RUNRECOVERY: Fatal error, run database recovery
> 10:24:59 error: cannot open Packages index using db5 -  (-30973)
> 10:24:59 error: cannot open Packages database in /var/lib/rpm
> 10:24:59 Error: Error: rpmdb open failed
> 10:24:59 + failed=true
> {code}
> http://jenkins.ovirt.org/job/lago_master_github_build-artifacts-el7-x86_64/91/console



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

[JIRA] (OVIRT-1257) Setup mail delivery from Jenkins and slaves

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1257:


Assignee: Marc Dequènes (Duck)  (was: infra)

> Setup mail delivery from Jenkins and slaves
> ---
>
> Key: OVIRT-1257
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1257
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI
>Reporter: Barak Korren
>Assignee: Marc Dequènes (Duck)
>Priority: High
>
> I'm setting up some jobs that will require Jenkins and/or the slaves to send 
> email to various places. Jenkins and the slaves seem to currently run Postfix 
> in a default configuration that makes them attempt to deliver email directly 
> to its destination. This causes sent email to get delayed.
> We typically don't notice this because our SPF setting for ovirt.org are 
> quite lax (We allow anyone to say he is from @ovirt.org, but delay messages 
> that are not from "{{lists.phx.ovirt.org}}, "{{mail.phx.ovirt.org}}", or 
> "{{gerrit.ovirt.org}}") abd because our ML server where we typically send to, 
> only imposes a 60second delay.
> We need to have a better setup. I suggest we configure Jenkins and the slaves 
> to use some other server as a smart host (maybe "{{mail.phx.ovirt.org}}"?). 
> To make the configuration as generic as possible I suggest we make the slaves 
> deliver via Jenkins and only make Jenkins deliver to the smart host.
> I think smart host configuration on Postfix is simple enough that we can make 
> our usual job-embedded slave setup scrips set it up insead of having to 
> resort to Puppet or Ansible.



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

[JIRA] (OVIRT-1471) Add SSL to jenkins.ovirt.org

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1471:


Assignee: Evgheni Dereveanchin  (was: infra)

> Add SSL to jenkins.ovirt.org
> 
>
> Key: OVIRT-1471
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1471
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt Infra
>Reporter: Barak Korren
>Assignee: Evgheni Dereveanchin
>Priority: High
>
> We probably need SSL for '{{jenkins.ovirt.org}}'. That server has privileges 
> on most stuff that is running in PHX, so better not have passwords to it be 
> exposed to MITM attacks...



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

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1061:
-
Epic Link: OVIRT-403

> Update http://monitoring.ovirt.org/ovirt.apps/
> --
>
> Key: OVIRT-1061
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring
> and production services currently being used in oVirt infra.
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1061:
-
Epic Link: OVIRT-403

> Update http://monitoring.ovirt.org/ovirt.apps/
> --
>
> Key: OVIRT-1061
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring
> and production services currently being used in oVirt infra.
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-1275) Allow anonymous access to nagios dashboard

[eedri (oVirt JIRA)]

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

eedri reassigned OVIRT-1275:


Assignee: Evgheni Dereveanchin  (was: infra)

> Allow anonymous access to nagios dashboard
> --
>
> Key: OVIRT-1275
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1275
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eedri
>Assignee: Evgheni Dereveanchin
>
> Right now you need a password to just view the main page of 
> monitoring.ovirt.org.
> It will be better if you won't need to login just to view the status, that 
> way anyone can look at current status w/o logging in and verify if there is 
> an outage.



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

[JIRA] (OVIRT-1410) Please update #ovirt motd with oVirt 4.1.2

[eedri (oVirt JIRA)]

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

eedri updated OVIRT-1410:
-
Epic Link: OVIRT-403

> Please update #ovirt motd with oVirt 4.1.2
> --
>
> Key: OVIRT-1410
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1410
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Joining #ovirt channel gives:
> *oVirt 4.1.0 is now available. Please register your nick to participate in
> this channel.*
> Please, update with oVirt 4.1.2.
> -- 
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> Red Hat EMEA 
> 
> TRIED. TESTED. TRUSTED. 



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