[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4038 - SUCCESS!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4038/,
Build Number: 4038,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 152

[jenkins]

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/152//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


upstream_report.html
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4037 - FAILURE!

[jenkins]

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4037/,
Build Number: 4037,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Add ovirt-engine-4.0.6 branch to the list of stable branches

[Shlomo Ben David]

The new check_backport hook released.
Currently waiting for CR.

- The new hook will replace the old check_merged_to_previous hook.
- The new hook bypass the static configuration file.

בתאריך 28 בנוב׳ 2016 02:48 PM,‏ "Eyal Edri"  כתב:

> We are in the last step of replacing this hook with a new hook which reads
> the branch names automatically from gerrit,
> w/o the need to maintain a static conf file.
>
> Adding Shlomi who can provide more info on ETA of deployment for it.
>
> On Mon, Nov 28, 2016 at 12:03 PM, Tal Nisan  wrote:
>
>> Otherwise gerrit-hooks ignores it: (taken from gerrit.ovirt.org/67324)
>>
>> gerrit-hooks
>> Nov 25 19:19
>> ↩
>>
>> Patch Set 1:
>>
>>- Update Tracker::#1398550::IGNORE, not relevant for Red Hat
>>classification
>>- Check Bug-Url::IGNORE, not relevant for 'Red Hat' classification
>>- Check Public Bug::#1398550::OK, public bug
>>- Check Product::#1398550::IGNORE, not relevant for classification:
>>Red Hat
>>- Check TM::#1398550::IGNORE, not relevant for classification: Red Hat
>>- Set POST::#1398550::IGNORE, not relevant for Red Hat classification
>>- Check merged to previous::IGNORE, Not in stable branch
>>(['ovirt-engine-3.6', 'ovirt-engine-4.0', 'ovirt-engine-3.6.9',
>>'ovirt-engine-4.0.2', 'ovirt-engine-4.0.4'])
>>
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Seems like every user can remove Gerrit-hooks vote on stable branch

[Shlomo Ben David]

Sure,  currently I released a new patch that removes all
ovirt-engine-master-maintainers permissions from the stable branches.

The abandon permission inherited from the All-Projects and granted to all
registered users.

בתאריך 28 בנוב׳ 2016 04:16 PM,‏ "Eyal Edri"  כתב:

> I'm not sure every user has this right, but we need to re-verify the list
> of stable branch maintainers to be correct.
> Shlomi - can you work with Tal to make sure the lists are updated for vdsm
> + engine ?
>
> On Mon, Nov 28, 2016 at 12:02 PM, Tal Nisan  wrote:
>
>> This is wrong, please revert it to how it was before when only stable
>> branch maintainers could remove it
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-877) [gerrit hooks] remove unused hooks

[Shlomo Ben David (oVirt JIRA)]

Shlomo Ben David created OVIRT-877:
--

 Summary: [gerrit hooks] remove unused hooks
 Key: OVIRT-877
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-877
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Shlomo Ben David
Assignee: infra


Remove all the unused hooks



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

[JIRA] (OVIRT-877) [gerrit hooks] remove unused hooks

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David updated OVIRT-877:
---
Epic Link: OVIRT-403

> [gerrit hooks] remove unused hooks
> --
>
> Key: OVIRT-877
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-877
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: infra
>
> Remove all the unused hooks



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

[JIRA] (OVIRT-877) [gerrit hooks] remove unused hooks

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David reassigned OVIRT-877:
--

Assignee: Shlomo Ben David  (was: infra)

> [gerrit hooks] remove unused hooks
> --
>
> Key: OVIRT-877
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-877
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: Shlomo Ben David
>
> Remove all the unused hooks



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

[JIRA] (OVIRT-876) create check_backport hook

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David updated OVIRT-876:
---
Epic Link: OVIRT-403

> create check_backport hook
> --
>
> Key: OVIRT-876
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Shlomo Ben David
>Assignee: infra
>
> The new hook should replace the old
> patchset-created.warn_if_not_merged_to_previous_branch
> - It should check that the current patch has been backported to all newer 
> branches
>   that are relevant for the patch.
> - It should bypass the use of the configuration file params (STABLE_BRANCH)
>   
>  



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

[JIRA] (OVIRT-876) create check_backport hook

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David updated OVIRT-876:
---
Issue Type: Task  (was: Improvement)

> create check_backport hook
> --
>
> Key: OVIRT-876
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: infra
>
> The new hook should replace the old
> patchset-created.warn_if_not_merged_to_previous_branch
> - It should check that the current patch has been backported to all newer 
> branches
>   that are relevant for the patch.
> - It should bypass the use of the configuration file params (STABLE_BRANCH)
>   
>  



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

[JIRA] (OVIRT-876) create check_backport hook

[Shlomo Ben David (oVirt JIRA)]

Shlomo Ben David created OVIRT-876:
--

 Summary: create check_backport hook
 Key: OVIRT-876
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Shlomo Ben David
Assignee: infra


The new hook should replace the old
patchset-created.warn_if_not_merged_to_previous_branch
- It should check that the current patch has been backported to all newer 
branches
  that are relevant for the patch.
- It should bypass the use of the configuration file params (STABLE_BRANCH)

   



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

[JIRA] (OVIRT-876) create check_backport hook

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David reassigned OVIRT-876:
--

Assignee: Shlomo Ben David  (was: infra)

> create check_backport hook
> --
>
> Key: OVIRT-876
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-876
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: Shlomo Ben David
>
> The new hook should replace the old
> patchset-created.warn_if_not_merged_to_previous_branch
> - It should check that the current patch has been backported to all newer 
> branches
>   that are relevant for the patch.
> - It should bypass the use of the configuration file params (STABLE_BRANCH)
>   
>  



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

[JIRA] (OVIRT-875) Build oVirt 4.0.6 RC3

[sbonazzo (oVirt JIRA)]

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

sbonazzo updated OVIRT-875:
---
Assignee: sbonazzo  (was: infra)
  Status: In Progress  (was: To Do)

> Build oVirt 4.0.6 RC3
> -
>
> Key: OVIRT-875
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-875
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: sbonazzo
>Priority: Highest
>




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

[JIRA] (OVIRT-875) Build oVirt 4.0.6 RC3

[sbonazzo (oVirt JIRA)]

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

sbonazzo updated OVIRT-875:
---
Epic Link: OVIRT-411

> Build oVirt 4.0.6 RC3
> -
>
> Key: OVIRT-875
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-875
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>Priority: Highest
>




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

[JIRA] (OVIRT-875) Build oVirt 4.0.6 RC3

[sbonazzo (oVirt JIRA)]

sbonazzo created OVIRT-875:
--

 Summary: Build oVirt 4.0.6 RC3
 Key: OVIRT-875
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-875
 Project: oVirt - virtualization made easy
  Issue Type: Task
  Components: Repositories Mgmt
Reporter: sbonazzo
Assignee: infra
Priority: Highest






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

oVirt 4.0.6 RC3 merge / branch / tag / bugzilla reminder

[Sandro Bonazzola]

All stable branch maintainers, please make sure to
merge all relevant open bugs until Wednesday morning 11:00 AM TLV time
(10:00 AM CET).

For each package that need to be built (i.e oVirt product) please make sure
every bug in MODIFIED has the right Target Release and Target Milestone.
A Target release should state the version of the package you're building
and should include the same version you used for the tag you just used for
this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.6, tr: 4.0.6)
A list of bugs that require attention is here:
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.6%20target_release%3A---%20status%3Amodified%2Cpost

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Seems like every user can remove Gerrit-hooks vote on stable branch

[Eyal Edri]

I'm not sure every user has this right, but we need to re-verify the list
of stable branch maintainers to be correct.
Shlomi - can you work with Tal to make sure the lists are updated for vdsm
+ engine ?

On Mon, Nov 28, 2016 at 12:02 PM, Tal Nisan  wrote:

> This is wrong, please revert it to how it was before when only stable
> branch maintainers could remove it
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin commented on OVIRT-867:


I think this may bring unwanted overhead and eventually even more serious 
consistency issues than when using the mirrorlist from upstream providers. For 
now I'd go with a plain squid+mirrorlist (or predefined list of three fastest 
mirrors) defined for jobs that currently use repoproxy.

> Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still 
> Failing!
> 
>
> Key: OVIRT-867
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> *00:01:53.955* Can't download or revert repomd.xml for
> check-epel-el7*00:01:53.955* Some dependencies may not be complete for
> this repository*00:01:53.956* Run as root to get all dependencies or
> use -t to enable a user temp cache
> Can you check? looks like it's not possible to update local cache of metadata.
> On Fri, Nov 25, 2016 at 1:07 PM,  wrote:
> > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/
> > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/
> > Build Number: 92
> > Build Status:  Still Failing
> > Triggered By: Started by user Sandro Bonazzola
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #89
> > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well
> >
> > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead
> > of snapshot
> >
> >
> > Changes for Build #90
> > No changes
> >
> > Changes for Build #91
> > No changes
> >
> > Changes for Build #92
> > No changes
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

Re: Add ovirt-engine-4.0.6 branch to the list of stable branches

[Eyal Edri]

We are in the last step of replacing this hook with a new hook which reads
the branch names automatically from gerrit,
w/o the need to maintain a static conf file.

Adding Shlomi who can provide more info on ETA of deployment for it.

On Mon, Nov 28, 2016 at 12:03 PM, Tal Nisan  wrote:

> Otherwise gerrit-hooks ignores it: (taken from gerrit.ovirt.org/67324)
>
> gerrit-hooks
> Nov 25 19:19
> ↩
>
> Patch Set 1:
>
>- Update Tracker::#1398550::IGNORE, not relevant for Red Hat
>classification
>- Check Bug-Url::IGNORE, not relevant for 'Red Hat' classification
>- Check Public Bug::#1398550::OK, public bug
>- Check Product::#1398550::IGNORE, not relevant for classification:
>Red Hat
>- Check TM::#1398550::IGNORE, not relevant for classification: Red Hat
>- Set POST::#1398550::IGNORE, not relevant for Red Hat classification
>- Check merged to previous::IGNORE, Not in stable branch
>(['ovirt-engine-3.6', 'ovirt-engine-4.0', 'ovirt-engine-3.6.9',
>'ovirt-engine-4.0.2', 'ovirt-engine-4.0.4'])
>
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-867:
-

I guess our only way to avoid mirroring broken repos is to use Pulp or Katello?

> Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still 
> Failing!
> 
>
> Key: OVIRT-867
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> *00:01:53.955* Can't download or revert repomd.xml for
> check-epel-el7*00:01:53.955* Some dependencies may not be complete for
> this repository*00:01:53.956* Run as root to get all dependencies or
> use -t to enable a user temp cache
> Can you check? looks like it's not possible to update local cache of metadata.
> On Fri, Nov 25, 2016 at 1:07 PM,  wrote:
> > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/
> > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/
> > Build Number: 92
> > Build Status:  Still Failing
> > Triggered By: Started by user Sandro Bonazzola
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #89
> > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well
> >
> > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead
> > of snapshot
> >
> >
> > Changes for Build #90
> > No changes
> >
> > Changes for Build #91
> > No changes
> >
> > Changes for Build #92
> > No changes
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin commented on OVIRT-867:


Eyal, this is a valid option, and even for the job in question we'd need to 
mirror the following repos:

CENTOS_MIRROR="http://centos.mirror.constant.com/;
EPEL_MIRROR="http://mirror.switch.ch/ftp/mirror;
FEDORA_MIRROR="http://mirrors.kernel.org/;
GLUSTER_MIRROR="http://download.gluster.org;
JPACKAGE_MIRROR="http://vesta.informatik.rwth-aachen.de/ftp/pub/comp/Linux/;
COPR="http://copr-be.cloud.fedoraproject.org/results;

So it's at least CentOS, Fedora (2-3 releases), EPEL, Gluster and jpackage. 
We'd need to maange all of these and if upstream produces a corrupted repo this 
will still be mirrored. I think 1TB of disk should be enough for this (I 
managed a Fedora+CentOS+EPEL mirror without ISOs and that was usually enough).

> Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still 
> Failing!
> 
>
> Key: OVIRT-867
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> *00:01:53.955* Can't download or revert repomd.xml for
> check-epel-el7*00:01:53.955* Some dependencies may not be complete for
> this repository*00:01:53.956* Run as root to get all dependencies or
> use -t to enable a user temp cache
> Can you check? looks like it's not possible to update local cache of metadata.
> On Fri, Nov 25, 2016 at 1:07 PM,  wrote:
> > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/
> > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/
> > Build Number: 92
> > Build Status:  Still Failing
> > Triggered By: Started by user Sandro Bonazzola
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #89
> > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well
> >
> > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead
> > of snapshot
> >
> >
> > Changes for Build #90
> > No changes
> >
> > Changes for Build #91
> > No changes
> >
> > Changes for Build #92
> > No changes
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-867:
--

Assignee: Evgheni Dereveanchin  (was: infra)

> Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still 
> Failing!
> 
>
> Key: OVIRT-867
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> *00:01:53.955* Can't download or revert repomd.xml for
> check-epel-el7*00:01:53.955* Some dependencies may not be complete for
> this repository*00:01:53.956* Run as root to get all dependencies or
> use -t to enable a user temp cache
> Can you check? looks like it's not possible to update local cache of metadata.
> On Fri, Nov 25, 2016 at 1:07 PM,  wrote:
> > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/
> > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/
> > Build Number: 92
> > Build Status:  Still Failing
> > Triggered By: Started by user Sandro Bonazzola
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #89
> > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well
> >
> > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead
> > of snapshot
> >
> >
> > Changes for Build #90
> > No changes
> >
> > Changes for Build #91
> > No changes
> >
> > Changes for Build #92
> > No changes
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



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

Re: Build failed in Jenkins: ovirt_3.6_he-system-tests #727

[Sandro Bonazzola]

On Mon, Nov 28, 2016 at 9:55 AM, Eyal Edri  wrote:

> I see the issue got fixed, any fixes merged for it to work?
>
>
Nothing I'm aware of.




> On Fri, Nov 25, 2016 at 2:12 PM, Sandro Bonazzola 
> wrote:
>
>> looks like a repository issue:
>>
>> Error: Package: 7:lvm2-2.02.166-1.el7_3.1.x86_64 (alocalsync)
>>Requires: device-mapper-persistent-data >= 0.6.3-1
>>Available: device-mapper-persistent-data-0.5.5-1.el7.x86_64 
>> (alocalsync)
>>device-mapper-persistent-data = 0.5.5-1.el7
>>
>>
>> On Fri, Nov 25, 2016 at 1:00 PM,  wrote:
>>
>>> See 
>>>
>>> Changes:
>>>
>>> [Eyal Edri] adding missing python-simplejson to epel repo
>>>
>>> --
>>> [...truncated 669 lines...]
>>> ##  took 373 seconds
>>> ##  rc = 1
>>> ##
>>> ##! ERROR v
>>> ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.
>>> he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log
>>> ##!
>>> + env_cleanup
>>> + echo '#'
>>> #
>>> + local res=0
>>> + local uuid
>>> + echo ' Cleaning up'
>>>  Cleaning up
>>> + [[ -e >> virt-system-tests/deployment-he-basic-suite-3.6> ]]
>>> + echo '--- Cleaning with lago'
>>> --- Cleaning with lago
>>> + lago --workdir >> ovirt_3.6_he-system-tests/ws/ovirt-system-tests/deployment-h
>>> e-basic-suite-3.6> destroy --yes --all-prefixes
>>> + echo '--- Cleaning with lago done'
>>> --- Cleaning with lago done
>>> + [[ 0 != \0 ]]
>>> + echo ' Cleanup done'
>>>  Cleanup done
>>> + exit 0
>>> + exit
>>> Took 233 seconds
>>> ===
>>> ##!
>>> ##! ERROR ^^
>>> ##!
>>> ##
>>> Build step 'Execute shell' marked build as failure
>>> Performing Post build task...
>>> Match found for :.* : True
>>> Logical operation result is TRUE
>>> Running script  : #!/bin/bash -xe
>>> echo 'shell_scripts/system_tests.collect_logs.sh'
>>>
>>> #
>>> # Required jjb vars:
>>> #version
>>> #
>>> VERSION=3.6
>>> SUITE_TYPE=
>>>
>>> WORKSPACE="$PWD"
>>> OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
>>> TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"
>>>
>>> rm -rf "$WORKSPACE/exported-artifacts"
>>> mkdir -p "$WORKSPACE/exported-artifacts"
>>>
>>> if [[ -d "$TESTS_LOGS" ]]; then
>>> mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
>>> fi
>>>
>>> [ovirt_3.6_he-system-tests] $ /bin/bash -xe
>>> /tmp/hudson4759223563830264904.sh
>>> + echo shell_scripts/system_tests.collect_logs.sh
>>> shell_scripts/system_tests.collect_logs.sh
>>> + VERSION=3.6
>>> + SUITE_TYPE=
>>> + WORKSPACE=
>>> + OVIRT_SUITE=3.6
>>> + TESTS_LOGS=>> -tests/ws/ovirt-system-tests/exported-artifacts>
>>> + rm -rf >> artifact/exported-artifacts>
>>> + mkdir -p >> artifact/exported-artifacts>
>>> + [[ -d >> virt-system-tests/exported-artifacts> ]]
>>> + mv >> virt-system-tests/exported-artifacts/lago_logs> <
>>> http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/727/
>>> artifact/exported-artifacts/>
>>> POST BUILD TASK : SUCCESS
>>> END OF POST BUILD TASK : 0
>>> Match found for :.* : True
>>> Logical operation result is TRUE
>>> Running script  : #!/bin/bash -xe
>>> echo "shell-scripts/mock_cleanup.sh"
>>>
>>> shopt -s nullglob
>>>
>>>
>>> WORKSPACE="$PWD"
>>>
>>> # Make clear this is the cleanup, helps reading the jenkins logs
>>> cat <>> ___
>>> ###
>>> # #
>>> #   CLEANUP   #
>>> # #
>>> ###
>>> EOC
>>>
>>>
>>> # Archive the logs, we want them anyway
>>> logs=(
>>> ./*log
>>> ./*/logs
>>> )
>>>
>>> if [[ "$logs" ]]; then
>>> for log in "${logs[@]}"
>>> do
>>> echo "Copying ${log} to exported-artifacts"
>>> mv $log exported-artifacts/
>>> done
>>> fi
>>>
>>> # stop any processes running 

Re: [JIRA] (OVIRT-874) Move github project to gerrit

[Eyal Edri]

this might work for small or independent projects,  not for something that
is integrated with ovirt like user portal.

we don't have Gerrit hooks for github and many of existing ci flows are
available only for Gerrit.

we can consider testing the github plugin for Gerrit to see if its possible
to get pull requests into Gerrit from githib,  but its not high priority
for now and will need to wait for checking.

On Nov 28, 2016 12:02, "eyal edri [Administrator] (oVirt JIRA)" <
j...@ovirt-jira.atlassian.net> wrote:


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

eyal edri [Administrator] reassigned OVIRT-874:
---

Assignee: Shlomo Ben David  (was: infra)

Can you please help with this ?
Lets make sure adding a new project has the new permisisons for all
projects we have and its mirrored to GitHub

> Move github project to gerrit
> -
>
> Key: OVIRT-874
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-874
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Marek Libra
>Assignee: Shlomo Ben David
>
> Hi,
> please move following github project
> https://github.com/mareklibra/userportal
> to gerrit as 'ovirt-web-ui' project.
> Please keep git history.
> What is needed for automatic read-only syncing the gerrit back to the
github?
> Thanks,
> Marek



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

Add ovirt-engine-4.0.6 branch to the list of stable branches

[Tal Nisan]

Otherwise gerrit-hooks ignores it: (taken from gerrit.ovirt.org/67324)

gerrit-hooks
Nov 25 19:19
↩

Patch Set 1:

   - Update Tracker::#1398550::IGNORE, not relevant for Red Hat
   classification
   - Check Bug-Url::IGNORE, not relevant for 'Red Hat' classification
   - Check Public Bug::#1398550::OK, public bug
   - Check Product::#1398550::IGNORE, not relevant for classification: Red
   Hat
   - Check TM::#1398550::IGNORE, not relevant for classification: Red Hat
   - Set POST::#1398550::IGNORE, not relevant for Red Hat classification
   - Check merged to previous::IGNORE, Not in stable branch
   (['ovirt-engine-3.6', 'ovirt-engine-4.0', 'ovirt-engine-3.6.9',
   'ovirt-engine-4.0.2', 'ovirt-engine-4.0.4'])
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Seems like every user can remove Gerrit-hooks vote on stable branch

[Tal Nisan]

This is wrong, please revert it to how it was before when only stable
branch maintainers could remove it
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-874) Move github project to gerrit

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] reassigned OVIRT-874:
---

Assignee: Shlomo Ben David  (was: infra)

Can you please help with this ?
Lets make sure adding a new project has the new permisisons for all projects we 
have and its mirrored to GitHub

> Move github project to gerrit
> -
>
> Key: OVIRT-874
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-874
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Marek Libra
>Assignee: Shlomo Ben David
>
> Hi,
> please move following github project
> https://github.com/mareklibra/userportal
> to gerrit as 'ovirt-web-ui' project.
> Please keep git history.
> What is needed for automatic read-only syncing the gerrit back to the github?
> Thanks,
> Marek



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

[JIRA] (OVIRT-874) Move github project to gerrit

[Marek Libra (oVirt JIRA)]

Marek Libra created OVIRT-874:
-

 Summary: Move github project to gerrit
 Key: OVIRT-874
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-874
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Marek Libra
Assignee: infra


Hi,

please move following github project
https://github.com/mareklibra/userportal

to gerrit as 'ovirt-web-ui' project.

Please keep git history.

What is needed for automatic read-only syncing the gerrit back to the github?

Thanks,
Marek



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

[JIRA] (OVIRT-758) Vdsm docker testing images

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-758:

Assignee: eyal edri [Administrator]  (was: infra)
  Status: In Progress  (was: To Do)

> Vdsm docker testing images
> --
>
> Key: OVIRT-758
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: eyal edri [Administrator]
>
> Hi all,
> Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images.
> See 
> https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:dockerfile
> Currently I maintain the images in docker hub:
> - https://hub.docker.com/r/nirs/vdsm-centos/
> - https://hub.docker.com/r/nirs/vdsm-fedora/
> I configured automatic build, so each time I push a change to this branch:
> https://github.com/nirs/vdsm/tree/dockerfile
> Docker go and rebuilds the images.
> We want to move the images to docker hub ovirt account:
> https://hub.docker.com/u/ovirt/
> And configure vdsm github project so docker will rebuild
> the images when we push a changes to the dockerfile branch,
> or another solution to allow easy update of the images by
> merging a new dockerfile.
> Nir



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

[JIRA] (OVIRT-758) Vdsm docker testing images

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-758:
-

I created a new organization for oVirt under:
https://hub.docker.com/u/ovirtinfra/
(ovirt wasn't available) 

please let me know which permissions do you need to create the VDSM images 
repos under it.

> Vdsm docker testing images
> --
>
> Key: OVIRT-758
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-758
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> Hi all,
> Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images.
> See 
> https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:dockerfile
> Currently I maintain the images in docker hub:
> - https://hub.docker.com/r/nirs/vdsm-centos/
> - https://hub.docker.com/r/nirs/vdsm-fedora/
> I configured automatic build, so each time I push a change to this branch:
> https://github.com/nirs/vdsm/tree/dockerfile
> Docker go and rebuilds the images.
> We want to move the images to docker hub ovirt account:
> https://hub.docker.com/u/ovirt/
> And configure vdsm github project so docker will rebuild
> the images when we push a changes to the dockerfile branch,
> or another solution to allow easy update of the images by
> merging a new dockerfile.
> Nir



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

[JIRA] (OVIRT-712) Use repoman extra sources feature in VDSM check merge

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] reassigned OVIRT-712:
---

Assignee: Nadav Goldin  (was: infra)

Nadav, I think this is what you're doing now on the check-merged job right?

> Use repoman extra sources feature in VDSM check merge 
> --
>
> Key: OVIRT-712
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-712
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Gal Ben Haim
>Assignee: Nadav Goldin
>
> When running check merge, new rpms with the latest patch are being generated.
> currently those repos are being copied by reposync to /var/lib/lago/reposync.
> Those rpms shouldn't be saved to the cache, thus we need to use repoman to 
> include those rpms in the internal repo. 



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

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-95:


we'll implement this as part of #OVIRT-567, 
as second step for upgrading hypervisors after engine upgrade. 

> [jenkins] add job to run upgrade vdsm from version X to version Y
> -
>
> Key: OVIRT-95
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Jenkins
>Affects Versions: Test
>Reporter: eyal edri [Administrator]
>Assignee: infra
>Priority: Lowest
>  Labels: infra,vdsm,jenkins
>
> vdsm upgrade should be tested. (following on bug that was found).
> suggested flow:
> 1. install vdsm version X (e.g from 3.2)
> 2. build latest vdsm version (3.3 or master) 
> 3. yum update vdsm 
> 4. check if service is up and running.



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

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-95:
---
Resolution: Duplicate
Status: Done  (was: To Do)

> [jenkins] add job to run upgrade vdsm from version X to version Y
> -
>
> Key: OVIRT-95
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Jenkins
>Affects Versions: Test
>Reporter: eyal edri [Administrator]
>Assignee: infra
>Priority: Lowest
>  Labels: infra,vdsm,jenkins
>
> vdsm upgrade should be tested. (following on bug that was found).
> suggested flow:
> 1. install vdsm version X (e.g from 3.2)
> 2. build latest vdsm version (3.3 or master) 
> 3. yum update vdsm 
> 4. check if service is up and running.



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

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-753:
-

[~fdeutsch] this job is still not working, is it using the new experimental 
rpms? 

Anything infra team can help with?

> ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
> -
>
> Key: OVIRT-753
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> In:
> http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/196/console
> After appliance shutdown:
> *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~
> --in-place ]] && ( virt-sparsify --in-place
> ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2
> ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify:
> error: libguestfs error: guestfs_launch failed.*00:25:53.735* This
> usually means the libguestfs appliance failed to start or
> crashed.*00:25:53.735* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735*
> or run 'libguestfs-test-tool' and post the *complete* output into
> a*00:25:53.735* bug report or message to the libguestfs mailing list.
> The job should have failed here. Instead, the job continues and fails in a
> later stage:
> *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G
> -rwxr-xr-x. 1 root root 1.4G Oct  6 14:13
> ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance
> done*00:33:01.290* all appliance done*00:33:01.291* + make
> check*00:33:01.299* make -f image-tools/build.mk
> ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering
> directory 
> `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305*
> guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort
> -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs:
> error: appliance closed the connection unexpectedly.*00:41:58.044*
> This usually means the libguestfs appliance crashed.*00:41:58.044* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045*
> for information about how to debug libguestfs and report
> bugs.*00:41:58.045* libguestfs: error: guestfs_launch
> failed.*00:41:58.045* This usually means the libguestfs appliance
> failed to start or crashed.*00:41:58.045* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046*
> or run 'libguestfs-test-tool' and post the *complete* output into
> a*00:41:58.046* bug report or message to the libguestfs mailing
> list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm]
> Error 1*00:41:58.059* make[1]: Leaving directory
> `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060*
> make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065*
> Took 2325 seconds
> wasting 20 minutes of jenkins slave time testing something already known
> broken.
> While working on fixing this job, please investigate while it's failing and
> open a separate issue or bugzilla for it.
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

Re: Build failed in Jenkins: ovirt_3.6_he-system-tests #727

[Eyal Edri]

I see the issue got fixed, any fixes merged for it to work?

On Fri, Nov 25, 2016 at 2:12 PM, Sandro Bonazzola 
wrote:

> looks like a repository issue:
>
> Error: Package: 7:lvm2-2.02.166-1.el7_3.1.x86_64 (alocalsync)
>Requires: device-mapper-persistent-data >= 0.6.3-1
>Available: device-mapper-persistent-data-0.5.5-1.el7.x86_64 
> (alocalsync)
>device-mapper-persistent-data = 0.5.5-1.el7
>
>
> On Fri, Nov 25, 2016 at 1:00 PM,  wrote:
>
>> See 
>>
>> Changes:
>>
>> [Eyal Edri] adding missing python-simplejson to epel repo
>>
>> --
>> [...truncated 669 lines...]
>> ##  took 373 seconds
>> ##  rc = 1
>> ##
>> ##! ERROR v
>> ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.
>> he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log
>> ##!
>> + env_cleanup
>> + echo '#'
>> #
>> + local res=0
>> + local uuid
>> + echo ' Cleaning up'
>>  Cleaning up
>> + [[ -e > virt-system-tests/deployment-he-basic-suite-3.6> ]]
>> + echo '--- Cleaning with lago'
>> --- Cleaning with lago
>> + lago --workdir > ovirt_3.6_he-system-tests/ws/ovirt-system-tests/deployment-h
>> e-basic-suite-3.6> destroy --yes --all-prefixes
>> + echo '--- Cleaning with lago done'
>> --- Cleaning with lago done
>> + [[ 0 != \0 ]]
>> + echo ' Cleanup done'
>>  Cleanup done
>> + exit 0
>> + exit
>> Took 233 seconds
>> ===
>> ##!
>> ##! ERROR ^^
>> ##!
>> ##
>> Build step 'Execute shell' marked build as failure
>> Performing Post build task...
>> Match found for :.* : True
>> Logical operation result is TRUE
>> Running script  : #!/bin/bash -xe
>> echo 'shell_scripts/system_tests.collect_logs.sh'
>>
>> #
>> # Required jjb vars:
>> #version
>> #
>> VERSION=3.6
>> SUITE_TYPE=
>>
>> WORKSPACE="$PWD"
>> OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
>> TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"
>>
>> rm -rf "$WORKSPACE/exported-artifacts"
>> mkdir -p "$WORKSPACE/exported-artifacts"
>>
>> if [[ -d "$TESTS_LOGS" ]]; then
>> mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
>> fi
>>
>> [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson4759223563830264904
>> .sh
>> + echo shell_scripts/system_tests.collect_logs.sh
>> shell_scripts/system_tests.collect_logs.sh
>> + VERSION=3.6
>> + SUITE_TYPE=
>> + WORKSPACE=
>> + OVIRT_SUITE=3.6
>> + TESTS_LOGS=> -tests/ws/ovirt-system-tests/exported-artifacts>
>> + rm -rf > artifact/exported-artifacts>
>> + mkdir -p > artifact/exported-artifacts>
>> + [[ -d > virt-system-tests/exported-artifacts> ]]
>> + mv > virt-system-tests/exported-artifacts/lago_logs> <
>> http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/727/
>> artifact/exported-artifacts/>
>> POST BUILD TASK : SUCCESS
>> END OF POST BUILD TASK : 0
>> Match found for :.* : True
>> Logical operation result is TRUE
>> Running script  : #!/bin/bash -xe
>> echo "shell-scripts/mock_cleanup.sh"
>>
>> shopt -s nullglob
>>
>>
>> WORKSPACE="$PWD"
>>
>> # Make clear this is the cleanup, helps reading the jenkins logs
>> cat <> ___
>> ###
>> # #
>> #   CLEANUP   #
>> # #
>> ###
>> EOC
>>
>>
>> # Archive the logs, we want them anyway
>> logs=(
>> ./*log
>> ./*/logs
>> )
>>
>> if [[ "$logs" ]]; then
>> for log in "${logs[@]}"
>> do
>> echo "Copying ${log} to exported-artifacts"
>> mv $log exported-artifacts/
>> done
>> fi
>>
>> # stop any processes running inside the chroot
>> failed=false
>> mock_confs=("$WORKSPACE"/*/mocker*)
>> # Clean current jobs mockroot if any
>> for mock_conf_file in "${mock_confs[@]}"; do
>> [[ "$mock_conf_file" ]] || continue
>> echo "Cleaning up mock 

[JIRA] (OVIRT-869) Investigate proxy errors from proxy.phx.ovirt.org

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] reassigned OVIRT-869:
---

Assignee: Evgheni Dereveanchin  (was: infra)

First priority should be fixing the DNS errors we see,
second is to reinstall the service as Squid as we talked before and stop using 
the custom python script we have now.

> Investigate proxy errors from proxy.phx.ovirt.org
> -
>
> Key: OVIRT-869
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-869
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eyal edri [Administrator]
>Assignee: Evgheni Dereveanchin
>Priority: Highest
>
> We need to make sure jobs don't fail on proxy like [1].
> Either use original repos if proxy is down or add watchdog / alerts for the 
> proxy service.
> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3693/artifact/exported-artifacts/basic_suite_master.sh-el7/logs/mocker-epel-7-x86_64.el7.init/root.log



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

[JIRA] (OVIRT-848) Add support for building containers in oVirt CI

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-848:


Some details and considerations about the interaction between containers 
(specifically Docker-based) and "Standard CI":

There are two possible ways to use Docker from inside mock:
# Install Docker inside the mock environment, and start up the Docker daemon 
inside it as well.
# Install Docker on the slave VM (The host under mock), Docker client in the 
mock env, and bind-mount the docket socket ({{/var/run/docker.sock}}) into it.

The obvious benefit of method #1 is that it does not require any adjustments to 
the existing CI infrastructure (We just need to teach devs how to implement 
it). I have doubts, however, that mock will not cause some difficulties with 
this (For example, are cgroups mounted inside mock?). We will need to test this 
and verify it works.

Method #1 will also cause issues when we come around to implementing something 
like OVIRT-873 ([Nested Docker is possible but far from 
recommneded|https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/])
 or do anything that causes us to run Docker on the hosts themselves.

Method #2 will not have the same issues as method #1, but it will require us to 
distribute and maintain Docker on the slaves which is a step back to the 
pre-Standard-CI era.

I think we should actually implement _both_ methods like this:
# Try to mount the Docker socket into the mock env.
# If it works use method #2
# If it doesn't, use method #1.

This will require a little change to {{mock_runner.sh}} to allow bind mounts to 
be optional, but this change may provide other benefits so we may as well go 
for it.

> Add support for building containers in oVirt CI
> ---
>
> Key: OVIRT-848
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-848
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> more and more projects in oVirt are starting to build containers and using 
> Docker files in their reops.
> We need to start preparing oVirt CI to know how to handle containers and 
> support containers the same way we support rpms today.
> This will be a parent task with multiple sub-tasks that will follow, the 
> following is a draft list of what we might need to do to add this support:
> # Install Registry server ( maybe use openshift.ovirt.org ) 
> # Add for standard CI 'build-containers.sh' support 
> # Add verification steps for the build before publishing to registry
> # Look at 3rd party OSS projects that might help and integrate with existing 
> solutions



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

[JIRA] (OVIRT-873) Implement Standard-CI with containers

[Nadav Goldin (oVirt JIRA)]

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

Nadav Goldin commented on OVIRT-873:


+1 - I think containers support would be great, especially if we use openshift. 

Few issues that come to mind from my little experience with docker:
1. docker has limitation, for example: running systemd is almost impossible, 
also I doubt if you can run qemu inside docker, so this is not relevant for 
OST. 
2. docker wants one process per container(as for the guidelines), I think we 
have jobs that need to do more than that.
3. docker images are not always one-to-one with the images we want to test on, 
i.e. can we claim that centos7:latest on docker hub is equivalent to centos7 we 
"support"? not sure. Moreover, this means we will need to start maintaining 
images, what we don't do now(in a way we maintain mock configurations which 
might be considered as maintaining Dockerfiles).

either way, every solution we go with would probably need to be hybrid 
one(maintaining both flows). 

> Implement Standard-CI with containers
> -
>
> Key: OVIRT-873
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: General
>Reporter: Barak Korren
>Assignee: infra
>
> oVirt's Standard-CI is currently implemented using mock, and this has worked 
> well for us so far.
> Changing the implementation to use containers will provide several benefits:
> * Faster start-up times - Most container provides have some form of image 
> layering and caching that will be faster as bringing up a basic OS image then 
> installing it with yum like mock does.
> * Broader OS support - mock can only run on the Red Hat family of operating 
> systems, and can only emulate those operating systems. Most container 
> providers can both run on and emulate a broader range of operating systems.
> * Better isolation and cleanup - Mock only isolates the file system, 
> containers can isolate the file system as well as the networking layer and 
> the process space.
> Depending on the container provider, we may gain additional benefits:
> * Some container providers like Kubernetes, can manage distributed compute 
> resources across many nodes. This means can can stop managing Jenkins slaves 
> and instead just have the Jenkins master start up containers on the provider.
> * Some providers like OpenShift have built-in CI processes for creating and 
> testing container images.
> *Note:* At some point, David started an effort going this way: 
> https://gerrit.ovirt.org/#/c/54376/



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

[JIRA] (OVIRT-873) Implement Standard-CI with containers

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-873:
-

I think its the right way going forward as version 2.0 of the standard CI.
At some point we considered moving to stateless slaves instead mock , but I 
think this approach might prove to be better, because of the advantages of less 
maintenance of keeping various VMs with multiple operating systems + the 
overhead of ensuring the stateless mechanism works. 

Worth also looking into fabric8.io, it has integration with Kubernetes & 
OpenShift already. 



more info @ https://fabric8.io/articles/index.html

> Implement Standard-CI with containers
> -
>
> Key: OVIRT-873
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: General
>Reporter: Barak Korren
>Assignee: infra
>
> oVirt's Standard-CI is currently implemented using mock, and this has worked 
> well for us so far.
> Changing the implementation to use containers will provide several benefits:
> * Faster start-up times - Most container provides have some form of image 
> layering and caching that will be faster as bringing up a basic OS image then 
> installing it with yum like mock does.
> * Broader OS support - mock can only run on the Red Hat family of operating 
> systems, and can only emulate those operating systems. Most container 
> providers can both run on and emulate a broader range of operating systems.
> * Better isolation and cleanup - Mock only isolates the file system, 
> containers can isolate the file system as well as the networking layer and 
> the process space.
> Depending on the container provider, we may gain additional benefits:
> * Some container providers like Kubernetes, can manage distributed compute 
> resources across many nodes. This means can can stop managing Jenkins slaves 
> and instead just have the Jenkins master start up containers on the provider.
> * Some providers like OpenShift have built-in CI processes for creating and 
> testing container images.
> *Note:* At some point, David started an effort going this way: 
> https://gerrit.ovirt.org/#/c/54376/



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