- Infra - oVirt List Archives

[JIRA] (OVIRT-2073) Re: I'm working on the cockpit-gluster plugin and I'd like to be on the wihtelist
by eyal edri (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2073?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2073: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: I'm working on the cockpit-gluster plugin and I'd like to be on the wihtelist > --------------------------------------------------------------------------------- > > Key: OVIRT-2073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2073 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: infra > > Hi Rohan! > The process is quite simple, you just need to ask one of the existing > maintainers to send a patch to the 'jenkins-whitelist' repo on > gerrit.ovirt.org and > one of the infra members can merge it once it has +1 from an existing > maintainer. > I'm also adding 'infra-support' to open a ticket. > On Fri, Jun 1, 2018 at 9:20 AM, Rohan Joseph <rojoseph(a)redhat.com> wrote: > > Hi! > > > > I'm working on the cockpit-gluster plugin and I'd like to be on the > > wihtelist to submit patches to gerrit.ovirt.org. > > > > Thanks! > > > > - Rohan CJ > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > > guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/ > > message/QTQLCWVB5SMNU2MYOBUYUFW5M3HEPWVN/ > > > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2073) Re: I'm working on the cockpit-gluster plugin and I'd like to be on the wihtelist
by eyal edri (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2073?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2073: ---------------------------------- [https://gerrit.ovirt.org/\#/c/91943/|https://gerrit.ovirt.org/#/c/91943/] > Re: I'm working on the cockpit-gluster plugin and I'd like to be on the wihtelist > --------------------------------------------------------------------------------- > > Key: OVIRT-2073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2073 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: infra > > Hi Rohan! > The process is quite simple, you just need to ask one of the existing > maintainers to send a patch to the 'jenkins-whitelist' repo on > gerrit.ovirt.org and > one of the infra members can merge it once it has +1 from an existing > maintainer. > I'm also adding 'infra-support' to open a ticket. > On Fri, Jun 1, 2018 at 9:20 AM, Rohan Joseph <rojoseph(a)redhat.com> wrote: > > Hi! > > > > I'm working on the cockpit-gluster plugin and I'd like to be on the > > wihtelist to submit patches to gerrit.ovirt.org. > > > > Thanks! > > > > - Rohan CJ > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > > guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/ > > message/QTQLCWVB5SMNU2MYOBUYUFW5M3HEPWVN/ > > > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2066) Re: Users list mail issue
by eyal edri (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2066?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2066: ---------------------------------- [~duck] are there any open issues on the list or we can close this? > Re: Users list mail issue > ------------------------- > > Key: OVIRT-2066 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2066 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Marc Dequènes (Duck) > > Opening a ticket > On Wed, May 30, 2018, 18:39 Fred Rolland <frolland(a)redhat.com> wrote: > > Hi, > > > > It seems that I am receiving some emails from users list after a long > > delay. > > > > For example this thread: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/5N6N4BHF6ZFJLE… > > > > I have received only 2 emails from this thread, and my colleagues did not > > receive the one I sent 4 hours ago. > > > > > > Any idea what is the problem? > > > > Thanks, > > Freddy > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6EKS6OYUQK7BK… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2066) Re: Users list mail issue
by eyal edri (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2066?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2066: -------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Re: Users list mail issue > ------------------------- > > Key: OVIRT-2066 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2066 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Marc Dequènes (Duck) > > Opening a ticket > On Wed, May 30, 2018, 18:39 Fred Rolland <frolland(a)redhat.com> wrote: > > Hi, > > > > It seems that I am receiving some emails from users list after a long > > delay. > > > > For example this thread: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/5N6N4BHF6ZFJLE… > > > > I have received only 2 emails from this thread, and my colleagues did not > > receive the one I sent 4 hours ago. > > > > > > Any idea what is the problem? > > > > Thanks, > > Freddy > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6EKS6OYUQK7BK… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2011) Fwd: Rerun-hooks doesn't work
by eyal edri (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2011?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2011: ----------------------------- Resolution: Duplicate Status: Done (was: To Do) was fixed already. > Fwd: Rerun-hooks doesn't work > ----------------------------- > > Key: OVIRT-2011 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2011 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: infra > > Forwarding to infra-support to create a Jira ticket. > ---------- Forwarded message ---------- > From: Tal Nisan <tnisan(a)redhat.com> > Date: 9 May 2018 at 13:04 > Subject: Rerun-hooks doesn't work > To: infra <infra(a)ovirt.org> > The Rerun-hooks: all used to rerun the hooks after changing something in > the commit message doesn't work for a few months now and it's quite needed > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > -- > 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 (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 487 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jun '18

17 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/487/ Build Number: 487 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #487 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Barak Korren (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2201: -------------------------------- Issue Type: Improvement (was: By-EMAIL) > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Barak Korren (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2201: -------------------------------- Component/s: Standard CI (Pipelines) > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Barak Korren (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2201: ------------------------------------- [~sbonazzo(a)redhat.com] rereading our chat transcript above it seems to me that given that in V2, things do not land on 'tested' unless they pass check-merged (in addition to all other conditions), and if we implement OVIRT-1717 (tagging commints that make it to tested), we can drop this requirement. Am I right about this, or are there other use cases I need to take into account? > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 296 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 Jun '18

17 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/296/ Build Number: 296 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #296 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

1 1