- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 69 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '18

26 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/69/ Build Number: 69 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #69 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 2

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by danken (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] danken commented on OVIRT-2259: ------------------------------- Sorry for the distraction. vdsm was not even installed on host-1: 2018-06-26 07:12:41,218-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connecting 'root@lago-basic-fc-suite-master-host-1' 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER on host-0 it was installed by means of 2018-06-26T11:07:14Z DDEBUG Command: dnf -y install ovirt-host on neither host do I see any attempt to *start* vdsm, most probably due to the failed ssh. > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by danken (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] danken updated OVIRT-2259: -------------------------- Summary: fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" (was: fc28: Failed to add ovirt-host: ) > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host:
by danken (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] danken updated OVIRT-2259: -------------------------- Summary: fc28: Failed to add ovirt-host: (was: Failed to add ovirt-host which runs on FC28) > fc28: Failed to add ovirt-host: > -------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2261) Configure FC28 VMs to save system.journal as text files
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

Gal Ben Haim created OVIRT-2261: ----------------------------------- Summary: Configure FC28 VMs to save system.journal as text files Key: OVIRT-2261 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2261 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gal Ben Haim Assignee: infra Priority: Low Configure FC28 VMs to save system.journal as text files, so it will be possible to read them on Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2261) Configure FC28 VMs to save system.journal as text files
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2261?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2261: -------------------------------- Epic Link: OVIRT-2177 > Configure FC28 VMs to save system.journal as text files > ------------------------------------------------------- > > Key: OVIRT-2261 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2261 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: infra > Priority: Low > > Configure FC28 VMs to save system.journal as text files, so it will be possible > to read them on Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2259: ------------------------------------- [^host-0-journal.txt] [~danken(a)redhat.com] > Failed to add ovirt-host which runs on FC28 > ------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2259: -------------------------------- Attachment: host-0-journal.txt > Failed to add ovirt-host which runs on FC28 > ------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by danken (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] danken commented on OVIRT-2259: ------------------------------- https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… shows that vdsm.log is empty, meaning that vdsmd has not started. Debugging further is difficult, since /var/log/mesasges is missing and the journal is an ugly binary blob https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… Can you look inside it for a reason why vdsm is down? > Failed to add ovirt-host which runs on FC28 > ------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2187) Create master suite based on FC 28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2187?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2187: -------------------------------- Status: Blocked (was: In Progress) > Create master suite based on FC 28 > ---------------------------------- > > Key: OVIRT-2187 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2187 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2260) Automate container builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2260?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2260: -------------------------------- Assignee: Gal Ben Haim (was: infra) > Automate container builds for kubevirt-ansible > ---------------------------------------------- > > Key: OVIRT-2260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2260 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: KubeVirt-Ansible > Reporter: Eyal Edri > Assignee: Gal Ben Haim > Priority: High > > One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2260) Automate container builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

Eyal Edri created OVIRT-2260: -------------------------------- Summary: Automate container builds for kubevirt-ansible Key: OVIRT-2260 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2260 Project: oVirt - virtualization made easy Issue Type: Improvement Components: KubeVirt-Ansible Reporter: Eyal Edri Assignee: infra Priority: High One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2260) Automate container builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2260?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2260: ----------------------------- Epic Link: OVIRT-2247 > Automate container builds for kubevirt-ansible > ---------------------------------------------- > > Key: OVIRT-2260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2260 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: KubeVirt-Ansible > Reporter: Eyal Edri > Assignee: infra > Priority: High > > One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

Gal Ben Haim created OVIRT-2259: ----------------------------------- Summary: Failed to add ovirt-host which runs on FC28 Key: OVIRT-2259 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm From engine.log: ``` 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER ``` Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2259: -------------------------------- Epic Link: OVIRT-2177 > Failed to add ovirt-host which runs on FC28 > ------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2258) Automate RPM builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

Eyal Edri created OVIRT-2258: -------------------------------- Summary: Automate RPM builds for kubevirt-ansible Key: OVIRT-2258 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2258 Project: oVirt - virtualization made easy Issue Type: Improvement Components: KubeVirt-Ansible Reporter: Eyal Edri Assignee: infra Priority: High One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2258) Automate RPM builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2258?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2258: ----------------------------- Epic Link: OVIRT-2247 > Automate RPM builds for kubevirt-ansible > ---------------------------------------- > > Key: OVIRT-2258 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2258 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: KubeVirt-Ansible > Reporter: Eyal Edri > Assignee: infra > Priority: High > > One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. > h3. Acceptance criteria > # We define a borrower and a borrowing Jenkins instances. Ans support the use case where both are the same instance > # Borrowing is done by setting up a JNLP connection from the slave of the borrower instance to to borrowing instance. > # On the borrower instance: > ## We have a "borrow" job that: > ##* Takes slave requirement details, allocates a matching slaves and make it connect via JNLP to the borrowing instance > ##* If all matching slaves are already borrowed by other instances, try to call the garbage collector jobs (see below) on borrowing instances to free the slaves. > ## We have a "return" job that is called by a borrowing instance to return a slave > # On the borrowing instance > ## STDCI tries to borrow slaves from a predefined instance if not matching slaves are available locally > ## Once borrowed - slaves stay attached to the borrowing instance so they can be reused by other STDCI jobs. > ## We have a "garbage collector" job that is triggered periodically or by the borrower instance. It looks at borrowed slaves, and frees ones that were not used recently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2254: ------------------------------------- Some design details: * The "borrow" job takes the following parameters: ** The IP and JNLP port of the Jenkins that is borrowing the slave ** The JNLP secret to register to the Jenkins that is borrowing the slave ** A YAML/JSON structure with node requirements that includes: *** A *kind* field set to "{{stdci_node_req}}" *** An *apiVersion* field set to "{{1}}". *** The project *name*. *** The project *clone_ur*, *branch* and *refspec*. *** The STDCI thread *stage*, *substage*, *distro* and *arch*. *** The STDCI *runtime_requirements*. > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. > h3. Acceptance criteria > # We define a borrower and a borrowing Jenkins instances. Ans support the use case where both are the same instance > # Borrowing is done by setting up a JNLP connection from the slave of the borrower instance to to borrowing instance. > # On the borrower instance: > ## We have a "borrow" job that: > ##* Takes slave requirement details, allocates a matching slaves and make it connect via JNLP to the borrowing instance > ##* If all matching slaves are already borrowed by other instances, try to call the garbage collector jobs (see below) on borrowing instances to free the slaves. > ## We have a "return" job that is called by a borrowing instance to return a slave > # On the borrowing instance > ## STDCI tries to borrow slaves from a predefined instance if not matching slaves are available locally > ## Once borrowed - slaves stay attached to the borrowing instance so they can be reused by other STDCI jobs. > ## We have a "garbage collector" job that is triggered periodically or by the borrower instance. It looks at borrowed slaves, and frees ones that were not used recently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Description: "Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master.\r\n\r\nh3. Acceptance criteria\r\n# We define a borrower and a borrowing Jenkins instances. Ans support the use case where both are the same instance\r\n# Borrowing is done by setting up a JNLP connection from the slave of the borrower instance to to borrowing instance.\r\n# On the borrower instance:\r\n## We have a \"borrow\" job that:\r\n##* Takes slave requirement details, allocates a matching slaves and make it connect via JNLP to the borrowing instance\r\n##* If all matching slaves are already borrowed by other instances, try to call the garbage collector jobs (see below) on borrowing instances to free the slaves.\r\n## We have a \"return\" job that is called by a borrowing instance to return a slave\r\n# On the borrowing instance\r\n## STDCI tries to borrow slaves from a predefined instance if not matching slaves are available locally\r\n## Once borrowed - slaves stay attached to the borrowing instance so they can be reused by other STDCI jobs.\r\n## We have a \"garbage collector\" job that is triggered periodically or by the borrower instance. It looks at borrowed slaves, and frees ones that were not used recently.\r\n\r\n" (was: Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. h3. Acceptance criteria # Create a job that allows another Jenkins instance to borrow a slave from the instance the job runs on. The job will: #* Take the following parameters: #** The IP and JNLP port of the Jenkins that is borrowing the slave #** The JNLP secret to register to the Jenkins that is borrowing the slave #** A YAML/JSON structure with node requirements that includes: #*** A *kind* field set to "{{stdci_node_req}}" #*** An *apiVersion* field set to "{{1}}". #*** The project *name*. #*** The project *clone_ur*, *branch* and *refspec*. #*** The STDCI thread *stage*, *substage*, *distro* and *arch*. #*** The STDCI *runtime_requirements*. #* Attempt to find a slave meeting the specified requirements #* If slave found: #** Set it to be used only with matching label expressions #** Label it with "borrowed" #** Start the JNLP client on the slave to make it connect to the borrowing Jenkins #** Archive an artifact containing the name on the slave. #** Finish successfully #* If slave not found - finish with an error. # Create a groovy function to be used from STDCI to borrow a slave. The function will: #* Allocate a JNLP node record for the new slave witha random temporary name starting with "borrowed_" to get a JNLP secret. #* Set a random label to the node record #* Launch the borrow slave job on a remote Jenkins instance that can be configured in JJB YAML by using the "Parametrized Remote Trigger" plugin #* If the job is successful: #** Rename the node record to the name of the slave we get from the artifact created by the borrow slave job with the 'borrowed_' prefix added. #** Return the random label allocated to it # Create a job that makes a jenkins instance release slaves it borrowed ) > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. > h3. Acceptance criteria > # We define a borrower and a borrowing Jenkins instances. Ans support the use case where both are the same instance > # Borrowing is done by setting up a JNLP connection from the slave of the borrower instance to to borrowing instance. > # On the borrower instance: > ## We have a "borrow" job that: > ##* Takes slave requirement details, allocates a matching slaves and make it connect via JNLP to the borrowing instance > ##* If all matching slaves are already borrowed by other instances, try to call the garbage collector jobs (see below) on borrowing instances to free the slaves. > ## We have a "return" job that is called by a borrowing instance to return a slave > # On the borrowing instance > ## STDCI tries to borrow slaves from a predefined instance if not matching slaves are available locally > ## Once borrowed - slaves stay attached to the borrowing instance so they can be reused by other STDCI jobs. > ## We have a "garbage collector" job that is triggered periodically or by the borrower instance. It looks at borrowed slaves, and frees ones that were not used recently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2187) Create master suite based on FC 28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2187?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2187: -------------------------------- Status: In Progress (was: Blocked) > Create master suite based on FC 28 > ---------------------------------- > > Key: OVIRT-2187 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2187 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2153: ------------------------------------- Adding OVIRT-2257 as a blocker as implementing it will solve this organically. > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: mock_runner > Reporter: sbonazzo > Assignee: infra > Priority: High > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2257) Make mock runner use the config files shipped with mock instead of its own set of files
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

Barak Korren created OVIRT-2257: ----------------------------------- Summary: Make mock runner use the config files shipped with mock instead of its own set of files Key: OVIRT-2257 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2257 Project: oVirt - virtualization made easy Issue Type: New Feature Components: mock_runner Reporter: Barak Korren Assignee: infra As an oVirt CI team member, I want to not have to maintain mock configuration files. As an oVirt developer I want distributions to be supported as soon as mock supports them without having to wait for the CI team to support it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2257) Make mock runner use the config files shipped with mock instead of its own set of files
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2257?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2257: -------------------------------- Epic Link: OVIRT-2189 > Make mock runner use the config files shipped with mock instead of its own set of files > --------------------------------------------------------------------------------------- > > Key: OVIRT-2257 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2257 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > As an oVirt CI team member, I want to not have to maintain mock configuration files. > As an oVirt developer I want distributions to be supported as soon as mock supports them without having to wait for the CI team to support it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2153: -------------------------------- Priority: High (was: Highest) > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: mock_runner > Reporter: sbonazzo > Assignee: infra > Priority: High > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2153: -------------------------------- Priority: Highest (was: Medium) > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: mock_runner > Reporter: sbonazzo > Assignee: infra > Priority: Highest > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2153: -------------------------------- Component/s: mock_runner > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: mock_runner > Reporter: sbonazzo > Assignee: infra > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Description: "Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master.\r\n\r\nh3. Acceptance criteria\r\n# Create a job that allows another Jenkins instance to borrow a slave from the instance the job runs on. The job will:\r\n#* Take the following parameters:\r\n#** The IP and JNLP port of the Jenkins that is borrowing the slave\r\n#** The JNLP secret to register to the Jenkins that is borrowing the slave\r\n#** A YAML/JSON structure with node requirements that includes:\r\n#*** A *kind* field set to \"{{stdci_node_req}}\"\r\n#*** An *apiVersion* field set to \"{{1}}\".\r\n#*** The project *name*.\r\n#*** The project *clone_ur*, *branch* and *refspec*.\r\n#*** The STDCI thread *stage*, *substage*, *distro* and *arch*.\r\n#*** The STDCI *runtime_requirements*.\r\n#* Attempt to find a slave meeting the specified requirements\r\n#* If slave found:\r\n#** Set it to be used only with matching label expressions\r\n#** Label it with \"borrowed\"\r\n#** Start the JNLP client on the slave to make it connect to the borrowing Jenkins\r\n#** Archive an artifact containing the name on the slave.\r\n#** Finish successfully\r\n#* If slave not found - finish with an error.\r\n# Create a groovy function to be used from STDCI to borrow a slave. The function will:\r\n#* Allocate a JNLP node record for the new slave witha random temporary name starting with \"borrowed_\" to get a JNLP secret.\r\n#* Set a random label to the node record\r\n#* Launch the borrow slave job on a remote Jenkins instance that can be configured in JJB YAML by using the \"Parametrized Remote Trigger\" plugin\r\n#* If the job is successful:\r\n#** Rename the node record to the name of the slave we get from the artifact created by the borrow slave job with the 'borrowed_' prefix added.\r\n#** Return the random label allocated to it\r\n# Create a job that makes a jenkins instance release slaves it borrowed " (was: Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another jenkins master. h3. Acceptance criteria ) > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. > h3. Acceptance criteria > # Create a job that allows another Jenkins instance to borrow a slave from the instance the job runs on. The job will: > #* Take the following parameters: > #** The IP and JNLP port of the Jenkins that is borrowing the slave > #** The JNLP secret to register to the Jenkins that is borrowing the slave > #** A YAML/JSON structure with node requirements that includes: > #*** A *kind* field set to "{{stdci_node_req}}" > #*** An *apiVersion* field set to "{{1}}". > #*** The project *name*. > #*** The project *clone_ur*, *branch* and *refspec*. > #*** The STDCI thread *stage*, *substage*, *distro* and *arch*. > #*** The STDCI *runtime_requirements*. > #* Attempt to find a slave meeting the specified requirements > #* If slave found: > #** Set it to be used only with matching label expressions > #** Label it with "borrowed" > #** Start the JNLP client on the slave to make it connect to the borrowing Jenkins > #** Archive an artifact containing the name on the slave. > #** Finish successfully > #* If slave not found - finish with an error. > # Create a groovy function to be used from STDCI to borrow a slave. The function will: > #* Allocate a JNLP node record for the new slave witha random temporary name starting with "borrowed_" to get a JNLP secret. > #* Set a random label to the node record > #* Launch the borrow slave job on a remote Jenkins instance that can be configured in JJB YAML by using the "Parametrized Remote Trigger" plugin > #* If the job is successful: > #** Rename the node record to the name of the slave we get from the artifact created by the borrow slave job with the 'borrowed_' prefix added. > #** Return the random label allocated to it > # Create a job that makes a jenkins instance release slaves it borrowed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2255) build aborted on time out
by Dafna Ron (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2255?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2255: ---------------------------------- [~gbenhaim(a)redhat.com] can you please take a look? > build aborted on time out > -------------------------- > > Key: OVIRT-2255 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2255 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago > > We had a test aborted which seemed to have been on time out. > Build was aborted: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/ > I can see it was a timeout: Timeout has been exceeded > sigterm was sent by lago: > '+ logger.success 'Cleanup done' > + logger.log SUCCESS 'Cleanup done' > + set +x > run_suite.sh::env_cleanup::SUCCESS:: Cleanup done > + exit 0 > + exit > Sending interrupt signal to process > sh: line 1: 47038 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/script.sh' > '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/jenkins-log.txt' 2>&1 > After 10s process did not stop' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2256) Install the Parametrized Remote Trigger plugin
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

Barak Korren created OVIRT-2256: ----------------------------------- Summary: Install the Parametrized Remote Trigger plugin Key: OVIRT-2256 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2256 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Master Reporter: Barak Korren Assignee: infra Please install the [Parametrized Remote Trigger|https://plugins.jenkins.io/Parameterized-Remote-Trigger] plugin so we can use it to trigger jobs in remote Jenkins instances. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 278 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '18

26 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 278 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #278 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Issue Type: New Feature (was: Bug) > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another jenkins master. > h3. Acceptance criteria -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2255) build aborted on time out
by Dafna Ron (oVirt JIRA) 26 Jun '18

26 Jun '18

Dafna Ron created OVIRT-2255: -------------------------------- Summary: build aborted on time out Key: OVIRT-2255 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2255 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We had a test aborted which seemed to have been on time out. Build was aborted: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/ I can see it was a timeout: Timeout has been exceeded sigterm was sent by lago: '+ logger.success 'Cleanup done' + logger.log SUCCESS 'Cleanup done' + set +x run_suite.sh::env_cleanup::SUCCESS:: Cleanup done + exit 0 + exit Sending interrupt signal to process sh: line 1: 47038 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/script.sh' > '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/jenkins-log.txt' 2>&1 After 10s process did not stop' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

Barak Korren created OVIRT-2254: ----------------------------------- Summary: Create slave borrowing flow Key: OVIRT-2254 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Master, Jenkins Slaves Reporter: Barak Korren Assignee: infra Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another jenkins master. h3. Acceptance criteria -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Epic Link: OVIRT-2178 > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another jenkins master. > h3. Acceptance criteria -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Component/s: (was: CI Mirrors) Jenkins Slaves > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another. > The are several issues that are caused by this configuration: > # Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675. > # The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Description: "Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another.\r\n\r\nThe are several issues that are caused by this configuration:\r\n# Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675.\r\n# The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system.\r\n\r\n\r\n\r\n" (was: One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. ) > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another. > The are several issues that are caused by this configuration: > # Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675. > # The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Summary: The s390x slave is used in parallel by both the staging and the production CI systems (was: Rece condition in python tests in jenkins repo on s390x) > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. > This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. > This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) Rece condition in python tests in jenkins repo on s390x
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2252: -------------------------------- Description: "One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number.\r\n\r\nThis can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave.\r\n\r\nThis issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions.\r\n\r\n\r\n" (was: One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions.) > Rece condition in python tests in jenkins repo on s390x > ------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. > This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. > This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 292 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '18

26 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/292/ Build Number: 292 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #292 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 409 reason: Conflict detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 200, in snapshot_merge api.vms.get(VM0_NAME).snapshots.list()[-2].delete() File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34001, in delete headers={"Correlation-Id":correlation_id,"Content-type":None} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 57, in delete return self.request('DELETE', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0.

1 3

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 323 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '18

26 Jun '18

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/323/ Build Number: 323 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #323 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 1

[CQ]: 92522, 2 (ovirt-engine-dashboard) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jun '18

26 Jun '18

Change 92522,2 (ovirt-engine-dashboard) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92522/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8355/

1 0

[CQ]: 91870, 7 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jun '18

26 Jun '18

Change 91870,7 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/91870/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/

1 0

[JIRA] (OVIRT-2248) Add CI for kubevirt-apb repo
by Gal Ben Haim (oVirt JIRA) 25 Jun '18

25 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2248?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2248: -------------------------------- Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) > Add CI for kubevirt-apb repo > ---------------------------- > > Key: OVIRT-2248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2248 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92414, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '18

25 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92414,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92486,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92486,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92414/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92486/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8348/

1 0

[JIRA] (OVIRT-2253) Move git function from usrc.py to a share library
by Daniel Belenky (oVirt JIRA) 25 Jun '18

25 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2253?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2253: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Move git function from usrc.py to a share library > ------------------------------------------------- > > Key: OVIRT-2253 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2253 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: usrc.py > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Change queue needs to have the ability to tag changes. > We don't want to add new dependencies to change queue so we need a python function to wrap Git commands. Such function is implemented in usrc.py so it needs to be moved to a shared library. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2253) Move git function from usrc.py to a share library
by Daniel Belenky (oVirt JIRA) 25 Jun '18

25 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2253?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2253: ---------------------------------- Epic Link: OVIRT-1717 > Move git function from usrc.py to a share library > ------------------------------------------------- > > Key: OVIRT-2253 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2253 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: usrc.py > Reporter: Daniel Belenky > Assignee: infra > > Change queue needs to have the ability to tag changes. > We don't want to add new dependencies to change queue so we need a python function to wrap Git commands. Such function is implemented in usrc.py so it needs to be moved to a shared library. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2253) Move git function from usrc.py to a share library
by Daniel Belenky (oVirt JIRA) 25 Jun '18

25 Jun '18

Daniel Belenky created OVIRT-2253: ------------------------------------- Summary: Move git function from usrc.py to a share library Key: OVIRT-2253 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2253 Project: oVirt - virtualization made easy Issue Type: Improvement Components: usrc.py Reporter: Daniel Belenky Assignee: infra Change queue needs to have the ability to tag changes. We don't want to add new dependencies to change queue so we need a python function to wrap Git commands. Such function is implemented in usrc.py so it needs to be moved to a shared library. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2252) Rece condition in python tests in jenkins repo on s390x
by Barak Korren (oVirt JIRA) 25 Jun '18

25 Jun '18

Barak Korren created OVIRT-2252: ----------------------------------- Summary: Rece condition in python tests in jenkins repo on s390x Key: OVIRT-2252 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 Project: oVirt - virtualization made easy Issue Type: Bug Components: CI Mirrors Reporter: Barak Korren Assignee: infra One of the tests of the CI mirrors python package is starting up an HTTP server on a fixed port number. This can cause an issue if the same test is running in parallel on the same machine. This typically cannot be an issue on the CI infra because it never runs more then one STDCI thread at a time on a given slave. This issue does arise specifically on the s390x slave because there the same slave is used both by the staging and the production CI systems. In that case the two systems might be trying to run the same test at the same time, so this can lead to port allocation exceptions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92486,1 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 25 Jun '18

25 Jun '18

Change 92486,1 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92486/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8346/

1 0