[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jir... ]
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/134...
> [~danken@redhat.com][~nsoffer(a)redhat.com][~mwperina] any advise?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
5 years, 10 months
[JIRA] (OVIRT-2258) Automate RPM builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA)
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)
5 years, 10 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:
--------------------------------
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)
5 years, 10 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 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)
5 years, 10 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# 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)
5 years, 10 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 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)
5 years, 10 months
[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)
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)
5 years, 10 months