- Infra - oVirt List Archives

[JIRA] (OVIRT-1287) Fwd: doc-police
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1287?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1287: --------------------------------------------- Comment: was deleted (was: doc police is downstream only project.... On Wed, Mar 29, 2017 at 1:29 PM, Gil Shinar (oVirt JIRA) < -- Eyal edri ASSOCIATE 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) ) > Fwd: doc-police > --------------- > > Key: OVIRT-1287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1287 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > I'm forwarding to infra-support so a Jira task will be opened. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Wed, Mar 29, 2017 at 1:22 PM > Subject: doc-police > To: rhev-integ <rhev-integ(a)redhat.com> > Hi all, > 1. Where is the code of doc-police maintained? Does this project have > any doc page or anything other than its code? I suggest to add a > header line to emails it sends linking there. E.g.: > X-doc-police-project-page: http://some.where.redhat.com > Or perhaps add something like this to each and every program we write > that sends email, so that it's easy to track who sent the email, e.g.: > X-RHV-project-name: doc-police > X-RHV-project-URL: http://some.where.redhat.com > Or whatever you feel like. > 2. (minor) It's missing 'Message-Id:', which is iirc mandatory, and > gmail adds it for us (which is ugly). E.g. in one of the emails it > sent me, there is: > Message-Id: <58d239f5.0ca7370a.88414.228aSMTPIN_ADDED_MISSING(a)mx.google.com> > 3. Is it working currently? I didn't receive an email from it about bz > 1419579. Perhaps it has too-strict filtering? > 4. Does it log anywhere what it does? A particular mail it sent was > sent (according to the headers) from 10.35.37.108 . I logged in there > and couldn't find anything in /var/log. > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1287) Fwd: doc-police
by Gil Shinar (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1287?page=com.atlassian.jira.… ] Gil Shinar updated OVIRT-1287: ------------------------------ Resolution: Won't Fix Status: Done (was: To Do) D/S bug > Fwd: doc-police > --------------- > > Key: OVIRT-1287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1287 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > I'm forwarding to infra-support so a Jira task will be opened. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Wed, Mar 29, 2017 at 1:22 PM > Subject: doc-police > To: rhev-integ <rhev-integ(a)redhat.com> > Hi all, > 1. Where is the code of doc-police maintained? Does this project have > any doc page or anything other than its code? I suggest to add a > header line to emails it sends linking there. E.g.: > X-doc-police-project-page: http://some.where.redhat.com > Or perhaps add something like this to each and every program we write > that sends email, so that it's easy to track who sent the email, e.g.: > X-RHV-project-name: doc-police > X-RHV-project-URL: http://some.where.redhat.com > Or whatever you feel like. > 2. (minor) It's missing 'Message-Id:', which is iirc mandatory, and > gmail adds it for us (which is ugly). E.g. in one of the emails it > sent me, there is: > Message-Id: <58d239f5.0ca7370a.88414.228aSMTPIN_ADDED_MISSING(a)mx.google.com> > 3. Is it working currently? I didn't receive an email from it about bz > 1419579. Perhaps it has too-strict filtering? > 4. Does it log anywhere what it does? A particular mail it sent was > sent (according to the headers) from 10.35.37.108 . I logged in there > and couldn't find anything in /var/log. > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1287) Fwd: doc-police
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1287?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1287: -------------------------------------------------- doc police is downstream only project.... On Wed, Mar 29, 2017 at 1:29 PM, Gil Shinar (oVirt JIRA) < -- Eyal edri ASSOCIATE 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) > Fwd: doc-police > --------------- > > Key: OVIRT-1287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1287 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > I'm forwarding to infra-support so a Jira task will be opened. > ---------- Forwarded message ---------- > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Wed, Mar 29, 2017 at 1:22 PM > Subject: doc-police > To: rhev-integ <rhev-integ(a)redhat.com> > Hi all, > 1. Where is the code of doc-police maintained? Does this project have > any doc page or anything other than its code? I suggest to add a > header line to emails it sends linking there. E.g.: > X-doc-police-project-page: http://some.where.redhat.com > Or perhaps add something like this to each and every program we write > that sends email, so that it's easy to track who sent the email, e.g.: > X-RHV-project-name: doc-police > X-RHV-project-URL: http://some.where.redhat.com > Or whatever you feel like. > 2. (minor) It's missing 'Message-Id:', which is iirc mandatory, and > gmail adds it for us (which is ugly). E.g. in one of the emails it > sent me, there is: > Message-Id: <58d239f5.0ca7370a.88414.228aSMTPIN_ADDED_MISSING(a)mx.google.com> > 3. Is it working currently? I didn't receive an email from it about bz > 1419579. Perhaps it has too-strict filtering? > 4. Does it log anywhere what it does? A particular mail it sent was > sent (according to the headers) from 10.35.37.108 . I logged in there > and couldn't find anything in /var/log. > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1287) Fwd: doc-police
by Gil Shinar (oVirt JIRA) 29 Mar '17

29 Mar '17

Gil Shinar created OVIRT-1287: --------------------------------- Summary: Fwd: doc-police Key: OVIRT-1287 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1287 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Gil Shinar Assignee: infra I'm forwarding to infra-support so a Jira task will be opened. ---------- Forwarded message ---------- From: Yedidyah Bar David <didi(a)redhat.com> Date: Wed, Mar 29, 2017 at 1:22 PM Subject: doc-police To: rhev-integ <rhev-integ(a)redhat.com> Hi all, 1. Where is the code of doc-police maintained? Does this project have any doc page or anything other than its code? I suggest to add a header line to emails it sends linking there. E.g.: X-doc-police-project-page: http://some.where.redhat.com Or perhaps add something like this to each and every program we write that sends email, so that it's easy to track who sent the email, e.g.: X-RHV-project-name: doc-police X-RHV-project-URL: http://some.where.redhat.com Or whatever you feel like. 2. (minor) It's missing 'Message-Id:', which is iirc mandatory, and gmail adds it for us (which is ugly). E.g. in one of the emails it sent me, there is: Message-Id: <58d239f5.0ca7370a.88414.228aSMTPIN_ADDED_MISSING(a)mx.google.com> 3. Is it working currently? I didn't receive an email from it about bz 1419579. Perhaps it has too-strict filtering? 4. Does it log anywhere what it does? A particular mail it sent was sent (according to the headers) from 10.35.37.108 . I logged in there and couldn't find anything in /var/log. Best, -- Didi -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by Barak Korren (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1281: ------------------------------------- [~danken(a)redhat.com] this sounds more like the kind of functionality you would find in a ticketing/task management systems rather then in a code review/scm system. I doubt Gerrit has anything like that built-in. What would the practical aspects of someone being the ReviewAssignee be? Nag emails? Wouldn't just commenting with "@someone please review this" be enough? > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

jenkins dev role for mlipchuk user
by Maor Lipchuk 29 Mar '17

29 Mar '17

Hi, Can you please add dev role to mlipchuk user so I can run the ci manual tests Thanks, Maor

3 3

[JIRA] (OVIRT-1286) Re: Asking for 'dev role' permissions
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1286?page=com.atlassian.jira.… ] Pavel Zhukov updated OVIRT-1286: -------------------------------- Resolution: Fixed Status: Done (was: Blocked) > Re: Asking for 'dev role' permissions > ------------------------------------- > > Key: OVIRT-1286 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1286 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Zhukov > Assignee: Pavel Zhukov > > Adding infra-support to open a ticket. > On Wed, Mar 29 2017, Shani Leviim wrote: > > Hi, > > I'm trying to be more involved with OST runs and testing. > > According to [1], can you please grant me the 'dev role' permissions? > > Thanks, > > > > Regards, > > Shani Leviim > > Intern > > Red Hat Israel > > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Pavel Zhukov -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

Asking for 'dev role' permissions
by Shani Leviim 29 Mar '17

29 Mar '17

Hi, I'm trying to be more involved with OST runs and testing. According to [1], can you please grant me the 'dev role' permissions? Thanks, *Regards,* *Shani LeviimInternRed Hat Israel* [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/

3 4

[JIRA] (OVIRT-1284) Fwd: jenkins dev role for mlipchuk user
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1284?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1284: ----------------------------------- Assignee: Pavel Zhukov (was: infra) > Fwd: jenkins dev role for mlipchuk user > --------------------------------------- > > Key: OVIRT-1284 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1284 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Pavel Zhukov > > Forwarding to infra-support to open ticket > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ > ‏---------- הודעה שהועברה ---------- > מאת: "Maor Lipchuk" <mlipchuk(a)redhat.com> > תאריך: 28 במרץ 2017 18:00 > נושא: jenkins dev role for mlipchuk user > אל: "infra" <infra(a)ovirt.org> > ‏עותק: > Hi, > > > > Can you please add dev role to mlipchuk user so I can run the ci manual > > tests > > > > Thanks, > > Maor > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1286) Re: Asking for 'dev role' permissions
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1286?page=com.atlassian.jira.… ] Pavel Zhukov updated OVIRT-1286: -------------------------------- Blocked By: pending user response Status: Blocked (was: In Progress) > Re: Asking for 'dev role' permissions > ------------------------------------- > > Key: OVIRT-1286 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1286 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Zhukov > Assignee: Pavel Zhukov > > Adding infra-support to open a ticket. > On Wed, Mar 29 2017, Shani Leviim wrote: > > Hi, > > I'm trying to be more involved with OST runs and testing. > > According to [1], can you please grant me the 'dev role' permissions? > > Thanks, > > > > Regards, > > Shani Leviim > > Intern > > Red Hat Israel > > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Pavel Zhukov -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1286) Re: Asking for 'dev role' permissions
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1286?page=com.atlassian.jira.… ] Pavel Zhukov updated OVIRT-1286: -------------------------------- Status: In Progress (was: To Do) > Re: Asking for 'dev role' permissions > ------------------------------------- > > Key: OVIRT-1286 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1286 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Zhukov > Assignee: Pavel Zhukov > > Adding infra-support to open a ticket. > On Wed, Mar 29 2017, Shani Leviim wrote: > > Hi, > > I'm trying to be more involved with OST runs and testing. > > According to [1], can you please grant me the 'dev role' permissions? > > Thanks, > > > > Regards, > > Shani Leviim > > Intern > > Red Hat Israel > > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Pavel Zhukov -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1280) Upstream mirrors are used to install cockpit
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1280?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1280: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Upstream mirrors are used to install cockpit > -------------------------------------------- > > Key: OVIRT-1280 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1280 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: Daniel Belenky > Priority: High > > 2017-03-27 12:24:21,563::ssh.py::ssh::89::lago.ssh::DEBUG::Command 3bc628c4 on lago-basic-suite-4-1-host0 output: > Loaded plugins: fastestmirror > Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was > 12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1081/artifact… -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1286) Re: Asking for 'dev role' permissions
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1286?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1286: ----------------------------------- Assignee: Pavel Zhukov (was: infra) > Re: Asking for 'dev role' permissions > ------------------------------------- > > Key: OVIRT-1286 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1286 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Zhukov > Assignee: Pavel Zhukov > > Adding infra-support to open a ticket. > On Wed, Mar 29 2017, Shani Leviim wrote: > > Hi, > > I'm trying to be more involved with OST runs and testing. > > According to [1], can you please grant me the 'dev role' permissions? > > Thanks, > > > > Regards, > > Shani Leviim > > Intern > > Red Hat Israel > > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Pavel Zhukov -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1285) Re: Asking for 'dev role' permissions
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1285?page=com.atlassian.jira.… ] Pavel Zhukov updated OVIRT-1285: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) OVIRT-1286 > Re: Asking for 'dev role' permissions > ------------------------------------- > > Key: OVIRT-1285 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1285 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > Adding infra-support to open a ticket. > On Wed, Mar 29, 2017 at 11:50 AM, Shani Leviim <sleviim(a)redhat.com> wrote: > > Hi, > > I'm trying to be more involved with OST runs and testing. > > According to [1], can you please grant me the 'dev role' permissions? > > Thanks, > > > > > > *Regards,* > > > > > > *Shani LeviimInternRed Hat Israel* > > > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal edri > ASSOCIATE 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 (v1000.867.1#100039)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1099 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Mar '17

29 Mar '17

------=_Part_43_1949048465.1490757520534 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1099/, Build Number: 1099, Build Status: FAILURE ------=_Part_43_1949048465.1490757520534--

1 1

[JIRA] (OVIRT-1286) Re: Asking for 'dev role' permissions
by Pavel Zhukov (oVirt JIRA) 29 Mar '17

29 Mar '17

Pavel Zhukov created OVIRT-1286: ----------------------------------- Summary: Re: Asking for 'dev role' permissions Key: OVIRT-1286 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1286 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Pavel Zhukov Assignee: infra Adding infra-support to open a ticket. On Wed, Mar 29 2017, Shani Leviim wrote: > Hi, > I'm trying to be more involved with OST runs and testing. > According to [1], can you please grant me the 'dev role' permissions? > Thanks, > > Regards, > Shani Leviim > Intern > Red Hat Israel > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- Pavel Zhukov -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by danken (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] danken commented on OVIRT-1281: ------------------------------- I'd like to set a single ReviewAssignee to a patch, so that it is very clear to everybody who needs to review this patch today. The current ReviewAssignee can give his score, and pass the role to someone else. In my opinion, anybody can take the role, or grant it to someone else. This comes to solve the current situation, where a patch has multiple reviewers, but no one in particular is responsible to review this first. > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1281: -------------------------------------------------- [~oourfali(a)redhat.com] [~danken(a)redhat.com] Since you requested this feature, please try to elaborate on the need and use case which this is needed. > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1285) Re: Asking for 'dev role' permissions
by eyal edri [Administrator] (oVirt JIRA) 29 Mar '17

29 Mar '17

eyal edri [Administrator] created OVIRT-1285: ------------------------------------------------ Summary: Re: Asking for 'dev role' permissions Key: OVIRT-1285 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1285 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Adding infra-support to open a ticket. On Wed, Mar 29, 2017 at 11:50 AM, Shani Leviim <sleviim(a)redhat.com> wrote: > Hi, > I'm trying to be more involved with OST runs and testing. > According to [1], can you please grant me the 'dev role' permissions? > Thanks, > > > *Regards,* > > > *Shani LeviimInternRed Hat Israel* > > [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/ > > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal edri ASSOCIATE 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 (v1000.867.1#100039)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by Barak Korren (oVirt JIRA) 29 Mar '17

29 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1281: ------------------------------------- Gerrit supports a patch owner, author and commiter, all of which can probably be different people (Though I'm not sure what you need to do to configure each field). What is the real-world use case for this request? Please describe a detailed process. > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.867.1#100039)

1 0

[oVirt Jenkins] ovirt_master_image-ng-system-tests - Build # 55 - Still Failing!
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

------=_Part_112_676206853.1490512437648 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/= =20 Build: http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/55/ Build Number: 55 Build Status: Still Failing Triggered By: Started by user Eyal Edri ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #37 [Yaniv Kaul] Slim down the amount of packages we sync Changes for Build #38 [Yaniv Kaul] Slim down the amount of packages we sync [Eyal Edri] remove emails from repo closure jobs Changes for Build #39 [Ond=C5=99ej Svoboda] Add a VM with a custom MAC to the second SD. [Sandro Bonazzola] repos-check-closure: move master from f24 to f25 [Sandro Bonazzola] pthreading: move from fc24 to fc25 on master [Sandro Bonazzola] aaa-misc: drop fc24 on master [Sandro Bonazzola] logger-log4j: drop fc24 on master [Sandro Bonazzola] python-windows: drop fc24 on master [Sandro Bonazzola] py2exe-py2.7: drop fc24 on master Changes for Build #40 [Ond=C5=99ej Svoboda] Add a VM with a custom MAC to the second SD. Changes for Build #41 [Ond=C5=99ej Svoboda] Add a VM with a custom MAC to the second SD. Changes for Build #42 [ngoldin] Add the engine VM IP as a valid FQDN on setup [Daniel Belenky] mock_stup and mock_cleanup:Add Docker engine installation = and cleanup Changes for Build #43 [Eyal Edri] exclude openvswitch-devel & test pkg from ovirt repo [Daniel Belenky] mock_cleanup: skip docker cleanup if docker is not install= ed Changes for Build #44 [Lev Veyde] Configure NFSv3 to use static ports [Sandro Bonazzola] qemu: don't publish on master [Sandro Bonazzola] ovirt-release: add check-patch for ppc64le Changes for Build #45 [Lev Veyde] Configure NFSv3 to use static ports [Eyal Edri] dropping jobs from master publisher - first patch [Ryan Barry] Remove vintage node jobs Changes for Build #46 [Lev Veyde] Configure NFSv3 to use static ports [Sandro Bonazzola] ovirt-engine-cli: drop fc24 on master [Sandro Bonazzola] ovirt-engine-yarn: drop fc24 on master [Sandro Bonazzola] ovirt-imageio: drop fc24 on master [Sandro Bonazzola] ovirt-vmconsole: drop fc24 on master Changes for Build #47 [Lev Veyde] Configure NFSv3 to use static ports Changes for Build #48 [Ondra Machacek] Fix Ansible modules tests [Daniel Belenky] ost publisher: replaced 'email' with 'email-ext' [Gil Shinar] New builder that includes a few more std steps Changes for Build #49 [Yaniv Kaul] Fix cockpit dependencies [Sandro Bonazzola] ovirt-optimizer: drop fc24 on master [Sandro Bonazzola] ovirt-scheduler-proxy: drop fc24 on master [Yaniv Bronhaim] remove check-merged job in python-pthreading [Daniel Belenky] jenkins (system_tests_template): added email-to macro to m= atch the [Pavel Zhukov] Add ovirt-web-ui project. [ngoldin] Add lago-demo check-patch job [Gil Shinar] Changing mock_runner mocks map to be in a file Changes for Build #50 [Simone Tiraboschi] hc: rebase on last gdeploy [Pavel Zhukov] Fix typo in github.yaml Changes for Build #51 [Simone Tiraboschi] he: fetch the domain name on the first HE host [Eyal Edri] remove ovirt 4.0 jobs [Pavel Zhukov] Use webhooks instead of polling [idodoroz] Remove opstools-ansible from oVirt repos Changes for Build #52 [Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo [Eyal Edri] removing projects from master publisher - stage II Changes for Build #53 [Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo [Sandro Bonazzola] ovirt-release: test ppc64le on master only [Sandro Bonazzola] ebay-cors-filter: drop jobs Changes for Build #54 [Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo Changes for Build #55 [Eyal Edri] rename ovirt-4.1.repo to ovirt-4.1-stable.repo ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_cluster Error Message: status: 409 reason: Conflict detail: KSM or balooning must be enabled to allow memory optimization. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 367, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in= wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt_master_image-ng-system-tests/ovirt-sy= stem-tests/image-ng-suite-master/test-scenarios/002_bootstrap.py", line 104= , in add_cluster nt.assert_true(api.clusters.add(p)) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 2854, in add headers=3D{"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 79, in add return self.request('POST', url, body, headers, cls=3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) RequestError:=20 status: 409 reason: Conflict detail: KSM or balooning must be enabled to allow memory optimization. =20 ------=_Part_112_676206853.1490512437648--

3 8

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6066 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

------=_Part_14_1782252100.1490711152458 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066/, Build Number: 6066, Build Status: FAILURE ------=_Part_14_1782252100.1490711152458--

1 9

oVirt infra daily report - unstable production jobs - 274
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

------=_Part_34_1360530363.1490742018670 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/274//artifact/exported-a… Cheers, Jenkins ------=_Part_34_1360530363.1490742018670 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 28/03/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_34_1360530363.1490742018670--

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #195
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/195/displa…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 395700ab9bea6237d521543aa1b88620d106d71b (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 395700ab9bea6237d521543aa1b88620d106d71b > git rev-list 395700ab9bea6237d521543aa1b88620d106d71b # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson8893048609426993807.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1451, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1429, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 911, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 899, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fc25/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1284) Fwd: jenkins dev role for mlipchuk user
by Barak Korren (oVirt JIRA) 28 Mar '17

28 Mar '17

Barak Korren created OVIRT-1284: ----------------------------------- Summary: Fwd: jenkins dev role for mlipchuk user Key: OVIRT-1284 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1284 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support to open ticket Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ ‏---------- הודעה שהועברה ---------- מאת: "Maor Lipchuk" <mlipchuk(a)redhat.com> תאריך: 28 במרץ 2017 18:00 נושא: jenkins dev role for mlipchuk user אל: "infra" <infra(a)ovirt.org> ‏עותק: Hi, > > Can you please add dev role to mlipchuk user so I can run the ci manual > tests > > Thanks, > Maor > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

Change in barak-test[master]: Just a dummy change for testing
by review＠gerrit-staging.phx.ovirt.org 28 Mar '17

28 Mar '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. Change subject: Just a dummy change for testing ...................................................................... Patch Set 2: -Code-Review -- To view, visit https://gerrit-staging.phx.ovirt.org/4 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5 Gerrit-PatchSet: 2 Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in barak-test[master]: Just a dummy change for testing
by review＠gerrit-staging.phx.ovirt.org 28 Mar '17

28 Mar '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. Change subject: Just a dummy change for testing ...................................................................... Patch Set 2: Code-Review-1 -Verified testing again -- To view, visit https://gerrit-staging.phx.ovirt.org/4 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5 Gerrit-PatchSet: 2 Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in barak-test[master]: Just a dummy change for testing
by review＠gerrit-staging.phx.ovirt.org 28 Mar '17

28 Mar '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. Change subject: Just a dummy change for testing ...................................................................... Patch Set 2: testing mc'testing -- To view, visit https://gerrit-staging.phx.ovirt.org/4 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5 Gerrit-PatchSet: 2 Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-1282) repoclosure is failed on gdeploy
by Pavel Zhukov (oVirt JIRA) 28 Mar '17

28 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1282?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1282: ----------------------------------- Assignee: Daniel Belenky (was: infra) > repoclosure is failed on gdeploy > -------------------------------- > > Key: OVIRT-1282 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1282 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: Daniel Belenky > Priority: Highest > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066 > 14:18:36 [basic_suit_el7] Repos looked at: 10 > 14:18:36 [basic_suit_el7] centos-base-el7 > 14:18:36 [basic_suit_el7] centos-extras-el7 > 14:18:36 [basic_suit_el7] centos-opstools-testing-el7 > 14:18:36 [basic_suit_el7] centos-ovirt-4.0-el7 > 14:18:36 [basic_suit_el7] centos-updates-el7 > 14:18:36 [basic_suit_el7] epel-el7 > 14:18:36 [basic_suit_el7] glusterfs-3.10-el7 > 14:18:36 [basic_suit_el7] internal_repo > 14:18:36 [basic_suit_el7] ovirt-master-snapshot-static-el7 > 14:18:36 [basic_suit_el7] ovirt-master-tested-el7 > 14:18:36 [basic_suit_el7] Num Packages in Repos: 38045 > 14:18:36 [basic_suit_el7] package: ovirt-release-host-node-4.2.0-0.3.master.20170328000035.git67870d2.el7.centos.noarch from internal_repo > 14:18:36 [basic_suit_el7] unresolved deps: > 14:18:36 [basic_suit_el7] gdeploy -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[JIRA] (OVIRT-1283) Repoclosure test output should be more verbose
by Pavel Zhukov (oVirt JIRA) 28 Mar '17

28 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1283?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1283: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Repoclosure test output should be more verbose > ---------------------------------------------- > > Key: OVIRT-1283 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1283 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: Daniel Belenky > Priority: High > > In current implementation it's not telling too much about the failure itself: > Error Message > Error: repoclosure failed. exit code is: 256 > Stacktrace > Traceback (most recent call last): > File "/usr/lib64/python2.7/unittest/case.py", line 369, in run > testMethod() > File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest > self.test(*self.arg) > File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test > test() > File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/000_check_repo_closure.py", line 95, in check_repo_closure > res, 0, 'Error: repoclosure failed. exit code is: {}'.format(res) > File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, in eq_ > raise AssertionError(msg or "%r != %r" % (a, b)) > AssertionError: Error: repoclosure failed. exit code is: 256 -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-03-2017 ] [ repoclosure ]
by Pavel Zhukov 28 Mar '17

28 Mar '17

Hi, Newly introduced repoclosure test is failed [1] on gdeploy package (GlusterFS) [2] As we hadn't run this test before the only suspected patch is the patch to add the test itself: 959e735c1c02a74c209fffc03d76f67ccf86606e ost: added repo closure test [1] http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066/ [2] 14:18:36 [basic_suit_el7] Repos looked at: 10 14:18:36 [basic_suit_el7] centos-base-el7 14:18:36 [basic_suit_el7] centos-extras-el7 14:18:36 [basic_suit_el7] centos-opstools-testing-el7 14:18:36 [basic_suit_el7] centos-ovirt-4.0-el7 14:18:36 [basic_suit_el7] centos-updates-el7 14:18:36 [basic_suit_el7] epel-el7 14:18:36 [basic_suit_el7] glusterfs-3.10-el7 14:18:36 [basic_suit_el7] internal_repo 14:18:36 [basic_suit_el7] ovirt-master-snapshot-static-el7 14:18:36 [basic_suit_el7] ovirt-master-tested-el7 14:18:36 [basic_suit_el7] Num Packages in Repos: 38045 14:18:36 [basic_suit_el7] package: ovirt-release-host-node-4.2.0-0.3.master.20170328000035.git67870d2.el7.centos.noarch from internal_repo 14:18:36 [basic_suit_el7] unresolved deps: 14:18:36 [basic_suit_el7] gdeploy -- Pavel Zhukov

1 0

[JIRA] (OVIRT-1283) Repoclosure test output should be more verbose
by Pavel Zhukov (oVirt JIRA) 28 Mar '17

28 Mar '17

Pavel Zhukov created OVIRT-1283: ----------------------------------- Summary: Repoclosure test output should be more verbose Key: OVIRT-1283 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1283 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Pavel Zhukov Assignee: infra Priority: High In current implementation it's not telling too much about the failure itself: Error Message Error: repoclosure failed. exit code is: 256 Stacktrace Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/000_check_repo_closure.py", line 95, in check_repo_closure res, 0, 'Error: repoclosure failed. exit code is: {}'.format(res) File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, in eq_ raise AssertionError(msg or "%r != %r" % (a, b)) AssertionError: Error: repoclosure failed. exit code is: 256 -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[JIRA] (OVIRT-1282) repoclosure is failed on gdeploy
by Pavel Zhukov (oVirt JIRA) 28 Mar '17

28 Mar '17

Pavel Zhukov created OVIRT-1282: ----------------------------------- Summary: repoclosure is failed on gdeploy Key: OVIRT-1282 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1282 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Pavel Zhukov Assignee: infra Priority: Highest http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6066 14:18:36 [basic_suit_el7] Repos looked at: 10 14:18:36 [basic_suit_el7] centos-base-el7 14:18:36 [basic_suit_el7] centos-extras-el7 14:18:36 [basic_suit_el7] centos-opstools-testing-el7 14:18:36 [basic_suit_el7] centos-ovirt-4.0-el7 14:18:36 [basic_suit_el7] centos-updates-el7 14:18:36 [basic_suit_el7] epel-el7 14:18:36 [basic_suit_el7] glusterfs-3.10-el7 14:18:36 [basic_suit_el7] internal_repo 14:18:36 [basic_suit_el7] ovirt-master-snapshot-static-el7 14:18:36 [basic_suit_el7] ovirt-master-tested-el7 14:18:36 [basic_suit_el7] Num Packages in Repos: 38045 14:18:36 [basic_suit_el7] package: ovirt-release-host-node-4.2.0-0.3.master.20170328000035.git67870d2.el7.centos.noarch from internal_repo 14:18:36 [basic_suit_el7] unresolved deps: 14:18:36 [basic_suit_el7] gdeploy -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by eyal edri [Administrator] (oVirt JIRA) 28 Mar '17

28 Mar '17

eyal edri [Administrator] created OVIRT-1281: ------------------------------------------------ Summary: Add 'patch owner' feature to Gerrit Key: OVIRT-1281 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. It might be Gerrit doesn't support such feature, but we'll check. [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[JIRA] (OVIRT-1281) Add 'patch owner' feature to Gerrit
by eyal edri [Administrator] (oVirt JIRA) 28 Mar '17

28 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1281?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1281: --------------------------------------------- Epic Link: OVIRT-403 > Add 'patch owner' feature to Gerrit > ------------------------------------ > > Key: OVIRT-1281 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1281 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Details still TBD, but we want to check if there is a way for the patch author who is the patch 'owner' or 'maintainer' and has the responsibility to make sure the patch is reviewed in time and pushed and not left behind. > It might be Gerrit doesn't support such feature, but we'll check. > [~oourfali(a)redhat.com][~ykaul][~danken] please add more info as needed. -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

Build failed in Jenkins: deploy-to-ovirt_experimental_master #14334
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/14334/disp…> ------------------------------------------ [...truncated 32.62 KB...] 2017-03-28 14:20:06,282::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,282::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,282::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,283::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,284::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,285::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,286::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,287::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,288::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,289::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,290::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,291::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,291::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,291::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,291::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,291::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,291::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,292::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,292::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,292::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,292::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,292::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,292::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,293::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,293::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,293::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,293::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,293::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,293::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,294::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,295::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,296::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,297::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,298::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,299::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,299::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,299::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,299::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,299::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,299::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,300::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,301::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,302::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,302::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,302::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,302::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,302::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,302::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,303::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,303::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,303::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,303::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,303::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,303::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,304::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,305::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,306::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,307::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,308::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,309::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,310::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,310::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,310::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,310::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,310::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,310::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,311::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,312::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,312::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,312::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,312::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,312::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,312::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,313::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if changes#detail is an iso 2017-03-28 14:20:06,314::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if https://gerrit.ovirt.org/73850 is an iso 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if api/ is an iso 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if http://jenkins-ci.org/ is an iso 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,315::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if # is an iso 2017-03-28 14:20:06,316::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,316::DEBUG::repoman.common.parser.parse:73::Checking source KojiURLSource with http://jenkins.ovirt.org/job/ovirt-vdsmfake_master_build-artifacts-el7-x86_… 2017-03-28 14:20:06,316::DEBUG::repoman.common.parser.parse:73::Checking source DirSource with http://jenkins.ovirt.org/job/ovirt-vdsmfake_master_build-artifacts-el7-x86_… 2017-03-28 14:20:06,317::DEBUG::repoman.common.stores.iso.handles_artifact:164::Checking if http://jenkins.ovirt.org/job/ovirt-vdsmfake_master_build-artifacts-el7-x86_… is an iso 2017-03-28 14:20:06,317::DEBUG::repoman.common.stores.iso.handles_artifact:170:: It is not 2017-03-28 14:20:06,317::DEBUG::repoman.common.sources.dir.expand:102::Skipping http://jenkins.ovirt.org/job/ovirt-vdsmfake_master_build-artifacts-el7-x86_… 2017-03-28 14:20:06,317::ERROR::repoman.common.parser.parse:108::No artifacts found for source http://jenkins.ovirt.org/job/ovirt-vdsmfake_master_build-artifacts-el7-x86_… Traceback (most recent call last): File "/usr/bin/repoman", line 10, in <module> sys.exit(main()) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 455, in main exit_code = do_add(args, config, repo) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 338, in do_add repo.add_source(art_src.strip()) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 153, in add_source self.parse_source_stream(sys.stdin.readlines()) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 193, in parse_source_stream self.add_source(line.strip()) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 175, in add_source artifact_paths = self.parser.parse(artifact_source) File "/usr/lib/python2.7/site-packages/repoman/common/parser.py", line 110, in parse raise Exception(msg) Exception: No artifacts found for source http://jenkins.ovirt.org/job/ovirt-vdsmfake_master_build-artifacts-el7-x86_… 2017-03-28 14:20:06,361::INFO::repoman.common.repo.cleanup:35::Cleaning up temporary dir /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpsPq_33/tmpdQYo6c/tmpS5x8hK 2017-03-28 14:20:06,361::INFO::repoman.common.repo.cleanup:35::Cleaning up temporary dir /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpsPq_33/tmpdQYo6c 2017-03-28 14:20:06,361::INFO::repoman.common.repo.cleanup:35::Cleaning up temporary dir /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpsPq_33 + rm -f /home/deploy-ovirt-experimental/experimental_repo.lock Build step 'Execute shell' marked build as failure [ssh-agent] Stopped.

1 1

[oVirt Jenkins] ovirt_3.6_he-system-tests - Build # 890 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

------=_Part_5_1265652716.1490691176007 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/890/ Build Number: 890 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #890 [Yaniv Bronhaim] Vdsm introduced abrt integration which requires additional rpms in [Sandro Bonazzola] ovirt-engine-sdk: drop fc24 on master [Sandro Bonazzola] ovirt-guest-agent: drop fc24 on master [Pavel Zhukov] Revert "Use webhooks instead of polling" [Eyal Edri] adding hyper converged storage system tests jobs ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_5_1265652716.1490691176007--

1 1

Change in barak-test[master]: Just a dummy change for testing
by review＠gerrit-staging.phx.ovirt.org 28 Mar '17

28 Mar '17

>From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. Change subject: Just a dummy change for testing ...................................................................... Patch Set 2: testing mc'testing!!! -- To view, visit https://gerrit-staging.phx.ovirt.org/4 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I5b35b72af9a40b1564792dbfcf30a82cf3f5ccb5 Gerrit-PatchSet: 2 Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

resources.ovirt.org directory layout is a mess
by Martin Sivak 28 Mar '17

28 Mar '17

Hi, I just noticed we have couple of different places for the same kind of content (packages): /pub/ - includes new releases and snapshots repos /repos/ovirt/{experimental,tested}/ - experimental seems pretty close to snapshots /releases - old releases The /repos prefix by itself is incredibly messy, there are bunch of private directories and ovirt among them. Can you please unify the structure so it is easier to navigate? We should at least have one top level dir for all official public content. Something like /ovirt/{releases,experimental,tested}/<version>/<arch> and /ovirt/yum-repos/release.rpm would work well enough I think. Thanks Martin

4 6

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation
by Shlomo Ben David (oVirt JIRA) 28 Mar '17

28 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.… ] Shlomo Ben David commented on OVIRT-1113: ----------------------------------------- [~bkorren(a)redhat.com] No, the doc isn't up to date. * From a small brief reading, the permission and the hook sections require an update. * There is a task to update the docs > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6058 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 28 Mar '17

28 Mar '17

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6058/, Build Number: 6058, Build Status: FAILURE

1 1

Change 32 [7] failed system tests
by oVirt Jenkins 28 Mar '17

28 Mar '17

Change 32 [7] is probably the reason behind recent system test failures in the "numbers" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/32/

1 0

Change 32 [7] queued for testing
by oVirt Jenkins 28 Mar '17

28 Mar '17

Change 32 [7] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/32/

1 0

Change 31 [6] passed system tests
by oVirt Jenkins 28 Mar '17

28 Mar '17

Change 31 [6] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/31/

1 0

Change 31 [6] queued for testing
by oVirt Jenkins 28 Mar '17

28 Mar '17

Change 31 [6] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/31/

1 0

Change 30 [2] passed system tests
by oVirt Jenkins 28 Mar '17

28 Mar '17

Change 30 [2] successfully passed the system tests invoked from the "numbers" queue. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/30/

1 0

Change 30 [2] queued for testing
by oVirt Jenkins 28 Mar '17

28 Mar '17

Change 30 [2] was successfully added into the "numbers" queue for testing. Further messages will be sent when test results are available. For further details about the change see: http://jenkins-staging.phx.ovirt.org/job/numbers_builder/30/

1 0

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation
by Barak Korren (oVirt JIRA) 28 Mar '17

28 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1113: ------------------------------------- Here is the existing doc about creating repos: http://ovirt-infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Pr… [~sbendavi(a)redhat.com] [~ederevea] is that doc up to date? > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation
by vishnu.srkmr (oVirt JIRA) 28 Mar '17

28 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.… ] vishnu.srkmr commented on OVIRT-1113: ------------------------------------- Can you please add the link to the documentation too? > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian JIRA (v1000.844.2#100035)

1 0

planned Jenkins restart
by Evgheni Dereveanchin 27 Mar '17

27 Mar '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1