[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1517994329-10691-188
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1880:
-----------------------------------
Summary: Manage bare metals with beaker
Key: OVIRT-1880
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Jenkins Slaves
Reporter: Barak Korren
Assignee: infra
There are multiple reasons why we may want to manage our bare-metal slaves with beaker:
* It will allow us to have auto-reprovisioning for them, perhaps even after every job
* It will allow us to scale up to multiple jenkins masters while sharing host resources
* If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)
------------=_1517994329-10691-188
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1880:</h3>
<pre> Summary: Manage bare metals with beaker
Key: OVIRT-1880
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Jenkins Slaves
Reporter: Barak Korren
Assignee: infra</pre>
<p>There are multiple reasons why we may want to manage our bare-metal slaves with beaker:</p>
<ul><li><p>It will allow us to have auto-reprovisioning for them, perhaps even after every job</p></li>
<li><p>It will allow us to scale up to multiple jenkins masters while sharing host resources</p></li>
<li><p>If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself.</p></li></ul>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1517994329-10691-188--
6 years, 10 months
Re: [OST][HC] HE fails to deploy
by Sahina Bose
On Mon, Feb 5, 2018 at 2:59 PM, Sahina Bose <sabose(a)redhat.com> wrote:
> Hi all,
>
> I see the HE fails to deploy after task in running ansible playbook create_target_vm :
>
> TASK [Wait for the engine to come up on the target VM]",
>
> with Error engine state=EngineUnexpectedlyDown
>
> Is this a known issue that you are working on?
>
>
This does seem like a race, because I see that the HC suite again failed
with the same error after a successful run yesterday.
Do I need to open a bug or do we have one tracking this already?
> thanks!
>
> sahina
>
>
> Full HE setup log at http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x8...
>
>
6 years, 10 months