[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5793 - FAILURE!

2017-03-12 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5793/,
Build Number: 5793,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

ovirt_4.1_he-system-tests Failed!

2017-03-12 Thread jenkins 
Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/ 
Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/37/
Build Number: 37
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #29
[Ondra Machacek] Add Ansible modules tests

[Sandro Bonazzola] pywin32-py2.7: drop fc24 on master

[Sandro Bonazzola] nsis-simple-service-plugin: drop fc24 on master

[Eyal Edri] adding job for master ansible suite


Changes for Build #30
[Ondra Machacek] Add Ansible modules tests


Changes for Build #31
[Yaniv Kaul] Remove cockpit-ovirt installation test


Changes for Build #32
[Yaniv Kaul] Remove cockpit-ovirt installation test

[Yedidyah Bar David] ovirt-wgt: Built master only on fc25

[Greg Sheremeta] ovirt-engine-phantomjs: configure jobs


Changes for Build #33
[Yaniv Kaul] Slim down the amount of packages we sync


Changes for Build #34
[Yaniv Kaul] Slim down the amount of packages we sync

[Eyal Edri] remove emails from repo closure jobs


Changes for Build #35
[Ondřej 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 #36
[Ondřej Svoboda] Add a VM with a custom MAC to the second SD.


Changes for Build #37
[Ondřej Svoboda] Add a VM with a custom MAC to the second SD.




-
Failed Tests:
-
No tests ran. 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 256

2017-03-12 Thread 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/256//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 12/03/2017
 
00 Unstable Critical
 
   
   ovirt_4.0_image-ng-system-tests
   
   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 
jenkins repo.

   
   
   
   ovirt_4.1_hc-system-tests
   
   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 
jenkins repo.


NOT STABLE YET
   
   
   
   ovirt_4.1_he-system-tests
   
   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 
jenkins repo.

   
   
   
   ovirt_4.1_image-ng-system-tests
   
   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 
jenkins repo.

   
   
   
   ovirt_master_hc-system-tests
   
   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 
jenkins repo.

   
   
   
   ovirt_master_image-ng-system-tests
   
   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 
jenkins repo.

   
   
   
   repos_4.1_check-closure_el7_merged
   
   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 
jenkins repo.

   
   
   
   repos_4.1_check-closure_fc24_merged
   
   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 
jenkins repo.

   
   
   
   repos_master_check-closure_el7_merged
   
   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 
jenkins repo.

   
   
   
   repos_master_check-closure_fc25_merged
   
   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 
jenkins repo.

   
   ___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.hotplug_nic ]

2017-03-12 Thread Dan Kenigsberg 
For the record, we have realized that this failure is unrelated to the
log supplied in bug
https://bugzilla.redhat.com/show_bug.cgi?id=1417595 .

That log is due to a test requesting dhcp address, not receiving it,
and carrying on to next tests, while a Vdsm thread is still waiting
for dhcp.

The cause for this breakage is probably a broken jsonrpc connection,
hopefully fixed by
https://gerrit.ovirt.org/#/q/Idaa54767bb7e54bf13e89887ca34fa8e01ade420

On Thu, Mar 9, 2017 at 3:06 PM, Dan Kenigsberg  wrote:
> On Thu, Mar 9, 2017 at 10:00 AM, Daniel Belenky  wrote:
>> Test failed: basic_sanity.hotplug_nic
>>
>> Link to failed job: test-repo_ovirt_experimental_4.1/917/
>>
>> Link to all logs: logs from Jenkins
>>
>> May be related to: https://bugzilla.redhat.com/show_bug.cgi?id=1417595
>>
>> Error snippet from log: (from supervdsm.log):
>>
>> ifup/VLAN100_Network::DEBUG::2017-03-08
>> 22:24:22,832::commands::93::root::(execCmd) FAILED:  = 'Running scope
>> as unit
>> ff994cde-b66d-4d54-9e36-fc253682608f.scope.\n/etc/sysconfig/network-scripts/ifup-eth:
>> line 297: 16985 Terminated  /sbin/dhclient ${DHCLIENTARGS}
>> ${DEVICE}\nCannot find device "VLAN100_Network"\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice
>> "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not
>> exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network"
>> does not exist.\n';  = 1
>> ifup/VLAN100_Network::ERROR::2017-03-08
>> 22:24:22,832::utils::371::root::(wrapper) Unhandled exception
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in
>> wrapper
>> return f(*a, **kw)
>>   File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in
>> run
>> return func(*args, **kwargs)
>>   File
>> "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line
>> 924, in _exec_ifup
>> _exec_ifup_by_name(iface.name, cgroup)
>>   File
>> "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line
>> 910, in _exec_ifup_by_name
>> raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '')
>> ConfigNetworkError: (29, 'Determining IPv6 information for
>> VLAN100_Network... failed.')
>
> Yes, this seems to be a reproduction of Vdsm bug 1417595 - hotplug_nic
> test fails in OST
>
> Eddy, can you tell how could it be that the VLAN100_NETWORK bridge
> does not exist when ifup is called?
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages

2017-03-12 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren commented on OVIRT-1250:
-

We probably shouldn't just add everyone to the oVirt org. instead we should 
probably instruct the maintainers to run 'ci test please' to confirm the PR. 
(Or add to the org of they choose to)

> Github PR builder plugin generates too many messages
> 
>
> Key: OVIRT-1250
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Pavel Zhukov
>Assignee: infra
>
> Seems like GH PR builder plugin posts one message like:
> Can one of the admins verify this patch?
> Per job which should be triggered. For example if we have 
> el7/fc25/fc24/master jobs to be triggered by Pull Request it means message 
> will appear 4 times in the GH UI which is useless and annoying. 



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

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

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

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

Until we fix this, can we replace the message with something like: You're not 
part of the oVirt organization, please request one of the oVirt infra members 
to add you to be able to send PR requests.

> Github PR builder plugin generates too many messages
> 
>
> Key: OVIRT-1250
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Pavel Zhukov
>Assignee: infra
>
> Seems like GH PR builder plugin posts one message like:
> Can one of the admins verify this patch?
> Per job which should be triggered. For example if we have 
> el7/fc25/fc24/master jobs to be triggered by Pull Request it means message 
> will appear 4 times in the GH UI which is useless and annoying. 



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

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

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

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

eyal edri [Administrator] updated OVIRT-1252:
-
Labels: standard-ci  (was: )

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



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

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

2017-03-12 Thread Barak Korren (oVirt JIRA) 
Barak Korren created OVIRT-1252:
---

 Summary: post-merge build-artifacts jobs can run out of order
 Key: OVIRT-1252
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Barak Korren
Assignee: infra


Right now build-artifacts jobs that run post merge get run on every patch and 
are allowed to run in parallel.
The end result of this is that they do not always finish in the same order in 
which the patches were merged. This ends up causing the latest build link in 
Jenkins to not always point to the real latest build. It may also means that 
packages get pushed to OST not in the right order.

To fix this we need to make sure the build-artifacts jobs do not run in 
parallel. Alternatively we could split the build artifacts job into a trigger 
job and a builder job where the trigger job gets run on every patch in parallel 
and the builder job only runs where resources are available.



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

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

2017-03-12 Thread Barak Korren (oVirt JIRA) 

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

Barak Korren updated OVIRT-1252:

Epic Link: OVIRT-400

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



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

[JIRA] (OVIRT-1251) create status.ovirt.org

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

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

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

https://cachethq.io/ looks like a cool OSS project we can use for it.

> create status.ovirt.org
> ---
>
> Key: OVIRT-1251
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> Similar to other projects:
> https://status.newrelic.com/
> https://status.centos.org/
> It should run probably using local storage so it won't get affected by a 
> storage outage.



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

[JIRA] (OVIRT-1251) create status.ovirt.org

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

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

eyal edri [Administrator] updated OVIRT-1251:
-
Epic Link: OVIRT-840

> create status.ovirt.org
> ---
>
> Key: OVIRT-1251
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> Similar to other projects:
> https://status.newrelic.com/
> https://status.centos.org/
> It should run probably using local storage so it won't get affected by a 
> storage outage.



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

[JIRA] (OVIRT-1251) create status.ovirt.org

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 
eyal edri [Administrator] created OVIRT-1251:


 Summary: create status.ovirt.org
 Key: OVIRT-1251
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251
 Project: oVirt - virtualization made easy
  Issue Type: New Feature
Reporter: eyal edri [Administrator]
Assignee: infra


Similar to other projects:
https://status.newrelic.com/
https://status.centos.org/

It should run probably using local storage so it won't get affected by a 
storage outage.



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

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

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

eyal edri [Administrator] updated OST-39:
-
Status: In Review  (was: To Do)

> Run OST against vdsm+Engine on kubernetes
> -
>
> Key: OST-39
> URL: https://ovirt-jira.atlassian.net/browse/OST-39
> Project: oVirt system tests
>  Issue Type: New Feature
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>  Labels: kubevirt
>
> Hey,
> Yaniv Bronheim is building containers for vdsm and engine.
> Lago should become capable of running OST against this setup.
> The basic flow is:
> 1. Normal CentOS
> 2. Install kubernetes
> 3. Deploy engine and vdsm pods
> The pod definitions are here:
> https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree
> https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree
> A similar script can be found here:
> https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh
> But this script is deploying kubevirt, instead of the engine + vdsm container.



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

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=28509#comment-28509
 ] 

eyal edri [Administrator] commented on OST-39:
--

still trying to move it to blocked status, please ignore for now.

> Run OST against vdsm+Engine on kubernetes
> -
>
> Key: OST-39
> URL: https://ovirt-jira.atlassian.net/browse/OST-39
> Project: oVirt system tests
>  Issue Type: New Feature
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>  Labels: kubevirt
>
> Hey,
> Yaniv Bronheim is building containers for vdsm and engine.
> Lago should become capable of running OST against this setup.
> The basic flow is:
> 1. Normal CentOS
> 2. Install kubernetes
> 3. Deploy engine and vdsm pods
> The pod definitions are here:
> https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree
> https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree
> A similar script can be found here:
> https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh
> But this script is deploying kubevirt, instead of the engine + vdsm container.



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

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes

2017-03-12 Thread eyal edri [Administrator] (oVirt JIRA) 

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

eyal edri [Administrator] updated OST-39:
-
Status: To Do  (was: In Review)

> Run OST against vdsm+Engine on kubernetes
> -
>
> Key: OST-39
> URL: https://ovirt-jira.atlassian.net/browse/OST-39
> Project: oVirt system tests
>  Issue Type: New Feature
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>  Labels: kubevirt
>
> Hey,
> Yaniv Bronheim is building containers for vdsm and engine.
> Lago should become capable of running OST against this setup.
> The basic flow is:
> 1. Normal CentOS
> 2. Install kubernetes
> 3. Deploy engine and vdsm pods
> The pod definitions are here:
> https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree
> https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree
> A similar script can be found here:
> https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh
> But this script is deploying kubevirt, instead of the engine + vdsm container.



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

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #147

2017-03-12 Thread jenkins 
See 


___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5784 - SUCCESS!

2017-03-12 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5784/,
Build Number: 5784,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra