[JIRA] (OVIRT-2822) qemu is configured with the wrong uid in our Jenkins slaves

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2822:
-

 Summary: qemu is configured with the wrong uid in our Jenkins 
slaves
 Key: OVIRT-2822
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2822
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Daniel Belenky
Assignee: infra


Our puppet script creates the qemu uid before qemu is installed, hence it's 
created with the wrong UID which is being assigned to it.
We should either create QEMU with the correct UID (107) or let QEMU's install 
scripts to do their job.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100114)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/NLBFTFBE3A2EV2FEV3UBR55ZWBFORNGA/

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2782:
--
Description: 
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay=0
{code}
We can also control the excessive workload threshold and force Jenkins to 
allocate slaves for jobs in the queue... but, because Jenkins computes the 
excess workload value (which decides if we need to allocate a new node) using 
an EMA, we set it's margins to higher values and it effectively lowers its 
threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}



  was:
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay=0
{code}
But, because Jenkins computes the excess workload value (which decides if we 
need to allocate a new node) using an EMA, we also can control it's margins to 
lower its threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}




> Configure Jenkins to wait less and allocate more
> 
>
> Key: OVIRT-2782
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting 
> {code:java}
> hudson.slaves.NodeProvisioner.initialDelay=0
> {code}
> We can also control the excessive workload threshold and force Jenkins to 
> allocate slaves for jobs in the queue... but, because Jenkins computes the 
> excess workload value (which decides if we need to allocate a new node) using 
> an EMA, we set it's margins to higher values and it effectively lowers its 
> threshold so that Jenkins will allocate nodes faster and in advance.
> The recommended settings by the k8s plugin to spawn a node for every build in 
> the queue:
> ```
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, 
> because Jenkins computes the excess workload value (which decides if we need 
> to allocate a new node) using an EMA, we also can lower its threshold so that 
> Jenkins will allocate nodes faster and in advance.
> {code:java}
> -Dhudson.slaves.NodeProvisioner.initialDelay=0
> -Dhudson.slaves.NodeProvisioner.MARGIN=50
> -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IVNHGJJU2T2JR7PSW2HP5ADG3CCMVRPF/

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2782:
--
Description: 
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay=0
{code}
We can also control the excessive workload threshold and force Jenkins to 
allocate slaves for jobs in the queue... but, because Jenkins computes the 
excess workload value (which decides if we need to allocate a new node) using 
an EMA, we set it's margins to higher values and it effectively lowers its 
threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:

{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}



  was:
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay=0
{code}
We can also control the excessive workload threshold and force Jenkins to 
allocate slaves for jobs in the queue... but, because Jenkins computes the 
excess workload value (which decides if we need to allocate a new node) using 
an EMA, we set it's margins to higher values and it effectively lowers its 
threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}




> Configure Jenkins to wait less and allocate more
> 
>
> Key: OVIRT-2782
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting 
> {code:java}
> hudson.slaves.NodeProvisioner.initialDelay=0
> {code}
> We can also control the excessive workload threshold and force Jenkins to 
> allocate slaves for jobs in the queue... but, because Jenkins computes the 
> excess workload value (which decides if we need to allocate a new node) using 
> an EMA, we set it's margins to higher values and it effectively lowers its 
> threshold so that Jenkins will allocate nodes faster and in advance.
> The recommended settings by the k8s plugin to spawn a node for every build in 
> the queue:
> {code:java}
> -Dhudson.slaves.NodeProvisioner.initialDelay=0
> -Dhudson.slaves.NodeProvisioner.MARGIN=50
> -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/URDQANBIS2V44N5DWL4YLCLBSQL4IWOM/

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2782:
--
Description: 
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can control it's margins to lower 
its threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}



  was:
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can control it's margins to lower 
its threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.

```
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
```


> Configure Jenkins to wait less and allocate more
> 
>
> Key: OVIRT-2782
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, 
> because Jenkins computes the excess workload value (which decides if we need 
> to allocate a new node) using an EMA, we also can control it's margins to 
> lower its threshold so that Jenkins will allocate nodes faster and in advance.
> The recommended settings by the k8s plugin to spawn a node for every build in 
> the queue:
> ```
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, 
> because Jenkins computes the excess workload value (which decides if we need 
> to allocate a new node) using an EMA, we also can lower its threshold so that 
> Jenkins will allocate nodes faster and in advance.
> {code:java}
> -Dhudson.slaves.NodeProvisioner.initialDelay=0
> -Dhudson.slaves.NodeProvisioner.MARGIN=50
> -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JNM6OTFKCH5OXLDEOIHDUHDVUUKKZLV4/

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2782:
--
Description: 
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay=0
{code}
But, because Jenkins computes the excess workload value (which decides if we 
need to allocate a new node) using an EMA, we also can control it's margins to 
lower its threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}



  was:
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay
{code}
 to `0`. But, because Jenkins computes the excess workload value (which decides 
if we need to allocate a new node) using an EMA, we also can control it's 
margins to lower its threshold so that Jenkins will allocate nodes faster and 
in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}




> Configure Jenkins to wait less and allocate more
> 
>
> Key: OVIRT-2782
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting 
> {code:java}
> hudson.slaves.NodeProvisioner.initialDelay=0
> {code}
> But, because Jenkins computes the excess workload value (which decides if we 
> need to allocate a new node) using an EMA, we also can control it's margins 
> to lower its threshold so that Jenkins will allocate nodes faster and in 
> advance.
> The recommended settings by the k8s plugin to spawn a node for every build in 
> the queue:
> ```
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, 
> because Jenkins computes the excess workload value (which decides if we need 
> to allocate a new node) using an EMA, we also can lower its threshold so that 
> Jenkins will allocate nodes faster and in advance.
> {code:java}
> -Dhudson.slaves.NodeProvisioner.initialDelay=0
> -Dhudson.slaves.NodeProvisioner.MARGIN=50
> -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/P3MT242D4TY6NIRJZ5Z3FLUCSNM6QXCU/

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2782:
--
Description: 
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting 
{code:java}
hudson.slaves.NodeProvisioner.initialDelay
{code}
 to `0`. But, because Jenkins computes the excess workload value (which decides 
if we need to allocate a new node) using an EMA, we also can control it's 
margins to lower its threshold so that Jenkins will allocate nodes faster and 
in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}



  was:
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can control it's margins to lower 
its threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.



{code:java}
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
{code}




> Configure Jenkins to wait less and allocate more
> 
>
> Key: OVIRT-2782
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting 
> {code:java}
> hudson.slaves.NodeProvisioner.initialDelay
> {code}
>  to `0`. But, because Jenkins computes the excess workload value (which 
> decides if we need to allocate a new node) using an EMA, we also can control 
> it's margins to lower its threshold so that Jenkins will allocate nodes 
> faster and in advance.
> The recommended settings by the k8s plugin to spawn a node for every build in 
> the queue:
> ```
> By default, Jenkins is configured to wait a few seconds before allocating a 
> new node in a hope that a node in use to be freed. We can control this 
> setting by setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, 
> because Jenkins computes the excess workload value (which decides if we need 
> to allocate a new node) using an EMA, we also can lower its threshold so that 
> Jenkins will allocate nodes faster and in advance.
> {code:java}
> -Dhudson.slaves.NodeProvisioner.initialDelay=0
> -Dhudson.slaves.NodeProvisioner.MARGIN=50
> -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6NX2QQ2IGYX2KJUOU2TFNNKV6L7SSRP4/

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2782:
-

 Summary: Configure Jenkins to wait less and allocate more
 Key: OVIRT-2782
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Daniel Belenky
Assignee: infra


By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can control it's margins to lower 
its threshold so that Jenkins will allocate nodes faster and in advance.

The recommended settings by the k8s plugin to spawn a node for every build in 
the queue:
```
By default, Jenkins is configured to wait a few seconds before allocating a new 
node in a hope that a node in use to be freed. We can control this setting by 
setting `hudson.slaves.NodeProvisioner.initialDelay` to `0`. But, because 
Jenkins computes the excess workload value (which decides if we need to 
allocate a new node) using an EMA, we also can lower its threshold so that 
Jenkins will allocate nodes faster and in advance.

```
-Dhudson.slaves.NodeProvisioner.initialDelay=0
-Dhudson.slaves.NodeProvisioner.MARGIN=50
-Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
```



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5T63UM3YMN25BCDUT2SB325AH27ZHKHP/

[JIRA] (OVIRT-2778) Re: [ovirt-devel] vdsm_standard-check-patch is stuck on Archiving artifacts

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2778:
---

Hi Nir,

It seems that the reason behind this issue is that the s390x node is
offline.
I'm checking it right now and will update asap.

On Sat, Aug 17, 2019 at 3:18 AM Nir Soffer  wrote:

> On Sat, Aug 17, 2019 at 3:06 AM Nir Soffer  wrote:
>
>> This looks like a bug, so adding infra-support - this will open a ticket
>> and someone will look into it.
>>
>> On Sat, Aug 17, 2019 at 1:12 AM Amit Bawer  wrote:
>>
>>> Hi
>>> Unable to run CI builds and OSTs due to indefinite processing over fc29 
>>> Archiving
>>> artifacts phase
>>> Example run:
>>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10453/console
>>>
>>
> We have 2 stuck builds:
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10454/
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10453/
>
> Both started 4 hours ago.
>
> It possible to abort jobs from jenkins UI, but usually it cause more
> trouble because
> of partial cleanup, so lets let infra team handle this properly.
>
>
>> ___
>>> Devel mailing list -- de...@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/de...@ovirt.org/message/JU3IZE2IQLVTVLRYCOOQZSQUC3QNLUD4/
>>>
>> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/de...@ovirt.org/message/3LAOTG5RQDYQTYT7GBPLPSXT4WFHXETL/
>


-- 

Daniel Belenky

Red Hat 


> Re: [ovirt-devel] vdsm_standard-check-patch is stuck on Archiving artifacts
> ---
>
> Key: OVIRT-2778
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2778
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> This looks like a bug, so adding infra-support - this will open a ticket
> and someone will look into it.
> On Sat, Aug 17, 2019 at 1:12 AM Amit Bawer  wrote:
> > Hi
> > Unable to run CI builds and OSTs due to indefinite processing over fc29 
> > Archiving
> > artifacts phase
> > Example run:
> > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/10453/console
> > ___
> > Devel mailing list -- de...@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/de...@ovirt.org/message/JU3IZE2IQLVTVLRYCOOQZSQUC3QNLUD4/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/R2H4FASNLJVEDTOW5KTKCQSIFLKUQV3M/

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2748:
---

Hi,
I've assigned the user germano with dev role. Can you verify you can
trigger builds now? (might require logout and login)

On Mon, Jul 1, 2019 at 10:22 AM Dafna Ron  wrote:

> Adding infra-support as this needs a ticket
>
>
> On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel 
> wrote:
>
>> Hi,
>>
>> I would like to be able to manually trigger OST. According to [1] I might
>> be missing the "Dev Role" as I cannot see the "*build with parameters*"
>> menu.
>>
>> Could you please check if I have permissions?
>>
>> [1]
>> https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html
>>
>> Thanks,
>> Germano
>> ___
>> Infra mailing list -- infra@ovirt.org
>> To unsubscribe send an email to infra-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV4HC7KHYSVMDQO7E5PBF/
>>
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/F4U6RGOA4OHYDTHCGTB7D7MK4ZSBYNH4/
>


-- 

Daniel Belenky

Red Hat 


> Re: "Dev Role" on Jenkins
> -
>
> Key: OVIRT-2748
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Dafna Ron
>Assignee: Daniel Belenky
>
> Adding infra-support as this needs a ticket
> On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel 
> wrote:
> > Hi,
> >
> > I would like to be able to manually trigger OST. According to [1] I might
> > be missing the "Dev Role" as I cannot see the "*build with parameters*"
> > menu.
> >
> > Could you please check if I have permissions?
> >
> > [1]
> > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html
> >
> > Thanks,
> > Germano
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV4HC7KHYSVMDQO7E5PBF/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SVVYG4K7NLFCOSQRGFAO26WGHIQTTISJ/

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2748:
--
Comment: was deleted

(was: Hi, I assigned the user germano with dev role. Can you verify you can 
trigger builds now? (might require logout and login))

> Re: "Dev Role" on Jenkins
> -
>
> Key: OVIRT-2748
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Dafna Ron
>Assignee: Daniel Belenky
>
> Adding infra-support as this needs a ticket
> On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel 
> wrote:
> > Hi,
> >
> > I would like to be able to manually trigger OST. According to [1] I might
> > be missing the "Dev Role" as I cannot see the "*build with parameters*"
> > menu.
> >
> > Could you please check if I have permissions?
> >
> > [1]
> > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html
> >
> > Thanks,
> > Germano
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV4HC7KHYSVMDQO7E5PBF/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/MVQXMOJIIK3JAQMSSMRQWAOUN3A6JEVL/

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2748:
---

Hi, I assigned the user germano with dev role. Can you verify you can trigger 
builds now? (might require logout and login)

> Re: "Dev Role" on Jenkins
> -
>
> Key: OVIRT-2748
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Dafna Ron
>Assignee: Daniel Belenky
>
> Adding infra-support as this needs a ticket
> On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel 
> wrote:
> > Hi,
> >
> > I would like to be able to manually trigger OST. According to [1] I might
> > be missing the "Dev Role" as I cannot see the "*build with parameters*"
> > menu.
> >
> > Could you please check if I have permissions?
> >
> > [1]
> > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html
> >
> > Thanks,
> > Germano
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV4HC7KHYSVMDQO7E5PBF/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/X5RQ7NL4CC6RTZVMZ42WYLD7ZVZXZUVN/

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2748:
--
Status: In Progress  (was: To Do)

> Re: "Dev Role" on Jenkins
> -
>
> Key: OVIRT-2748
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Dafna Ron
>Assignee: Daniel Belenky
>
> Adding infra-support as this needs a ticket
> On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel 
> wrote:
> > Hi,
> >
> > I would like to be able to manually trigger OST. According to [1] I might
> > be missing the "Dev Role" as I cannot see the "*build with parameters*"
> > menu.
> >
> > Could you please check if I have permissions?
> >
> > [1]
> > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html
> >
> > Thanks,
> > Germano
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV4HC7KHYSVMDQO7E5PBF/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6EEDJ3RCQJILBX3LM23NXOSKCBX6JOGP/

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2748:
-

Assignee: Daniel Belenky  (was: infra)

> Re: "Dev Role" on Jenkins
> -
>
> Key: OVIRT-2748
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Dafna Ron
>Assignee: Daniel Belenky
>
> Adding infra-support as this needs a ticket
> On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel 
> wrote:
> > Hi,
> >
> > I would like to be able to manually trigger OST. According to [1] I might
> > be missing the "Dev Role" as I cannot see the "*build with parameters*"
> > menu.
> >
> > Could you please check if I have permissions?
> >
> > [1]
> > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html
> >
> > Thanks,
> > Germano
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV4HC7KHYSVMDQO7E5PBF/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HHHA7ZHJPSKLA4XVUROPMZRC367YETAP/

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky edited comment on OVIRT-2704 at 3/24/19 4:27 PM:


You need to update the throttle secion of the "{project}_manual" template in 
`jobs/confs/yaml/templates/system_tests_templates.yaml`


was (Author: dbele...@redhat.com):
You need to update the throttle secion of the {project}_manual template in 
`jobs/confs/yaml/templates/system_tests_templates.yaml`

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
> 
>
> Key: OVIRT-2704
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/RDOOSO6RKAUAWNADLMJ7NHEBWXMCDXDQ/

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky edited comment on OVIRT-2704 at 3/24/19 4:26 PM:


You need to update the throttle secion of the {project}_manual template in 
`jobs/confs/yaml/templates/system_tests_templates.yaml`


was (Author: dbele...@redhat.com):
You need to update the throttle secion of the '{project}_manual' template in 
`jobs/confs/yaml/templates/system_tests_templates.yaml`

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
> 
>
> Key: OVIRT-2704
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HYLSH7KZCF2FRNSCYVVFYQLO3X6C7Y2Z/

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2704:
---

You need to update the throttle secion of the '{project}_manual' template in 
`jobs/confs/yaml/templates/system_tests_templates.yaml`

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
> 
>
> Key: OVIRT-2704
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EO2OWVR6IQQK34J4VSLHOXA3U7UXP2Z7/

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2704:
---

AFAIK, this job is limited because it never meant to be used as a production 
job, but as a way to debug things or specifically run some scenario. Nir, can't 
your tool work directly with the OST manual job? it already allows some 
concurrency and I guess we could increase it.

Otherwise, I don't have any strict objection on increasing the # of concurrent 
jobs in the manual runner other than that IMO, it wasn't meant to be used in 
this scenario and it will be hard to find jobs there.

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
> 
>
> Key: OVIRT-2704
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W7Z7ANY3PUTUYVITGM5QCUOGCM4KA6L3/

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2656:
---

I'm checking

On Sun, Jan 20, 2019 at 10:30 AM Shirly Radco  wrote:

>
> --
>
> SHIRLY RADCO
>
> BI SENIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
> 
> TRIED. TESTED. TRUSTED. 
>


-- 

DANIEL BELENKY

> Upstream-sources trigger for ovirt-engine-metrics does not work
> ---
>
> Key: OVIRT-2656
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2656
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Shirly Radco
>Assignee: infra
>
> --
> SHIRLY RADCO
> BI SENIOR SOFTWARE ENGINEER
> Red Hat Israel 
> 
> TRIED. TESTED. TRUSTED. 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EU3SSG7TYQDCQQ7BPBYME6GJLQGNQIOZ/

[JIRA] (OVIRT-2645) [VDSM] Tests mounting loop devices fail randomly again

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2645:
---

Nir,

I think that you have a bug in create_loop_devices()
From the log you've sent, it seems that it created just devices 5, 6 and
7dsf
while skipping devices 1-4 because they already existed.
I'm not sure how your tests know which loop devices were created by you
and which already existed and might be busy, but maybe you should
create loop devices until you have enough and store them in a file?

On Wed, Jan 9, 2019 at 2:24 AM Nir Soffer  wrote:

> We had this issue few years ago, and it was solved when we started
> to create loop devices to the slave in check-path.sh.
>
> Before we run the tests, we created loop devices. Looking at the log, we
> had 5
> nodes and we added 3 nodes - this is typical log.
>
> + create_loop_devices 8
> + local last=7
> + local min
> ++ seq 0 7
> + for min in '`seq 0 $last`'
> + local name=/dev/loop0
> + '[' '!' -e /dev/loop0 ']'
> + for min in '`seq 0 $last`'
> + local name=/dev/loop1
> + '[' '!' -e /dev/loop1 ']'
> + for min in '`seq 0 $last`'
> + local name=/dev/loop2
> + '[' '!' -e /dev/loop2 ']'
> + for min in '`seq 0 $last`'
> + local name=/dev/loop3
> + '[' '!' -e /dev/loop3 ']'
> + for min in '`seq 0 $last`'
> + local name=/dev/loop4
> + '[' '!' -e /dev/loop4 ']'
> + for min in '`seq 0 $last`'
> + local name=/dev/loop5
> + '[' '!' -e /dev/loop5 ']'
> + mknod --mode 0666 /dev/loop5 b 7 5
> + for min in '`seq 0 $last`'
> + local name=/dev/loop6
> + '[' '!' -e /dev/loop6 ']'
> + mknod --mode 0666 /dev/loop6 b 7 6
> + for min in '`seq 0 $last`'
> + local name=/dev/loop7
> + '[' '!' -e /dev/loop7 ']'
> + mknod --mode 0666 /dev/loop7 b 7 7
>
>
> But mounting images failed later as you can see bellow.
>
> Failed build:
>
> https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_standard-check-patch/runs/1297/nodes/124/steps/345/log/?start=0
>
>
> The same tests run fine in travis inside a container:
> https://travis-ci.org/nirs/vdsm/jobs/471920126
>
> Anyone has idea why mounting fail randomly in Jenkins slaves, and how we
> can fix this issue?
>
> ==
>
> ERROR: Tests mkimage.mkFloppyFs creating an image and checking its content.
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", 
> line 142, in wrapper
> return f(self, *args)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py",
>  line 194, in wrapper
> return f(*args, **kwargs)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py",
>  line 211, in test_mkFloppyFs
> floppy = mkimage.mkFloppyFs("vmId_floppy", self.files, label)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", 
> line 137, in mkFloppyFs
> injectFilesToFs(floppy, files, 'vfat')
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", 
> line 113, in injectFilesToFs
> m.mount(mntOpts='loop', vfstype=fstype)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py",
>  line 207, in mount
> cgroup=cgroup)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py",
>  line 277, in _mount
> _runcmd(cmd)
>   File 
> "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py",
>  line 305, in _runcmd
> raise MountError(rc, b";".join((out, err)))
> MountError: (32, ';mount: 
> /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img:
>  failed to setup loop device: No such file or directory\n')
>  >> begin captured logging << 
> 2019-01-08 23:46:19,720 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 
> 0-1 /usr/sbin/mkfs.msdos -C 
> /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img
>  1440 -n FSLABEL (cwd None) (commands:198)
> 2019-01-08 23:46:19,729 DEBUG (MainThread) [root] SUCCESS:  = '';  = 
> 0 (commands:219)
> 2019-01-08 23:46:19,731 INFO  (MainThread) [storage.Mount] mounting 
> /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img
>  at /tmp/tmpSejvmr (mount:204)
> 2019-01-08 23:46:19,731 DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 
> 0-1 /usr/bin/mount -t vfat -o loop 
> /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img
>  /tmp/tmpSejvmr (cwd None) (commands:198)
> 2019-01-08 23:46:19,743 DEBUG (MainThread) [root] FAILED:  = 'mount: 
> /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img:
>  failed to setup 

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky edited comment on OVIRT-2638 at 12/31/18 12:47 PM:
--

I've cleaned the host, and it is not up and running.
The problem was that due filled disk, there were stuck VMs there that prevented 
the host from being cleaned up. 


was (Author: dbele...@redhat.com):
I've cleaned the host, and it is not up and running.

> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Daniel Belenky
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/C2L6CEJ77Q6TNJAS552AKJPY2S2ETIIN/

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2638:
---

I've cleaned the host, and it is not up and running.

> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Daniel Belenky
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CMM4VU6R7DQFFMU45KOX7ONBHARTKJII/

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2638:
--
Resolution: Fixed
Status: Done  (was: To Do)

> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Daniel Belenky
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XXYBKEXDGWTR4ZAWDYY7WBEIITOPOOGJ/

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2638:
---

[~lmilb...@redhat.com] There is no service that sends an email but those VMs 
are managed by our oVirt engine phx instance 
[here|https://engine-phx.ovirt.org] so the disk can be monitored from there.


> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Daniel Belenky
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/Z4GT4YOUWFX7UKE5EXTECRNHAIOBZFRX/

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2638:
-

Assignee: Daniel Belenky  (was: infra)

> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Daniel Belenky
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GXR6KL3PQVLQNY7WS5UXYQG5QF6MWCFQ/

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2638:
---

The node where the build was running on ( vm0038.workers-phx.ovirt.org ) ran 
out of disk space.
That's why we see all those issues.
I'm checking what fills the disk.

> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VE6J5ACCRMYTQZH47LILAVZARRYNDMER/

[JIRA] (OVIRT-2616) Rawhide build failed, not logs available

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2616:
---

The build summary doesn't point to a log because it doesn't exist yet.
That's why see "Testing system error" message on that substage.
You can have a look in Blue Ocean and see the logs from the CI system
itself here

.

On Thu, Dec 6, 2018 at 12:05 PM Nir Soffer  wrote:

> On Thu, Dec 6, 2018, 11:16 Daniel Belenky 
>> Hi Nir,
>>
>> The rawhide substage failed to install `python2-docker`.
>>
>
> Can you point me to the log with this error?
>
> Why the build log was missing?
>
> Maybe the build sammary html should point to a differrent log for such
> failures?
>
> I think it was a temporary issue with the rawhide repo. We don't mirror it.
>>
>> On Wed, Dec 5, 2018 at 11:21 PM Nir Soffer  wrote:
>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/artifact/ci_build_summary.html
>>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//artifact/check-patch.fcraw.x86_64/mock_logs/script/stdout_stderr.log
>>> returns 404
>>>
>>> The next builds on this topic succeeded, so it probably was a temporary
>>> error. Do we have any other
>>> log that can explain what happened on the slave running the rawhide
>>> build?
>>>
>>>
>>> Nir
>>> ___
>>> Infra mailing list -- infra@ovirt.org
>>> To unsubscribe send an email to infra-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FFF7KZJ4BSZGHTJYAJPASOPVZCJQ7WB5/
>>>
>>
>>
>> --
>>
>> DANIEL BELENKY
>>
>

-- 

DANIEL BELENKY

> Rawhide build failed, not logs available
> 
>
> Key: OVIRT-2616
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2616
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/artifact/ci_build_summary.html
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//artifact/check-patch.fcraw.x86_64/mock_logs/script/stdout_stderr.log
> returns 404
> The next builds on this topic succeeded, so it probably was a temporary
> error. Do we have any other
> log that can explain what happened on the slave running the rawhide build?
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TDB5LTKXVGEDPKWEU4GHBKYHUIJSQHKR/

[JIRA] (OVIRT-2616) Rawhide build failed, not logs available

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2616:
---

Hi Nir,

The rawhide substage failed to install `python2-docker`.
I think it was a temporary issue with the rawhide repo. We don't mirror it.

On Wed, Dec 5, 2018 at 11:21 PM Nir Soffer  wrote:

>
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/artifact/ci_build_summary.html
>
>
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//artifact/check-patch.fcraw.x86_64/mock_logs/script/stdout_stderr.log
> returns 404
>
> The next builds on this topic succeeded, so it probably was a temporary
> error. Do we have any other
> log that can explain what happened on the slave running the rawhide build?
>
>
> Nir
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FFF7KZJ4BSZGHTJYAJPASOPVZCJQ7WB5/
>


-- 

DANIEL BELENKY

> Rawhide build failed, not logs available
> 
>
> Key: OVIRT-2616
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2616
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/artifact/ci_build_summary.html
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//artifact/check-patch.fcraw.x86_64/mock_logs/script/stdout_stderr.log
> returns 404
> The next builds on this topic succeeded, so it probably was a temporary
> error. Do we have any other
> log that can explain what happened on the slave running the rawhide build?
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GJOXEBKZ6TDM4HJHKAUFS2Y4PJ3YUKG7/

[JIRA] (OVIRT-2595) Re: identities on gerrit.ovirt.org

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2595:
-

 Summary: Re: identities on gerrit.ovirt.org
 Key: OVIRT-2595
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2595
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Daniel Belenky
Assignee: infra


fwd to infra-support

On Tue, Nov 27, 2018 at 4:19 PM Dominik Holler  wrote:

> Hi,
> can you please remove the identities with the email address
> thegreenkep...@hollyhome.ath.cx
> and
> dominik.hol...@gmail.com
> from gerrit.ovirt.org.
> But please do not delete dhol...@redhat.com.
> Thanks,
> Dominik
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/C7OLABFOL6YXVNEPUV6DKESO2EJIQEP3/
>


-- 

DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EHK5O5NZOGHZMC27Q4EDBYEFL4XP4EU6/

[JIRA] (OVIRT-2588) Fwd: Jenkins – Running OST Manual

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2588:
-

 Summary: Fwd: Jenkins – Running OST Manual
 Key: OVIRT-2588
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2588
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Daniel Belenky
Assignee: infra


-- Forwarded message -
From: Tomasz Barański 
Date: Fri, Nov 23, 2018 at 11:53 AM
Subject: Jenkins – Running OST Manual
To: 


Hello,

I'm trying to diagnose a failing build and need to run manually run the
OST. I'm logged in to Jenkins, but I don't seem to have the right
credentials to start a build at
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/

My account: tbaransk, with my @redhat mail address.

Please help.

Tomo
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GKH7W27IUZSXBLY5GFITFL3BCWL3BHR2/


-- 

DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5TCARBTTPVPCBIYTMIKVC7SC7GNK5EEU/

[JIRA] (OVIRT-2569) attach bare metal node to OpenShift

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2569:
-

Assignee: Evgheni Dereveanchin  (was: infra)

> attach bare metal node to OpenShift
> ---
>
> Key: OVIRT-2569
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2569
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Evgheni Dereveanchin
>Priority: High
>
> We want to use ephemeral openshift pods as Jenkins slaves and to be able to 
> test virtualization capabilities we need to make sure we have a bare metal 
> node for those pods.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZT5RKFR3LIKDX6SJVMVTU4JJFJ545MFZ/

[JIRA] (OVIRT-2569) attach bare metal node to OpenShift

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2569:
-

 Summary: attach bare metal node to OpenShift
 Key: OVIRT-2569
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2569
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra
Priority: High


We want to use ephemeral openshift pods as Jenkins slaves and to be able to 
test virtualization capabilities we need to make sure we have a bare metal node 
for those pods.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VK74EG3IYK2FANAMEMDQ5ZWKPPN4RKHB/

[JIRA] (OVIRT-2569) attach bare metal node to OpenShift

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2569:
--
Epic Link: OVIRT-403

> attach bare metal node to OpenShift
> ---
>
> Key: OVIRT-2569
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2569
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>Priority: High
>
> We want to use ephemeral openshift pods as Jenkins slaves and to be able to 
> test virtualization capabilities we need to make sure we have a bare metal 
> node for those pods.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FYCIUNMSD2DRADRB4HZMNIFR6Y5N7BIT/

[JIRA] (OVIRT-2551) failure to remove journal logs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2551:
-

Assignee: Evgheni Dereveanchin  (was: infra)

> failure to remove journal logs
> --
>
> Key: OVIRT-2551
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2551
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Daniel Belenky
>Assignee: Evgheni Dereveanchin
>
> Lately, we've seen an issue where systemd-journal logs dir belongs to the 
> root group and automation (slave_cleanup.sh) fails to remove those logs and 
> eventually fails the entire job. I can think of 2 reasons why we should 
> remove journals: saving disk space and possibly having a clean journal for 
> every job (though it makes debugging hard because we don't have old logs). 
> Anyway, I think that the way we remove journal logs is improper - maybe back 
> when David wrote this (back in 2015) it was the only way, but today we can 
> ask journalctl to handle the logs rotation for us:
>--vacuum-size=, --vacuum-time=, --vacuum-files=
>Removes archived journal files until the disk space they use falls 
> below the specified size (specified with the usual "K", "M", "G" and "T" 
> suffixes), or all archived journal
>files contain no data older than the specified timespan (specified 
> with the usual "s", "m", "h", "days", "months", "weeks" and "years" 
> suffixes), or no more than the
>specified number of separate journal files remain. Note that 
> running --vacuum-size= has only an indirect effect on the output shown by 
> --disk-usage, as the latter includes
>active journal files, while the vacuuming operation only operates 
> on archived journal files. Similarly, --vacuum-files= might not actually 
> reduce the number of journal files
>to below the specified number, as it will not remove active 
> journal files.  --vacuum-size=, --vacuum-time= and --vacuum-files= may be 
> combined in a single invocation to
>enforce any combination of a size, a time and a number of files 
> limit on the archived journal files. Specifying any of these three parameters 
> as zero is equivalent to not
>enforcing the specific limit, and is thus redundant.
> I think that we should use --vacuum-time and keep journal logs for 10-15 days.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100094)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IQX375J5H3MCCS2OPVG27X3EE5HXA6PC/

[JIRA] (OVIRT-2551) failure to remove journal logs

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2551:
-

 Summary: failure to remove journal logs
 Key: OVIRT-2551
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2551
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Daniel Belenky
Assignee: infra


Lately, we've seen an issue where systemd-journal logs dir belongs to the root 
group and automation (slave_cleanup.sh) fails to remove those logs and 
eventually fails the entire job. I can think of 2 reasons why we should remove 
journals: saving disk space and possibly having a clean journal for every job 
(though it makes debugging hard because we don't have old logs). Anyway, I 
think that the way we remove journal logs is improper - maybe back when David 
wrote this (back in 2015) it was the only way, but today we can ask journalctl 
to handle the logs rotation for us:

   --vacuum-size=, --vacuum-time=, --vacuum-files=
   Removes archived journal files until the disk space they use falls 
below the specified size (specified with the usual "K", "M", "G" and "T" 
suffixes), or all archived journal
   files contain no data older than the specified timespan (specified 
with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), 
or no more than the
   specified number of separate journal files remain. Note that running 
--vacuum-size= has only an indirect effect on the output shown by --disk-usage, 
as the latter includes
   active journal files, while the vacuuming operation only operates on 
archived journal files. Similarly, --vacuum-files= might not actually reduce 
the number of journal files
   to below the specified number, as it will not remove active journal 
files.  --vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a 
single invocation to
   enforce any combination of a size, a time and a number of files 
limit on the archived journal files. Specifying any of these three parameters 
as zero is equivalent to not
   enforcing the specific limit, and is thus redundant.

I think that we should use --vacuum-time and keep journal logs for 10-15 days.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100094)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OKDFEWDBUD2GKD4QC75WNP63BAVDWCTS/

[JIRA] (OVIRT-2529) OST network suite master is failing on reposync

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2529:
--
Status: In Progress  (was: To Do)

The cause was an outage in resources.ovirt.org

> OST network suite master is failing on reposync
> ---
>
> Key: OVIRT-2529
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2529
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Edward Haas
>Assignee: infra
>
> Hello,
> The network suite master job is failing on
> reposync command failed for repoid: ovirt-master-tested-el7
> http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/644/
> Could you please help determine what is going on?
> Thanks,
> Edy.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100093)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QI4WEDEHAU5BNBVAIZKS3CEGVAYYYLE2/

[JIRA] (OVIRT-2500) Support for notifications configuration in STDCI DSL

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2500:
-

Assignee: Daniel Belenky  (was: infra)

> Support for notifications configuration in STDCI DSL
> 
>
> Key: OVIRT-2500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2500
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> As a developer, I  want to have the ability to configure different aspects of 
> the CI system's notifications: who receives the notifications (the change/tag 
> owner, list of maintainers, etc), what kind of notifications are sent (notify 
> SCM, notify mail, etc) so that I wont miss important events in my proejct.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2DFGF2JIGACCLVWJ7OP73ZIOKDOH2JQZ/

[JIRA] (OVIRT-2500) Support for notifications configuration in STDCI DSL

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2500:
-

 Summary: Support for notifications configuration in STDCI DSL
 Key: OVIRT-2500
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2500
 Project: oVirt - virtualization made easy
  Issue Type: New Feature
Reporter: Daniel Belenky
Assignee: infra


As a developer, I  want to have the ability to configure different aspects of 
the CI system's notifications: who receives the notifications (the change/tag 
owner, list of maintainers, etc), what kind of notifications are sent (notify 
SCM, notify mail, etc) so that I wont miss important events in my proejct.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WNZMIB2KEH5XBLDBBXVKDOHD6QK4G75Y/

[JIRA] (OVIRT-2500) Support for notifications configuration in STDCI DSL

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2500:
--
Epic Link: OVIRT-2499

> Support for notifications configuration in STDCI DSL
> 
>
> Key: OVIRT-2500
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2500
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Daniel Belenky
>Assignee: infra
>
> As a developer, I  want to have the ability to configure different aspects of 
> the CI system's notifications: who receives the notifications (the change/tag 
> owner, list of maintainers, etc), what kind of notifications are sent (notify 
> SCM, notify mail, etc) so that I wont miss important events in my proejct.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EMBXPFJ5BKQVEI2RR3Z3RDTSVCTVQUUA/

[JIRA] (OVIRT-2499) Add support for tag stage in STDCI

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2499:
-

 Summary: Add support for tag stage in STDCI
 Key: OVIRT-2499
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2499
 Project: oVirt - virtualization made easy
  Issue Type: Epic
  Components: Standard CI (Pipelines), STDCI DSL
Reporter: Daniel Belenky
Assignee: infra


As a developer, I want to have the ability to run my automation code upon new 
tags being pushed to my project so that I can trigger an automated release 
process.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/MMWBM33FEVD2XXHHEPERYTVPAXO5SB5P/

[JIRA] (OVIRT-2499) Add support for tag stage in STDCI

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2499:
-

Assignee: Daniel Belenky  (was: infra)

> Add support for tag stage in STDCI
> --
>
> Key: OVIRT-2499
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2499
> Project: oVirt - virtualization made easy
>  Issue Type: Epic
>  Components: Standard CI (Pipelines), STDCI DSL
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> As a developer, I want to have the ability to run my automation code upon new 
> tags being pushed to my project so that I can trigger an automated release 
> process.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/C5EWMOTZ3JI3SABL6X7I3MFX4XOVNR6T/

[JIRA] (OVIRT-2490) Add support for tag-stage

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2490:
-

Assignee: Daniel Belenky  (was: infra)

> Add support for tag-stage
> -
>
> Key: OVIRT-2490
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2490
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/MRF7EDF6C5QVWOCIYE4CHOBGO4CPWA7C/

[JIRA] (OVIRT-2490) Add support for tag-stage

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2490:
-

 Summary: Add support for tag-stage
 Key: OVIRT-2490
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2490
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UJDE56OPEC452DYW4PIECQU3JPDCITPK/

[JIRA] (OVIRT-2474) Avoid duplicated code for mock runner's shell cmd

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2474:
-

 Summary: Avoid duplicated code for mock runner's shell cmd
 Key: OVIRT-2474
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2474
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: mock_runner
Reporter: Daniel Belenky
Assignee: infra


Instead of having to maintain duplicated code for the mock shell
command (which is actually what runs in mock), we should store it in a
variable.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/553FVGW4RYCKOW7UHE25YT4OARZ7LKIE/

[JIRA] (OVIRT-2474) Avoid duplicated code for mock runner's shell cmd

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2474:
-

Assignee: Daniel Belenky  (was: infra)

> Avoid duplicated code for mock runner's shell cmd
> -
>
> Key: OVIRT-2474
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2474
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> Instead of having to maintain duplicated code for the mock shell
> command (which is actually what runs in mock), we should store it in a
> variable.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PXUMV3FCZ2WDICHKFR4BMNQQWZMM3EBW/

[JIRA] (OVIRT-2471) Make timeout configurable from STDCI DSL

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2471:
-

Assignee: Daniel Belenky  (was: infra)

> Make timeout configurable from STDCI DSL
> 
>
> Key: OVIRT-2471
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> As new projects have new timeout requirements, we should allow them to 
> configure the timeout from stdci.yaml.
> The configuration should probably go to runtime_requirements and configurable 
> under the 'timeout' key. The configuration should be from the following form: 
> {code:java}
> [0-9]+(\s+)?(h|s|m)
> {code}
>  and where h, s and m can have multiple forms such as hour, hours, minute, 
> etc...
> Example:
> {code:java}
> ---
>   runtime requirements:
> timeout: 2h
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HWPLH33JL3VTDTMUPWSPWSOMUYX4GYHD/

[JIRA] (OVIRT-2471) Make timeout configurable from STDCI DSL

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2471:
--
Description: 
As new projects have new timeout requirements, we should allow them to 
configure the timeout from stdci.yaml.

The configuration should probably go to runtime_requirements and configurable 
under the 'timeout' key. The configuration should be from the following form: 
{code:java}
[0-9]+(\s+)?(h|s|m)
{code}
 and where h, s and m can have multiple forms such as hour, hours, minute, 
etc...

Example:
{code:java}
---
  runtime requirements:
timeout: 2h
{code}


  was:
As new projects have new timeout requirements, we should allow them to 
configure the timeout from stdci.yaml.

The configuration should probably go to runtime_requirements and configurable 
under the 'timeout' key. The configuration should be from the following form: 
[0-9]+(\s+)?(h|s|m) and where h, s and m can have multiple forms such as hour, 
hours, minute, etc...

Example:
{code:java}
---
  runtime requirements:
timeout: 2h
{code}



> Make timeout configurable from STDCI DSL
> 
>
> Key: OVIRT-2471
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: Daniel Belenky
>Assignee: infra
>
> As new projects have new timeout requirements, we should allow them to 
> configure the timeout from stdci.yaml.
> The configuration should probably go to runtime_requirements and configurable 
> under the 'timeout' key. The configuration should be from the following form: 
> {code:java}
> [0-9]+(\s+)?(h|s|m)
> {code}
>  and where h, s and m can have multiple forms such as hour, hours, minute, 
> etc...
> Example:
> {code:java}
> ---
>   runtime requirements:
> timeout: 2h
> {code}



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3WAROSEFILO6M2B425HYLY6LMU4OEKLQ/

[JIRA] (OVIRT-2471) Make timeout configurable from STDCI DSL

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2471:
-

 Summary: Make timeout configurable from STDCI DSL
 Key: OVIRT-2471
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2471
 Project: oVirt - virtualization made easy
  Issue Type: New Feature
Reporter: Daniel Belenky
Assignee: infra


As new projects have new timeout requirements, we should allow them to 
configure the timeout from stdci.yaml.

The configuration should probably go to runtime_requirements and configurable 
under the 'timeout' key. The configuration should be from the following form: 
[0-9]+(\s+)?(h|s|m) and where h, s and m can have multiple forms such as hour, 
hours, minute, etc...

Example:
{code:java}
---
  runtime requirements:
timeout: 2h
{code}




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PQGN5KPZYS6RG4UMYVPUTEXACYUX2HPK/

[JIRA] (OVIRT-2453) vdsm_{master,4.2} check-merge to run on bare metal slaves on CI

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2453:
---

On Tue, Aug 28, 2018 at 8:23 AM Edward Haas  wrote:

> Hello,
>
> VDSM check-merge is using lago VM/s to run functional tests, mainly in the
> network domain.
> Unfortunately, when running on a VM slave, the tests are running in a
> nested VM which seems to be unstable (the nested VM is getting
> stuck/crashes).
>
> Here are some recent failures:
> http://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/247/
> http://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/249/
>
> Could you please run this job on a bare metal slave?
>
> Thanks,
> Edy.
>


-- 

DANIEL BELENKY

> vdsm_{master,4.2} check-merge to run on bare metal slaves on CI
> ---
>
> Key: OVIRT-2453
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2453
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Edward Haas
>Assignee: infra
>
> Hello,
> VDSM check-merge is using lago VM/s to run functional tests, mainly in the
> network domain.
> Unfortunately, when running on a VM slave, the tests are running in a
> nested VM which seems to be unstable (the nested VM is getting
> stuck/crashes).
> Here are some recent failures:
> http://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/247/
> http://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/249/
> Could you please run this job on a bare metal slave?
> Thanks,
> Edy.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LQTMPDYI4K5TZ65WADYH2MDIIUFZHERG/

[JIRA] (OVIRT-2427) Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - Still Failing!

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2427:
-

Assignee: Daniel Belenky  (was: infra)

> Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - 
> Still Failing!
> 
>
> Key: OVIRT-2427
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2427
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> I'm checking this issue. +infra-supp...@ovirt.org 
> to track in Jira
> On Sun, Aug 12, 2018 at 10:11 AM Eyal Edri  wrote:
> > Adding Gal.
> >
> > On Sun, Aug 12, 2018 at 9:46 AM Yedidyah Bar David 
> > wrote:
> >
> >> On Sun, Aug 12, 2018 at 5:33 AM,   wrote:
> >> > Project:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/
> >> > Build:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/465/
> >> > Build Number: 465
> >> > Build Status:  Still Failing
> >> > Triggered By: Started by timer
> >>
> >> 02:33:45 ##
> >> 02:33:45 ## FINISHED SUCCESSFULLY
> >> 02:33:45 ##
> >> 02:33:45 mkdir: cannot create directory
> >> 'exported-artifacts/mock_logs': Permission denied
> >>
> >> Can someone please have a look? Thanks.
> >>
> >> >
> >> > -
> >> > Changes Since Last Success:
> >> > -
> >> > Changes for Build #457
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> > [Barak Korren] mock_runner: don`t store logs in source checkout
> >> >
> >> >
> >> > Changes for Build #458
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> > [Sandro Bonazzola] ovirt-wgt: exclude fc28 on 4.2
> >> >
> >> >
> >> > Changes for Build #459
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #460
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #461
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #462
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #463
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #464
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #465
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> >
> >> >
> >> > -
> >> > Failed Tests:
> >> > -
> >> > No tests ran.
> >>
> >>
> >>
> >> --
> >> Didi
> >> ___
> >> Infra mailing list -- infra@ovirt.org
> >> To unsubscribe send an email to infra-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >> oVirt Code of Conduct:
> >> https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives:
> >> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LQBKUFS24SRNZN7ROZBYH6KOI6LG5YCR/
> >>
> >
> >
> > --
> >
> > Eyal edri
> >
> >
> > MANAGER
> >
> > RHV DevOps
> >
> > EMEA VIRTUALIZATION R
> >
> >
> > Red Hat EMEA 
> >  TRIED. TESTED. TRUSTED. 
> > phone: +972-9-7692018
> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EHACX5RACY6G5ULXIQ7VPQCYZFFII72Z/
> >
> -- 
> DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SYFJHCMUBI7PPYULVG3JAFVALEPA23WN/

[JIRA] (OVIRT-2427) Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - Still Failing!

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2427:
--
Resolution: Fixed
Status: Done  (was: To Do)

Fixed in OVIRT-2434

> Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - 
> Still Failing!
> 
>
> Key: OVIRT-2427
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2427
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Daniel Belenky
>Assignee: infra
>
> I'm checking this issue. +infra-supp...@ovirt.org 
> to track in Jira
> On Sun, Aug 12, 2018 at 10:11 AM Eyal Edri  wrote:
> > Adding Gal.
> >
> > On Sun, Aug 12, 2018 at 9:46 AM Yedidyah Bar David 
> > wrote:
> >
> >> On Sun, Aug 12, 2018 at 5:33 AM,   wrote:
> >> > Project:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/
> >> > Build:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/465/
> >> > Build Number: 465
> >> > Build Status:  Still Failing
> >> > Triggered By: Started by timer
> >>
> >> 02:33:45 ##
> >> 02:33:45 ## FINISHED SUCCESSFULLY
> >> 02:33:45 ##
> >> 02:33:45 mkdir: cannot create directory
> >> 'exported-artifacts/mock_logs': Permission denied
> >>
> >> Can someone please have a look? Thanks.
> >>
> >> >
> >> > -
> >> > Changes Since Last Success:
> >> > -
> >> > Changes for Build #457
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> > [Barak Korren] mock_runner: don`t store logs in source checkout
> >> >
> >> >
> >> > Changes for Build #458
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> > [Sandro Bonazzola] ovirt-wgt: exclude fc28 on 4.2
> >> >
> >> >
> >> > Changes for Build #459
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #460
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #461
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #462
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #463
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #464
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #465
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> >
> >> >
> >> > -
> >> > Failed Tests:
> >> > -
> >> > No tests ran.
> >>
> >>
> >>
> >> --
> >> Didi
> >> ___
> >> Infra mailing list -- infra@ovirt.org
> >> To unsubscribe send an email to infra-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >> oVirt Code of Conduct:
> >> https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives:
> >> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LQBKUFS24SRNZN7ROZBYH6KOI6LG5YCR/
> >>
> >
> >
> > --
> >
> > Eyal edri
> >
> >
> > MANAGER
> >
> > RHV DevOps
> >
> > EMEA VIRTUALIZATION R
> >
> >
> > Red Hat EMEA 
> >  TRIED. TESTED. TRUSTED. 
> > phone: +972-9-7692018
> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EHACX5RACY6G5ULXIQ7VPQCYZFFII72Z/
> >
> -- 
> DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YY4EP2W4W7FQHGPW3PR42MIHGITNKRJE/

[JIRA] (OVIRT-2434) mock runner leaks stdin to user's script

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2434:
--
Assignee: Daniel Belenky  (was: infra)
  Status: In Progress  (was: To Do)

> mock runner leaks stdin to user's script
> 
>
> Key: OVIRT-2434
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2434
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TN75E3XRQNDLMYXUE5C4CMAKBLZ3GKN7/

[JIRA] (OVIRT-2434) mock runner leaks stdin to user's script

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2434:
-

 Summary: mock runner leaks stdin to user's script
 Key: OVIRT-2434
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2434
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6MCBJNUGP5ORPUE5UG3BYYCDRCLNG2LK/

[JIRA] (OVIRT-2434) mock runner leaks stdin to user's script

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2434:
--
Epic Link: OVIRT-400

> mock runner leaks stdin to user's script
> 
>
> Key: OVIRT-2434
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2434
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Daniel Belenky
>Assignee: infra
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TLUDXRPUKUOLJGZ7EQ6KIOQKTUHMJIHX/

[JIRA] (OVIRT-2427) Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - Still Failing!

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2427:
---

It affects all HE suites. I'm trying to find the cause.




-- 

DANIEL BELENKY


> Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - 
> Still Failing!
> 
>
> Key: OVIRT-2427
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2427
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Daniel Belenky
>Assignee: infra
>
> I'm checking this issue. +infra-supp...@ovirt.org 
> to track in Jira
> On Sun, Aug 12, 2018 at 10:11 AM Eyal Edri  wrote:
> > Adding Gal.
> >
> > On Sun, Aug 12, 2018 at 9:46 AM Yedidyah Bar David 
> > wrote:
> >
> >> On Sun, Aug 12, 2018 at 5:33 AM,   wrote:
> >> > Project:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/
> >> > Build:
> >> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/465/
> >> > Build Number: 465
> >> > Build Status:  Still Failing
> >> > Triggered By: Started by timer
> >>
> >> 02:33:45 ##
> >> 02:33:45 ## FINISHED SUCCESSFULLY
> >> 02:33:45 ##
> >> 02:33:45 mkdir: cannot create directory
> >> 'exported-artifacts/mock_logs': Permission denied
> >>
> >> Can someone please have a look? Thanks.
> >>
> >> >
> >> > -
> >> > Changes Since Last Success:
> >> > -
> >> > Changes for Build #457
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> > [Barak Korren] mock_runner: don`t store logs in source checkout
> >> >
> >> >
> >> > Changes for Build #458
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> > [Sandro Bonazzola] ovirt-wgt: exclude fc28 on 4.2
> >> >
> >> >
> >> > Changes for Build #459
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #460
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #461
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #462
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #463
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #464
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> > Changes for Build #465
> >> > [Gal Ben Haim] HE: Added Local Maintenance Tests
> >> >
> >> >
> >> >
> >> >
> >> > -
> >> > Failed Tests:
> >> > -
> >> > No tests ran.
> >>
> >>
> >>
> >> --
> >> Didi
> >> ___
> >> Infra mailing list -- infra@ovirt.org
> >> To unsubscribe send an email to infra-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> >> oVirt Code of Conduct:
> >> https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives:
> >> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LQBKUFS24SRNZN7ROZBYH6KOI6LG5YCR/
> >>
> >
> >
> > --
> >
> > Eyal edri
> >
> >
> > MANAGER
> >
> > RHV DevOps
> >
> > EMEA VIRTUALIZATION R
> >
> >
> > Red Hat EMEA 
> >  TRIED. TESTED. TRUSTED. 
> > phone: +972-9-7692018
> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EHACX5RACY6G5ULXIQ7VPQCYZFFII72Z/
> >
> -- 
> DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/J26NUIOFUXZTYJMGDGPMASCOFWZVLLBW/

[JIRA] (OVIRT-2413) Set up CNV Jenkins to run STDCI

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2413:
--
Epic Name: Jenkins STDCI setup  (was: Set up CNV Jenkins to run STDCI)

> Set up CNV Jenkins to run STDCI
> ---
>
> Key: OVIRT-2413
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2413
> Project: oVirt - virtualization made easy
>  Issue Type: Epic
>Reporter: Daniel Belenky
>Assignee: infra
>
> Add here all tasks that needs to be done in order to run STDCI on CNV Jenkins.
> https://cnv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FWPLLSWD3ZKYXMDYIZ2VZTVCWULM65GS/

[JIRA] (OVIRT-2427) Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 465 - Still Failing!

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2427:
-

 Summary: Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 
- Build # 465 - Still Failing!
 Key: OVIRT-2427
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2427
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Daniel Belenky
Assignee: infra


I'm checking this issue. +infra-supp...@ovirt.org 
to track in Jira

On Sun, Aug 12, 2018 at 10:11 AM Eyal Edri  wrote:

> Adding Gal.
>
> On Sun, Aug 12, 2018 at 9:46 AM Yedidyah Bar David 
> wrote:
>
>> On Sun, Aug 12, 2018 at 5:33 AM,   wrote:
>> > Project:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/
>> > Build:
>> http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/465/
>> > Build Number: 465
>> > Build Status:  Still Failing
>> > Triggered By: Started by timer
>>
>> 02:33:45 ##
>> 02:33:45 ## FINISHED SUCCESSFULLY
>> 02:33:45 ##
>> 02:33:45 mkdir: cannot create directory
>> 'exported-artifacts/mock_logs': Permission denied
>>
>> Can someone please have a look? Thanks.
>>
>> >
>> > -
>> > Changes Since Last Success:
>> > -
>> > Changes for Build #457
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> > [Barak Korren] mock_runner: don`t store logs in source checkout
>> >
>> >
>> > Changes for Build #458
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> > [Sandro Bonazzola] ovirt-wgt: exclude fc28 on 4.2
>> >
>> >
>> > Changes for Build #459
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> > Changes for Build #460
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> > Changes for Build #461
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> > Changes for Build #462
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> > Changes for Build #463
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> > Changes for Build #464
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> > Changes for Build #465
>> > [Gal Ben Haim] HE: Added Local Maintenance Tests
>> >
>> >
>> >
>> >
>> > -
>> > Failed Tests:
>> > -
>> > No tests ran.
>>
>>
>>
>> --
>> Didi
>> ___
>> Infra mailing list -- infra@ovirt.org
>> To unsubscribe send an email to infra-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LQBKUFS24SRNZN7ROZBYH6KOI6LG5YCR/
>>
>
>
> --
>
> Eyal edri
>
>
> MANAGER
>
> RHV DevOps
>
> EMEA VIRTUALIZATION R
>
>
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
> ___
> Infra mailing list -- infra@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EHACX5RACY6G5ULXIQ7VPQCYZFFII72Z/
>


-- 

DANIEL BELENKY



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ISLZXFMDVSDSLHED32C6IU57BTJBDGCR/

[JIRA] (OVIRT-2417) upgrade-from-prevrelease-suite failure *.repo No such file or directory

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2417:
--
Resolution: Done
Status: Done  (was: To Do)

Closing as this is not a bug.
I've updated the version table helper https://gerrit.ovirt.org/#/c/93590/

Thanks for reporting this [~gsher...@redhat.com]

> upgrade-from-prevrelease-suite failure *.repo No such file or directory
> ---
>
> Key: OVIRT-2417
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2417
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: OST Manual job
>Reporter: Greg Sheremeta
>Assignee: infra
>Priority: Highest
>
> Hi,
> Re: packaging: Replace dashboard with ui-extensions
> https://gerrit.ovirt.org/#/c/92698/
> As Didi requested, I tried to run upgrade-from-prevrelease-suite but:
> *23:45:23* + cp
> 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo'
> exported-artifacts*23:45:23* cp: cannot stat
> 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo': No
> such file or directory*23:45:23* POST BUILD TASK : FAILURE*23:45:23*
> END OF POST BUILD TASK : 0*23:45:23* ESCALATE FAILED POST BUILD TASK
> TO JOB STATUS
> Can you assist?
> -- 
> GREG SHEREMETA
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
> Red Hat NA
> 
> gsher...@redhat.comIRC: gshereme
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DUMT6KHXVHCIOVPAWMSNFYVWVRHZSCXJ/

[JIRA] (OVIRT-2417) upgrade-from-prevrelease-suite failure *.repo No such file or directory

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2417:
---

[~gsher...@redhat.com] Upgrade from prevrelease-suite-master doesn't exist. You 
probably want to test upgrade from 4.2->master which is upgrade from 
release_suite master (currently, master is not considered a 'release').

There was a discussion on this topic here OVIRT-2091.

> upgrade-from-prevrelease-suite failure *.repo No such file or directory
> ---
>
> Key: OVIRT-2417
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2417
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: OST Manual job
>Reporter: Greg Sheremeta
>Assignee: infra
>Priority: Highest
>
> Hi,
> Re: packaging: Replace dashboard with ui-extensions
> https://gerrit.ovirt.org/#/c/92698/
> As Didi requested, I tried to run upgrade-from-prevrelease-suite but:
> *23:45:23* + cp
> 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo'
> exported-artifacts*23:45:23* cp: cannot stat
> 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo': No
> such file or directory*23:45:23* POST BUILD TASK : FAILURE*23:45:23*
> END OF POST BUILD TASK : 0*23:45:23* ESCALATE FAILED POST BUILD TASK
> TO JOB STATUS
> Can you assist?
> -- 
> GREG SHEREMETA
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
> Red Hat NA
> 
> gsher...@redhat.comIRC: gshereme
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5TDF43JA54EGHN2JW6SAVQXW4CAKYD5C/

[JIRA] (OVIRT-2416) Evaluate available options for Jenkins slaves

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2416:
-

 Summary: Evaluate available options for Jenkins slaves
 Key: OVIRT-2416
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2416
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


We need to see where we'll get slaves for CNV Jenkins



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/C7XO2NSGTOBSRTSK6OETBESKQIOA35PG/

[JIRA] (OVIRT-2416) Evaluate available options for Jenkins slaves

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2416:
--
Epic Link: OVIRT-2413

> Evaluate available options for Jenkins slaves
> -
>
> Key: OVIRT-2416
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2416
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> We need to see where we'll get slaves for CNV Jenkins



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GLXEGCX37YLKHXPJUZOSIUQXBZVLWWMN/

[JIRA] (OVIRT-2413) Set up CNV Jenkins to run STDCI

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2413:
--
Description: 
Add here all tasks that needs to be done in order to run STDCI on CNV Jenkins.

https://cnv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/

  was:Add here all tasks that needs to be done in order to run STDCI on CNV 
Jenkins


> Set up CNV Jenkins to run STDCI
> ---
>
> Key: OVIRT-2413
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2413
> Project: oVirt - virtualization made easy
>  Issue Type: Epic
>Reporter: Daniel Belenky
>Assignee: infra
>
> Add here all tasks that needs to be done in order to run STDCI on CNV Jenkins.
> https://cnv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PNZSCFEN465UEWB6MJIG7NGKCXCXEJ7W/

[JIRA] (OVIRT-2415) Upload secrets file to new Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2415:
--
Epic Link: OVIRT-2413

> Upload secrets file to new Jenkins
> --
>
> Key: OVIRT-2415
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2415
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> In order to use secrets, we need to upload a STDCI secrets file. Secret name 
> should be *ci_secrets_file* and file name should be *ci_secrets_file.yaml*



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SZHDAQY2PDG5H4ECCABLO6CN5K3JU5A2/

[JIRA] (OVIRT-2415) Upload secrets file to new Jenkins

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2415:
-

 Summary: Upload secrets file to new Jenkins
 Key: OVIRT-2415
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2415
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


In order to use secrets, we need to upload a STDCI secrets file. Secret name 
should be *ci_secrets_file* and file name should be *ci_secrets_file.yaml*



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/RFIVWOKBT6B4HFWW4AT5WIMUECKANNJ6/

[JIRA] (OVIRT-2414) Make a list of all Jenkins plugins we need and install them on the new Jenkins

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2414:
-

 Summary: Make a list of all Jenkins plugins we need and install 
them on the new Jenkins
 Key: OVIRT-2414
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2414
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


In order to run on Jenkins, STDCI requires some plugins installed such as 
Gerrit trigger, GitHub webhook and etc. We need to make a list of all plugins 
we need to install them



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/MBEET6ALHYQB7NLP2KWQBDOFY2UX52ZY/

[JIRA] (OVIRT-2414) Make a list of all Jenkins plugins we need and install them on the new Jenkins

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2414:
--
Epic Link: OVIRT-2413

> Make a list of all Jenkins plugins we need and install them on the new Jenkins
> --
>
> Key: OVIRT-2414
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2414
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> In order to run on Jenkins, STDCI requires some plugins installed such as 
> Gerrit trigger, GitHub webhook and etc. We need to make a list of all plugins 
> we need to install them



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LJXXIPJHGMIQACYGLIT2IU423FKJ2TSC/

[JIRA] (OVIRT-2413) Set up CNV Jenkins to run STDCI

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2413:
--
Description: Add here all tasks that needs to be done in order to run STDCI 
on CNV Jenkins

> Set up CNV Jenkins to run STDCI
> ---
>
> Key: OVIRT-2413
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2413
> Project: oVirt - virtualization made easy
>  Issue Type: Epic
>Reporter: Daniel Belenky
>Assignee: infra
>
> Add here all tasks that needs to be done in order to run STDCI on CNV Jenkins



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XGKJJUHKMFTPUSLEXETPWHTLRZZLEN4H/

[JIRA] (OVIRT-2413) Set up CNV Jenkins to run STDCI

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2413:
-

 Summary: Set up CNV Jenkins to run STDCI
 Key: OVIRT-2413
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2413
 Project: oVirt - virtualization made easy
  Issue Type: Epic
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/X4O47FWODROD4PDIX2M4DPZRXYC75TTM/

[JIRA] (OVIRT-2408) Add shared volume between stdci-containers

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2408:
-

Assignee: Daniel Belenky  (was: infra)

> Add shared volume between stdci-containers
> --
>
> Key: OVIRT-2408
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2408
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> Sometimes we need to store large files (such as images) to be used by builds. 
> Because those files are large, we'd prefer to store them once because our 
> disk is limited and to avoid too many I/O calls.
> Create a /shared volume under /var/lib/stdci and mount it to every 
> stdci-container slave under the same path. Projects then can access it by 
> mounting it to mock via *.mou



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XAOQ46P2FWBYSVT4LNBSR6CPOAWPN22L/

[JIRA] (OVIRT-2408) Add shared volume between stdci-containers

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2408:
--
Epic Link: OVIRT-2339

> Add shared volume between stdci-containers
> --
>
> Key: OVIRT-2408
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2408
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> Sometimes we need to store large files (such as images) to be used by builds. 
> Because those files are large, we'd prefer to store them once because our 
> disk is limited and to avoid too many I/O calls.
> Create a /shared volume under /var/lib/stdci and mount it to every 
> stdci-container slave under the same path. Projects then can access it by 
> mounting it to mock via *.mou



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JIYUHKPVGLQQF347NCWWRW5X45GXXZ5A/

[JIRA] (OVIRT-2408) Add shared volume between stdci-containers

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2408:
-

 Summary: Add shared volume between stdci-containers
 Key: OVIRT-2408
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2408
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Daniel Belenky
Assignee: infra


Sometimes we need to store large files (such as images) to be used by builds. 
Because those files are large, we'd prefer to store them once because our disk 
is limited and to avoid too many I/O calls.

Create a /shared volume under /var/lib/stdci and mount it to every 
stdci-container slave under the same path. Projects then can access it by 
mounting it to mock via *.mou



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/57CUTYS5UWVBNIXDI4VM3YKFAJ7PM72R/

[JIRA] (OVIRT-2401) Update SSL cert in staging OpenShift instance

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2401:
-

Assignee: Evgheni Dereveanchin  (was: infra)

> Update SSL cert in staging OpenShift instance
> -
>
> Key: OVIRT-2401
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2401
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: Evgheni Dereveanchin
>
> Currently, I can't reach it due to bad SSL cert (chrome doesn't even let me 
> the option to ignore the warning...)



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/62ZEUNK3XL3WHONMV632HJPAUZ6MO55M/

[JIRA] (OVIRT-2401) Update SSL cert in staging OpenShift instance

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2401:
--
Epic Link: OVIRT-403

> Update SSL cert in staging OpenShift instance
> -
>
> Key: OVIRT-2401
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2401
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> Currently, I can't reach it due to bad SSL cert (chrome doesn't even let me 
> the option to ignore the warning...)



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GAQSY7VOECNE4ISEZH7QV5ZTUUJW5XZ2/

[JIRA] (OVIRT-2401) Update SSL cert in staging OpenShift instance

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2401:
-

 Summary: Update SSL cert in staging OpenShift instance
 Key: OVIRT-2401
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2401
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Daniel Belenky
Assignee: infra


Currently, I can't reach it due to bad SSL cert (chrome doesn't even let me the 
option to ignore the warning...)



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/Q3DWCB5ODR3WYFSTXLJ56TXDOBGF3KVM/

[JIRA] (OVIRT-2330) Host specific resource allocation for stdci containers

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2330:
--
Resolution: Won't Do
Status: Done  (was: To Do)

Will be done in OVIRT-2390

> Host specific resource allocation for stdci containers
> --
>
> Key: OVIRT-2330
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2330
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> To maximize the utilization of stdci containers, we need a mechanism that can 
> decide how much RAM and CPU each stdci container gets and how many stdci 
> containers we can run on that host.
> A special handling should be done for user-defined containers (those are ones 
> that the user run as part of his script). Those containers are created using 
> a mounted docker socket, so the resource limit we put on the STDCI container 
> will not affect them. 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XWPMHM2ALIZKXKDSC33NRUR7A7S6KIEM/

[JIRA] (OVIRT-2389) libvirt issues on ovirt-srv17

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky commented on OVIRT-2389:
---

Not related to the container work...





-- 

DANIEL BELENKY


> libvirt issues on ovirt-srv17
> -
>
> Key: OVIRT-2389
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2389
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins Slaves
>Reporter: Yuval Turgeman
>Assignee: infra
>
> Recently, jobs that run on ovirt-srv17 and use libvirt to install a vm, fail 
> because the vms do not receive an ip from libvirt/dnsmasq.  Some examples:
> https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/64/
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/
> Thanks.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/4ZUTGKZM53BLOVY677JU3HIGIKS3WU6Y/

[JIRA] (OVIRT-2396) mirrors_client should export the the files it injects

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2396:
--
Resolution: Won't Do
Status: Done  (was: To Do)

> mirrors_client should export the the files it injects
> -
>
> Key: OVIRT-2396
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2396
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Change Queue, Standard CI (Pipelines)
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: first_time_task
>
> As an infra-owner I want to be able to see the injected repo files so that 
> I'll be able to easily view the repos that were used by OST for debugging.
> * mirror_client.py should collect the files it injects mirrors to and put 
> them in a dedicated directory - probably should be some kind of a flag so we 
> won't change the default behavior.
> * after mirror injection is called in CI/CQ we need to export them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/T5SEQERKKAJGJOIA6S7UEURMDEG55RN6/

[JIRA] (OVIRT-2396) mirrors_client should export the the files it injects

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2396:
--
Epic Link: OVIRT-400

> mirrors_client should export the the files it injects
> -
>
> Key: OVIRT-2396
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2396
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Change Queue, Standard CI (Pipelines)
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: first_time_task
>
> As an infra-owner I want to be able to see the injected repo files so that 
> I'll be able to easily view the repos that were used by OST for debugging.
> * mirror_client.py should collect the files it injects mirrors to and put 
> them in a dedicated directory - probably should be some kind of a flag so we 
> won't change the default behavior.
> * after mirror injection is called in CI/CQ we need to export them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ROVDILRLIP2QFQJRGBODKUT5BQJ3ERYQ/

[JIRA] (OVIRT-2396) mirrors_client should export the the files it injects

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2396:
-

 Summary: mirrors_client should export the the files it injects
 Key: OVIRT-2396
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2396
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: Change Queue, Standard CI (Pipelines)
Reporter: Daniel Belenky
Assignee: infra


As an infra-owner I want to be able to see the injected repo files so that I'll 
be able to easily view the repos that were used by OST for debugging.

* mirror_client.py should collect the files it injects mirrors to and put them 
in a dedicated directory - probably should be some kind of a flag so we won't 
change the default behavior.
* after mirror injection is called in CI/CQ we need to export them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2T5ZJ4HYS2XGIAMA7P3WN2P2YNB4TUZT/

[JIRA] (OVIRT-2395) Rolling updates and AB testing of STDCI container-slaves

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2395:
--
Description: Or, since STDCI slave is containerized, we can containerize 
everything (Jenkins, Gerrit, dummy-resources, etc..) and create full CI flow 
for a patch.

> Rolling updates and AB testing of STDCI container-slaves
> 
>
> Key: OVIRT-2395
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2395
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> Or, since STDCI slave is containerized, we can containerize everything 
> (Jenkins, Gerrit, dummy-resources, etc..) and create full CI flow for a patch.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DKFEARXB6QL5KDJNOHPBZUTMU62ZANH4/

[JIRA] (OVIRT-2395) Rolling updates and AB testing of STDCI container-slaves

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2395:
-

 Summary: Rolling updates and AB testing of STDCI container-slaves
 Key: OVIRT-2395
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2395
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TIXKUHFU5CC3CBGBPE5VDDOM4PKM75R2/

[JIRA] (OVIRT-2395) Rolling updates and AB testing of STDCI container-slaves

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2395:
--
Epic Link: OVIRT-2390

> Rolling updates and AB testing of STDCI container-slaves
> 
>
> Key: OVIRT-2395
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2395
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/B4PJT4GBRCGLMDSTBSRVXQNN637CRJBR/

[JIRA] (OVIRT-2394) Tear down and re-create containers between job runs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2394:
--
Epic Link: OVIRT-2390

> Tear down and re-create containers between job runs
> ---
>
> Key: OVIRT-2394
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2394
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/DCFC6Z7HGVAAGVNBMOM4DNEY3YSHDIYR/

[JIRA] (OVIRT-2394) Tear down and re-create containers between job runs

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2394:
-

 Summary: Tear down and re-create containers between job runs
 Key: OVIRT-2394
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2394
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/54RUWOKAR63W2MJHOTRWDAVGTNRQZVBV/

[JIRA] (OVIRT-2393) Automate deployment of slave-containers with OpenShift

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2393:
--
Epic Link: OVIRT-2390

> Automate deployment of slave-containers with OpenShift
> --
>
> Key: OVIRT-2393
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2393
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TGLGEJRBQTW4SGOSPYYK72PKMSQH3XFJ/

[JIRA] (OVIRT-2393) Automate deployment of slave-containers with OpenShift

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2393:
-

 Summary: Automate deployment of slave-containers with OpenShift
 Key: OVIRT-2393
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2393
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W5QYIC5SM3ADJRGKJGZKWIDJHXTQW6DL/

[JIRA] (OVIRT-2392) POC Multiple STDCI containers per host w/o sharing sets of volumes

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2392:
--
Epic Link: OVIRT-2390

> POC Multiple STDCI containers per host w/o sharing sets of volumes
> --
>
> Key: OVIRT-2392
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2392
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> Make sure that if multiple volumes are used per container, the same set of 
> volumes is always used together



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TXLABNRUCVGCDXH4XX74ONTQFICFZEII/

[JIRA] (OVIRT-2392) POC Multiple STDCI containers per host w/o sharing sets of volumes

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2392:
-

 Summary: POC Multiple STDCI containers per host w/o sharing sets 
of volumes
 Key: OVIRT-2392
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2392
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


Make sure that if multiple volumes are used per container, the same set of 
volumes is always used together



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WT3JERQLEBBA4QW6Z7FZYZVO3MIZ5EAA/

[JIRA] (OVIRT-2391) POC STDI Container on OpenShift with host volumes

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2391:
-

Assignee: Daniel Belenky  (was: infra)

> POC STDI Container on OpenShift with host volumes
> -
>
> Key: OVIRT-2391
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2391
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2V42G2CULQXBTSXANBSE52D5MP2YUEP6/

[JIRA] (OVIRT-2391) POC STDI Container on OpenShift with host volumes

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2391:
-

 Summary: POC STDI Container on OpenShift with host volumes
 Key: OVIRT-2391
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2391
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TW53GQFPWVRU5NF7MDYXZQOYZJNJRJF6/

[JIRA] (OVIRT-2391) POC STDI Container on OpenShift with host volumes

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2391:
--
Epic Link: OVIRT-2390

> POC STDI Container on OpenShift with host volumes
> -
>
> Key: OVIRT-2391
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2391
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>




--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2KHPWYTJJWOONAPBZR2TX52BJZPWTH2E/

[JIRA] (OVIRT-2390) Allow running STDCI containers on OpenShift

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2390:
-

 Summary: Allow running STDCI containers on OpenShift
 Key: OVIRT-2390
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2390
 Project: oVirt - virtualization made easy
  Issue Type: Epic
Reporter: Daniel Belenky
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6RJH4VDQJVRFN55PMO7XKYHKXZVUOHND/

[JIRA] (OVIRT-2364) STDCI containers should register themselves as agents

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2364:
--
Resolution: Won't Do
Status: Done  (was: To Do)

> STDCI containers should register themselves as agents
> -
>
> Key: OVIRT-2364
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2364
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> Instead of manually setting up an agent from Jenkins GUI, 
> run_stdci_containers.sh should register them automatically.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SG7I44YIM2OPHAXXFWY22FQRAPEHRNHS/

[JIRA] (OVIRT-2345) Allow parallel reposyncs

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2345:
--
Resolution: Won't Do
Status: Done  (was: To Do)

> Allow parallel reposyncs
> 
>
> Key: OVIRT-2345
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2345
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> Since we're going to run multiple suites in parallel on the same host, the 
> repolock may become a bottle neck. We probably will need  per-container cache 
> or something similar.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KQ6BHHKV7VYPEY3YGPI7WAX6UCBGI6TJ/

[JIRA] (OVIRT-2384) Allow single slot deployment in run_stdci_containers.sh

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2384:
-

Assignee: Daniel Belenky  (was: infra)

> Allow single slot deployment in run_stdci_containers.sh
> ---
>
> Key: OVIRT-2384
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2384
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> As an STDCI operator, I want to have the ability to deploy/modify a single 
> slot of the containerized slave so that I won't have to remove all running 
> slaves to modify one of them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BSGOH4L7DWURZTRNFNUYP43BOENDRDJ3/

[JIRA] (OVIRT-2384) Allow single slot deployment in run_stdci_containers.sh

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2384:
--
Epic Link: OVIRT-2326

> Allow single slot deployment in run_stdci_containers.sh
> ---
>
> Key: OVIRT-2384
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2384
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> As an STDCI operator, I want to have the ability to deploy/modify a single 
> slot of the containerized slave so that I won't have to remove all running 
> slaves to modify one of them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/G3YGTW4OKVRF75L34P4WDMS5BTWBHN3M/

[JIRA] (OVIRT-2384) Allow single slot deployment in run_stdci_containers.sh

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2384:
-

 Summary: Allow single slot deployment in run_stdci_containers.sh
 Key: OVIRT-2384
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2384
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


As an STDCI operator, I want to have the ability to deploy/modify a single slot 
of the containerized slave so that I won't have to remove all running slaves to 
modify one of them.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OFXB7SGJVSA5EVDCJFQUHJ5FBG3R6VK6/

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2359:
-

Assignee: Daniel Belenky  (was: infra)

> Set environment variable in jenkins user's env to inidicate it's a container
> 
>
> Key: OVIRT-2359
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> We need to set a variable under the jenkins user that will indicate we're 
> running inside a container.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2YFC7K6PXZ2HJGRUU44SSTBCDYRTPSEL/

[JIRA] (OVIRT-2382) Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky updated OVIRT-2382:
--
Epic Link: OVIRT-2326

> Refactor global_setup and slave_cleanup to have different setup/cleanup flows 
> for container slaves
> --
>
> Key: OVIRT-2382
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2382
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: infra
>
> Since setup/cleanup in a container can end up being very different than for 
> VM/BM, it's better to have different main functions instead of skipping 
> inside individual configuration functions.
> So for example, the current main will become main_native and we'll also have 
> main_container while main will just switch between the two.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KOJ524G2MFHLBASCSGUQMYMDCVW37LNQ/

[JIRA] (OVIRT-2382) Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves

[Daniel Belenky (oVirt JIRA)]

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

Daniel Belenky reassigned OVIRT-2382:
-

Assignee: Daniel Belenky  (was: infra)

> Refactor global_setup and slave_cleanup to have different setup/cleanup flows 
> for container slaves
> --
>
> Key: OVIRT-2382
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2382
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> Since setup/cleanup in a container can end up being very different than for 
> VM/BM, it's better to have different main functions instead of skipping 
> inside individual configuration functions.
> So for example, the current main will become main_native and we'll also have 
> main_container while main will just switch between the two.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/QJ33OPJIHLVPTLEKDHBC4HLRCC5SVDNT/

[JIRA] (OVIRT-2382) Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves

[Daniel Belenky (oVirt JIRA)]

Daniel Belenky created OVIRT-2382:
-

 Summary: Refactor global_setup and slave_cleanup to have different 
setup/cleanup flows for container slaves
 Key: OVIRT-2382
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2382
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


Since setup/cleanup in a container can end up being very different than for 
VM/BM, it's better to have different main functions instead of skipping inside 
individual configuration functions.

So for example, the current main will become main_native and we'll also have 
main_container while main will just switch between the two.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/RP5DWPTU75IJBIYMUFZU4LDGHQK2TH6X/