May 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2019) users can't unsubscribe from list
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

eyal edri created OVIRT-2019: -------------------------------- Summary: users can't unsubscribe from list Key: OVIRT-2019 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2019 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri Assignee: infra Priority: Highest There has been multiple reports from users on users(a)ovirt.org that they can't un-subscribe from the list, either using the UI or the leave ML alias. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2018) Add documentation for the stdci_conf_check.py utility
by Emil Natan (oVirt JIRA) 13 May '18

13 May '18

Emil Natan created OVIRT-2018: --------------------------------- Summary: Add documentation for the stdci_conf_check.py utility Key: OVIRT-2018 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2018 Project: oVirt - virtualization made easy Issue Type: Task Components: Documentation Reporter: Emil Natan Assignee: infra Priority: Low -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2017) Add fc28 slave to jenkins
by Gal Ben Haim (oVirt JIRA) 13 May '18

13 May '18

Gal Ben Haim created OVIRT-2017: ----------------------------------- Summary: Add fc28 slave to jenkins Key: OVIRT-2017 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2017 Project: oVirt - virtualization made easy Issue Type: Bug Components: Lago Reporter: Gal Ben Haim Assignee: infra fc28 slave is required for lago's check-patch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1465: ----------------------------------- Assignee: Barak Korren (was: infra) > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > Labels: jenkins, jjb, standard-ci > > Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1465: -------------------------------- Description: Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo. Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. was: Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo. Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. > Run JJB from 'check-merged' of 'jenkins' repo instead of its own job > -------------------------------------------------------------------- > > Key: OVIRT-1465 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, jjb, standard-ci > > Right now we have a custom job for running JJB after patches are merged to the 'jenkins' repo. > Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2015: ------------------------------------- [~eedri] I see. [~dron] - just for the sake of full RCA - lets find the smoking gun here and see if the patch was indeed merged with CI that failed on this. Lets think if we can make a short lesson to the team about this kind of incident in one way or another (E.g in email or in the MTG tomorrow). > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

Please help unsubscribing inactive members
by Yaniv Kaul 13 May '18

13 May '18

Vered left, but Allon could not / did not cancel her subscription. Now Allon left, and I'm getting the emails: Delivered-To: ykaul(a)redhat.com Received: by smtp.corp.redhat.com (Postfix, from userid 8) id 0082F3001656; Sun, 13 May 2018 06:53:57 +0000 (UTC) X-Original-To: amureini Delivered-To: amureini(a)redhat.com Received: by smtp.corp.redhat.com (Postfix, from userid 8) id E64673001641; Sun, 13 May 2018 06:53:57 +0000 (UTC) X-Original-To: vvolansk(a)redhat.com Delivered-To: vvolansk(a)redhat.com Can we somehow remove vvolansk(a)redhat.com from infra(a)ovirt.org?

2 4

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2015: ---------------------------------- It might have failed and I missed it, due to the will to solve the 7.5 and 4.1 issues fast, I think I might have thought the failure was reposync related and it will get fixed once I open the master repos. > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by Barak Korren (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2015: ------------------------------------- [~eedri] yeah , I chatted with [~dron] about this a little - the thing we need to check here is why the OST check-patch didn't catch this for us. > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by eyal edri (oVirt JIRA) 13 May '18

13 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2015: ---------------------------------- CQ can also fail on OST test change, which is not (yet) a CQ object, you have to take that into account when debugging failures. so I'm not sure this is a real issue. [~bkorren(a)redhat.com] > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100083)

1 0