[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jir... ]
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)
6 years, 6 months
[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jir... ]
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)
6 years, 6 months
[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jir... ]
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)
6 years, 6 months
[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jir... ]
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)
6 years, 6 months
[JIRA] (OVIRT-2255) build aborted on time out
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2255?page=com.atlassian.jir... ]
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)
6 years, 6 months
[JIRA] (OVIRT-2256) Install the Parametrized Remote Trigger plugin
by Barak Korren (oVirt JIRA)
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)
6 years, 6 months
[JIRA] (OVIRT-2255) build aborted on time out
by Dafna Ron (oVirt JIRA)
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)
6 years, 6 months
[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA)
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)
6 years, 6 months
