- Infra - oVirt List Archives

[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